One possibility is that your primary name server is failing, and your secondary name server is succeeding. This would account for why you can browse and surf, as Windows will fallback to secondary name servers after a timeout period. However SB2 does not seem to timeout or fallback correctly to secondary name servers.
I configured a test, and added a bogus primary nameserver and a good secondardy nameserver. After reconfiguring networking, I could no longer connect to SqueezeNetwork, despite a valid secondary nameserver. Try testing your primary nameserver in a Windows command shell. The command nslookup slimdevices.com PRIMARY-NAMESERVER-IP where PRIMARY-NAMESERVER-IP is the IP address of your primary nameserver. If you get back a "no response from server" message, this would validate the problem, especially if the nslookup works for the secondardy nameserver address. -- MrC _______________________________________________ squeezenetwork mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/squeezenetwork
