Hi again andyg, Sorry my post had been so brief. It wasn't meant to be, and I was in a hurry.
The information came from a firewall expert/developer who I wont mention without checking with him first. In fairness the comment came from information I submitted to him, so he did not have the full picture, although I do trust his call. To paraphrase his comments: " Before the MS Windows KB951748 update, XP would use temp-range ports 1024-5000, with the update it's now 49152-65535, and the main DNS rule uses whatever is being used, so with SqueezeCenter built-in Lookups it continues to use from port 1024, even though KB951748 updated been applied to your system." This is what was happening in my SC logs: "[08-08-30 12:02:38.5171] Slim::Networking::Async::DNS::init (68) Verifying if we can use nameserver 192.168.1.254... [08-08-30 12:02:38.5175] Slim::Networking::Async::DNS::init (69) Testing lookup of f.root-servers.net [08-08-30 12:02:42.5159] Slim::Networking::Async::DNS::init (99) Lookup failed [08-08-30 12:02:42.5164] Slim::Networking::Async::DNS::init (102) Warning: No DNS servers responded, falling back to OpenDNS. " When my firewall blocked this (as it should as it was using ports 1024-5000) it then carried on blocking the OpenDNS calls as they too were using the wrong ports. I am afraid I am in a hurry again, sorry, but I hope this helps. I have created a rule in my firewall to accomodate this, but thought I'd post back to help. I'll catch up later.. -- Ron1 ------------------------------------------------------------------------ Ron1's Profile: http://forums.slimdevices.com/member.php?userid=11607 View this thread: http://forums.slimdevices.com/showthread.php?t=51705 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
