If nothing has changed but your physical location and your provider I would be tempted to think it was one of those two things. I would call your provider.

It may be that the DNS stuff is different from one to the other. If the old one used a static DNS setup, but the new one requires DHCP (for example), it might lead to this kind of problem. Contact your provider -- but don't mention the router until you know their policy on them!

very good point about the router.. tallcool1... CHECK BEFORE YOU MENTION IT!!!

Did you manage to fix your problem. I seem to be having the same problem. All your infor was useful..

Good advice about not mentioning the router. I did and now the ISP and broadband supplier blames it!.

Please let us know if you resolved it.

Hello,

I would too suggest that it is DNS related. But, unless your new provider is blocking materials on port 53, or the old DNS provider filters incoming requests, the DNS should still work. I run an open DNS on a cable modem, my Grandma who uses dialup across town uses it because her Windows setup refuses to grab DNS from her ISP. Oh well.

But, there was something else you said:

This indicates a problem that is not DNS, unless you have an internal DNS server, and have assigned names to them. This is something else. I wonder if there is something wrong with the NPGear Router. I wonder if your new location has power issues. Don't laugh -- minor power hiccups that are fine to lightbulbs will kill off a computer connection, or cause an issue on the switch. You might want to consider a UPS to eliminate those risks.

What would I do?

I would find some external network address to ping, and I would ping it with a packet sniffer installed. Find out what the packets are doing. This step is beyond the beginner though, but it might give you some ideas.

Good Luck,

Christian

To test your connection, place one of your pcs directly on your modem, instead of the router, your ISP will ask you to do this anyway. Make sure you reboot your machine or reset the IP address information as they sent it to you. Next, do an extended PING to your default gateway like this, PING [gateway IP] -n 100 -l 1500 . the second option is a lowercase L . This will send 100 pings loaded each packet loaded to 1500 bytes. If ANY fail, you have a physical connection problem to your ISP. Next try an standard ping to known sites to test dns: like this PING yourisp.com or PING daniweb.com if dns is working, it will convert the name to the correct IP address and ping the host. If you have trouble ever pinging from one of your local IP addresses to another, it sounds like you have your internal networking mucked up.

Good Luck,

bentkey MCSE,CCNA
Bytewiser Data Systems,

Had the same issue until I followed the following:

Reduce DNS errors in Windows 2000/XP
Windows 2000 and Windows XP come with a "DNS Client" Service that automatically caches (temporarily saves) DNS addresses. This boosts performance by avoiding repetitive DNS lookups of the same address -- the results of a successful lookup (positive response) are saved and reused until the cache expires.
By default the DNS Client also caches negative responses (including the lack of any response from the DNS server). Unfortunately, that can prevent you from recovering from transient DNS errors for an extended period of time. If, for example, the DNS servers at your ISP are temporarily overloaded, or slow to respond due to network congestion, the DNS Client will cache the negative response. Until that cache entry expires, which can take several minutes, it won't even try to lookup that name again -- you'll just get an immediate error. That prevents you from quickly recovering from DNS errors by simply retrying, the recommended thing to do. This can lead to frustrating delays and seeming loss of connectivity problems.
The best way for the typical Internet user to deal with this issue is to disable negative caching, leaving positive caching intact. (Completely disabling the DNS Client is like throwing the baby out with the bathwater because you would then lose the benefits of positive caching.) Negative caching can be disabled by adding three Registry Values (NegativeCacheTime, NegativeSOACacheTime, and NetFailureCacheTime, all not normally present), setting them to zero. Since manual editing of the Registry is a tricky and risky business, I've provided a simple Registry script to do the job. (Click the link to start the download; save the script to your desktop; and then double-click on it to run it. When you get the "Are you sure you want to add the information..." dialog box, click Yes. The script can then be discarded.)
There is no real downside to making these changes -- just delay if you make repeated tries to an invalid Internet name. (Nevertheless, please note that you do this at your own risk, and that it's always a good idea to back up your Registry before making any change.)
To go back to Windows default behavior, simply remove the three Registry Values described above. Since manual editing of the Registry is a tricky and risky business, I've provided a simple INF script to do the removal. (Click the link to start the download; save the INF file to your desktop; right-click on it, and then choose Install to run it. The INF file can then be discarded.)
For a more complete discussion and explanation of this issue, see "Broadband Tip: How to keep DNS Errors from slowing you down!

Note: I did not understand all of the above but............the problem has gone away.

Hi Cyclone,
I am having the same problems the others seem to have. You mentioned a link for a script........it is not in your post. Could you please post that link? Thanks

http://cable-dsl.home.att.net/
This is the area that had that information and much more.