Hrm. Could be that the setup might be malforming the header sent to the NYT server. To be honest, more specifics are needed - what error are you getting (if it's a 404, you could try hardcoding the NYT IP addy into your HOSTS file and see if that alleviates the problem.)?

It's less likely a problem with the wifi than it is a problem with the different connections.

Maybe the NYT's servers has your friend's ISP blocked for some reason.

are you using a proxy connection, or direct? Can you resolve the address? Can you reach the nyt server? Here's how to check:
For dns, open a cmd window (assuming you're on windows) and type 'nslookup www.nytimes.com'. If that returns, try 'telnet www.nytimes.com 80'. If you get a connection type 'GET /' hit return twice. If that works (you'll get a bunch of html back), then theres a problem with your browser.

are you using a proxy connection, or direct? Can you resolve the address? Can you reach the nyt server? Here's how to check:
For dns, open a cmd window (assuming you're on windows) and type 'nslookup www.nytimes.com'. If that returns, try 'telnet www.nytimes.com 80'. If you get a connection type 'GET /' hit return twice. If that works (you'll get a bunch of html back), then theres a problem with your browser.

Lee - I got a response on the nlookup command, but the telnet didn't work. Thoughts on what that means?

Thanks for any ideas!

Have you checked the spark plugs?