Switches and routers maintain databases of connected devices in their RAM (MAC address tables, ARP caches) and those tables can become corrupt and require a reboot of a specific device (usually that will take care of it) or of the entire network infrastructure (thereby forcing a complete re-convergence of device location information and pathing). Sometimes you have to leave a device powered off for a bit to completely clear the corrupted/incorrect data in memory. Doesn't happen often, but can be a tricky one when it does.
Also, device IP address conflicts can be a tricky bitch to suss out, and manually setting addresses rather than allowing DHCP to deal with it causes this type of problem with some regularity (I've had times I'd swear on my life that addressing was good only to discover later I was wrong). DHCP can also foul up, and I'm not sure the DHCP servers sitting in a $60 WAP or internet router are going to be the most consistent for correct addressing. The question that would seem to remain to some degree is why the SB *seems* to be more sensitive to this sort of stuff (or is that more perception and we're just more used to rebooting PCs 1000 times when they're quirking out?). Dunno. -- joncourage SlimServer Version: 6.5b1 - 6939 - Windows XP - EN - cp1252 Player Firmware Version: 41 SB3 > Audio Note DAC 3.1x Sig > Levinson 383 integrated > Amphion Argons ------------------------------------------------------------------------ joncourage's Profile: http://forums.slimdevices.com/member.php?userid=2837 View this thread: http://forums.slimdevices.com/showthread.php?t=23828 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
