Hi Jim,

To reproduce this, I'd like to understand how you've got your system set up with multiple IP addresses.  Basically, I can't repro this on multiple physical systems each with slimserver, so I'm trying to figure out what might be different in your setup.

Is there some feature of XP that lets you do this, or are you running images under VMware, or what?

Thanks for any info!

They're all running on a single physical XP Pro server without virtual machines.  I have a dozen or so IP addresses bound to the server NIC.  This is easy to do on XP: Settings > Control Panel > Network Connections > Local Area Connection > Properties > Internet Protocol (TCP/IP) > Properties > Advanced > IP Addresses.  Then each instance of SlimServer runs as a Windows service that was installed using instsvr.exe and srvany.exe from the Windows Resource Kit, and downloadable from Microsoft.

All the active servers are running the Perl script version of SlimServer using ActiveWare Perl.  I have one trunk/7.0 server running, plus four beta/6.5.1 servers.  Of the different 6.5.1 servers, one is my main 'listening' server and the others point at different libraries so I can test the effects of tagging changes on Flac and MP3 files without needing to alter or scan the entire main library.  I almost never connect players to anything other than the main server - the testing I do is mostly in the web interface.

In the Windows registry for any given 6.5.1 instance of a SlimServer service, under Parameters/AppParameters, I enter something like the following to designate the IP address under which the server is to run, and the location of the log file.

"C:\Program Files\SlimServer 6.5 Dev\server\slimserver.pl" --playeraddr 192.168.9.6 --cliaddr 192.168.9.6 --streamaddr 192.168.9.6 --httpaddr 192.168.9.6 --httpport 80 --noupnp --logfile "D:\slim\dot6\server.log"

I noticed the problem last week when updating firmware on the Transporter.  For some reason when I restarted the main server, the Transporter connected to the wrong server (an older version without the newest firmware) and failed to update its firmware.  Took me a bit to realize what happened, as the SB2 on the same network always reconnects to the main server.  That's when I saw that there's no way to select another server without manually entering the IP address.  No doubt this has something to do with all the servers using the same host name, as was seen in an earlier SB bug.

There is an issue with the discovery routine apparently that crops up when using the *addr params.  I ran into it with Jive, and richard is now aware of it. Not sure what a target should be yet.

I recently also noticed this on an SB2, so it's not limited to Transporter.  Seems that there's some sequence of naviagition and connecting/disconnecting where all the local servers become visible again.  I've seen it, but I'm not certain how it came about.  Someone in the forums claims that if you connect and disconnect then all servers are seen.

We won't be able to get to this for 7.0, will revisit post-release.

This is fixed by 7.4's ability to give the server/library a name.  It's still problematic if you run multiple pre-7.4 servers, but I suppose we won't worry about that case any more.