Discussion Locked

Websites timingout when accessing them

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm running a win2000/xp network with DHCP enabled. The way I have set up DHCP is that the clients access the 2 domain controllers for their DNS resolving and if they cannot do it then the DC's forward it on to our ISP to resolve. This works 99% of the time but I have found that there are certain sites (www.hp.com www.adobe.com www.kodak.com to name a few) which always time out when I try and access them. I do have a firewall but on doing a tracert at the cmd prompt it doesn't even seem to get anywhere near the firewall to get outside, and there is nothing on my firewall logs. Also seem unable to ping these sites. However, if I plug a laptop directly into my router and point it at the ISP for dns resolving then I am able to reach these sites.

Would appreciate any and all help you can give!

6 replies

by sgt_shultz

I searched support.microsoft.com by 'Windows 2000' "slow DNS" (all the words) and got a few hits of interest. below is snippet of one. browsing the hits makes me want to ask you:
what is in the event logs on each computer?
what service pack is each computer (esp. win3k) on?
the problems referenced below are supposed to be fixed in win2ksp4.
from mskb 812785

Slow Response Times Occur If a Delegated Name Server Is Down
View products that this article applies to.
SYMPTOMS
In a delegated DNS environment with more than one name server per delegation, unexpected delays and additional network traffic may occur when names are being resolved. The delay occurs only if the first name server that is listed for the delegation is down or is unreachable. You can see in a network trace that the DNS server is sending all request to the first name server that is listed in the DNS snap-in.
CAUSE
The DNS server does not correctly update an internal table with the response times for the remote name servers.
RESOLUTION
Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

by richardhoughton

All machines have the latest service pack on - Windows 2000 SP4 and XP SP1a. In addition to this all machines are also kept up to date automatically with patches so I can't see it being this that is causing an error.

I've looked in the event log on the client when it tries to connect and nothing is registered when you try and connect. On the servers again no DNS errors for at least a week so nothing seems to be registering there either....

Must admit I don't have too much experience of DNS so it might be something daft that I haven't done???

by richardhoughton

All machines have the latest service pack on - Windows 2000 SP4 and XP SP1a. In addition to this all machines are also kept up to date automatically with patches so I can't see it being this that is causing an error.

I've looked in the event log on the client when it tries to connect and nothing is registered when you try and connect. On the servers again no DNS errors for at least a week so nothing seems to be registering there either....

Must admit I don't have too much experience of DNS so it might be something daft that I haven't done???

by richardhoughton

I think I have managed to make progress on my own on this one but not sure how I can cure it. From doing a few name lookups on the websites I'm struggling to access they all have the format 192.x.x.x
What I'm thinking is that my dns servers are detecting these addresses as internal ones... how can I check this and if so stop it?

by richardhoughton

Thanks for the suggestion - wasn't really helpful anyway we managed to solve it ourselves.

Turned out our scope on DHCP was set to 192.x.x.x and not 192.168.x.x in addition to this our subnet mask was also 255.0.0.0 instead of 255.255.255.0. So for any internet site which was 192.x.x.x it was looking internally.

Re setup scope to fix the settings and rolled it out - fixed the problems. Just beware that some printers might need restalling since the subnet has been changed!

This discussion is closed to new replies.