Good to hear that you were able to get it working. In regards to using Winamp as a streaming client from slimserver. It's almost certianly not SlimServer as it streams the data in the same way regardless of client.
One thing to consider. If you have server side FLAC decoding enabled, you will actually be streaming a WAV file to Winamp. It needs to understand this and I haven't used winamp in quite a while so I'm of little help there. Even if you aren't using server side decoding, it may be that Winamp won't deal with any streaming data except for MP3.
My next goal is to be able to connect remotely to my "base" computer from my workplace computer. I am anticipating a lot of difficulty with this step, but I am willing to try it and would appreciate any insights into the process.
This could work but there are several obstacles that you will have to overcome.
1) Bandwidth. Does your home internet connection have sufficient outbound bandwidth to support a FLAC stream? Most DSL and Cable providers use asymetrical bandwidth in that upstream speeds are genearlly much slower that downstream speeds. My provider, Comcast, provides 4Mb downstream but only 256Kb upstream. Not even close to enough for a FLAC stream.
2) Router configuration. You will have to configure your router to allow inbound connections to your slimserver on the correct ports. How this is done varies from vendor to vendor. Of note is that you will be allowing traffic from the internet access to your PC. This of course carries some risk. I have no idea how secure SlimServer is or if their are exploits for it. Personally I would have SlimServer on a dedicated machine if allowing internet access to it.
3) Public internet address. Chances are high that your public internet address is assigned using DHCP. Assuming your router is always on, this likely won't change often but it may. You will need to log into your router to determine what this address is. That is the address you will need to use from remote systems to connect to your SlimServer.
Mike
