Jim Perrin wrote: >> Tried that several times, but the answer is always "it must be your DNS". > > That usually is the problem for what you're describing. But the odd thing is that no matter where in the world I connect (and therefore using the DNS of whoever I'm connected through) I still get the same error. If it was only on (for example) my home network using my own ISP's DNS, I'd agree the DNS would be the problem, but it's everywhere (and no, I'm not running a DNS on my laptop, and yes, my connections do all use the DHCP-provided DNS addresses :-) ///Peter
