Glad that fixed it for you. Network (mis)identification can create havoc on network services. For domain joined workstations it's generally not an issue, but for computers in a workgroup network it often causes problems. It's intended as a security measure so that your computer is not as vulnerable to attack on an unknown network, so it's not completely random behavior.
There's a more permanent fix for non-mobile computers. The Local Security Policy editor allows you to set the behavior for identifying network connections including unidentified and identifying in Network List Manager Policies. Set both to Private and you shouldn't run into this issue again. However, for computers that are routinely connected to public networks (open wifi hot spots, hotel rooms, etc.) you should not make this change as it will make your computer more accessible to other devices on that network. Home: Win7Pro(x64)[3.3Ghz i5, 8GB RAM, 120GB SSD system, 15TB storage], LMS 7.9.0 -> Logitech Squeezebox Classic V.3 -> Cambridge Audio DacMagic -> NAD C160 -> 2 x NAD C272 -> Quad 22L2 Portable: FreeNAS 9.3 [HP Microserver Gen8, 10GB RAM, 16GB flash boot, 120GB SSD for LMS 7.9.0 in FreeBSD jail, 5 x 4TB WD Red HD ZFS RAIDZ1] -> Logitech Squeezebox Classic V.3 -> Cambridge Audio DacMagic: XLR out -> Soundmaster Diamond 12-2 mixing board -> P.A. ------------------------------------------------------------------------ get.amped's Profile: http://forums.slimdevices.com/member.php?userid=10022 View this thread: http://forums.slimdevices.com/showthread.php?t=105918 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
