JJZolx wrote:
I recently assigned my Windows XP computer a second IP address and
switched to HTTP port 80 so that I could more easily address the
SlimServer without a port, and so that I could run Apache on port 80 at
another IP address on the same machine. SlimServer had been at
192.168.9.11:9000 previously. I'm using the --httpaddr command line
option to designate the IP address.
192.168.9.11 (audrey)
192.168.9.30 (slim) running SlimServer, HTTP port 80
I have two SB2's on my network. Both "see" the server named 'audrey'
at the .11 address, but don't "see" the server at .30. I had to key in
the IP address to connect. If I get into the network setup on either
SB, it always shows the nonexistent server.
Is this a bug, with SlimServer incorrectly announcing that it's running
on the .11 IP address?
I suppose it is a bug, but I don't understand the point of what you're
trying to do. By using the alternate port 9000, a Slimserver can easily
co-exist with Apache on the same machine with a single IP address.
I haven't checked, but it seems likely that the Squeezeboxes discover
the slimserver by their zeroconf advertisements. They're made
symbolically, not numerically, so the Squeezebox that sees a Slimserver
advertisement will assume that it can connect to it on port 9000.
Again, what's the point of what you're trying to do?
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
