Bug 1367 - needed to reconfigure (with same settings!) for other OS
: needed to reconfigure (with same settings!) for other OS
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Platform Support
: unspecified
: PC Debian Linux
: P2 normal (vote)
: Future
Assigned To: Blackketter Dean
http://mali.geekcorps.org/mediawiki/i...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-13 06:28 UTC by kasper
Modified: 2005-06-07 15:41 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kasper 2005-04-13 06:28:02 UTC
I needed to reconfigure with exactly the same network settings, for a different
OS. I was running exactly the same slimserver software, same configuration on
the host OSes, one Mandrake, one Debianic thing (Kunnafonix).

After reconfiguration the thing worked fine. But it took quite some time to
figure  this. The server machine has the same network settings on both OSes.
Comment 1 KDF 2005-04-13 11:55:30 UTC
can you provide more details? what exact problems did you run into?
Comment 2 kasper 2005-04-14 02:58:31 UTC
Well, more details.

The Squeezebox was configured at 192.168.0.14.

The Slimserver at 192.168.0.15, on a P4 machine. Everything was running fine
under Mandrake. But when booting the Debian-like system the Squeezebox didn't
find the Slimserver. Same IP address, even same Slimserver software/configs.

After several reboots (booting into Debian and Mandrake) I finally thought of
reconfiguring the Squeezebox, thinking that it wouldn't help, since I wasn't
gonna change any settings. But, then, miraculously the Squeezebox found the
Slimserver. With the same IP settings.

If you need more details, please tell me which... :)
Comment 3 KDF 2005-04-14 19:59:27 UTC
wireless/wired connection from squeezebox?
if wireless, what model/fw rev of AP?
what version of slimserver are you using?

could be a dns leasing issue, if sqeezebox thought it still had a lease, and
debian hadn't recieved a request in order to create the proper arp/route entries.
Comment 4 kasper 2005-04-15 03:06:57 UTC
The box was wired. Can't get more information right now, since
computer+squeezebox are 15 kilometers from here, and there's no internet
connection at the site - yet.
Comment 5 Blackketter Dean 2005-04-20 19:12:58 UTC
If you are connecting to a slimserver on your local subnet, Squeezebox will attempt to use the 
hostname to find the server via a broadcast.  (This is so that we can reconnect to server's whose IP 
address changes through DHCP.)  Would this explain what you are seeing?
Comment 6 kasper 2005-04-21 06:09:41 UTC
Yep, that's a perfectly valid explanation. :) It's funny however, that the
Squeezebox after the reconfiguration did recognize both of the slimservers. But,
maybe the box should first try hostname, and if that doesn't work, try same IP
address?