sgmlaw wrote: > It is sometimes not so much the server machine not seeing the Touch as > the Touch not seeing the server. > > One of the best things you can do in any server-based environment is > assign a fixed local IP address to the server machine itself. > > This will make the clients' job much easier going forward, especially > those that NV cache networking settings through reboots and updates. > Everything they need is always at the same local address, every time, > without fail. > > LMS is no different in this regard. Our SB clients can always locate > the server, with the occasional exception of our Receiver, which > occasionally balks at a final connection without intervention from the > Controller. > > While we use DHCP for clients that are constantly logging on and off, > all major static network resources (always-on elements such as servers, > NAS and other data hubs, printers and switches, etc,) get static > addresses. You will have a much more trouble-free network environment > if the major pieces are always in the same place. Place these static > resources out of the assigned DHCP range, and even the most poorly > designed DHCP server can handle it. You will rarely need 'finder' apps > to hunt down moving resources again. > > After decades of networking, this is the best way to do it.
Have never had to do that in the past plus 12 years of using Slim Devices/Squeezebox/LMS. This just started happening recently. ------------------------------------------------------------------------ tdehan's Profile: http://forums.slimdevices.com/member.php?userid=65180 View this thread: http://forums.slimdevices.com/showthread.php?t=109856 _______________________________________________ Touch mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/touch
