W2K Server - Internet drops only in server

[LP]

Hi everyone. I have the following problem in a network:


- Server: Windows 2000 Server SP 3
- The server is DC
- 4 workstations: 1 Windows 98, 3 Windows 2000
- The access to the internet is made through cable with a router for
distribution.
- The server is used as workstation.

First of all I must apologise for my poor english


About a month ago the network start having problems with Internet access. I
verified that the server was configured like Root Server, and so I deleted
the root key (.) and reconfigured the FORWARD DNS. The situation was
resolved and everything started working fine.

It happens that the access to the internet ONLY in the server started to
have the following problem: I get to open any page and to navigate during 1
or 2 minutes, after that I cannot open anything during another 1 or 2
minutes, then I get online again for a couple of minutes and so on. In the
workstations doesn't exist any internet access problems.

DNS is configured in the following way:
- The workstations search the IP of the server and then they are forwarded
to the router.
- The server is configured in the same way.


Thank's in advance for any help or tip

 

[Kevin D. Goodknecht [MVP]]

In

Hi everyone. I have the following problem in a network:


- Server: Windows 2000 Server SP 3
- The server is DC
- 4 workstations: 1 Windows 98, 3 Windows 2000
- The access to the internet is made through cable with a router for
distribution.
- The server is used as workstation.

First of all I must apologise for my poor english


About a month ago the network start having problems with Internet
access. I verified that the server was configured like Root Server,
and so I deleted the root key (.) and reconfigured the FORWARD DNS.
The situation was resolved and everything started working fine.

It happens that the access to the internet ONLY in the server started
to have the following problem: I get to open any page and to navigate
during 1 or 2 minutes, after that I cannot open anything during
another 1 or 2 minutes, then I get online again for a couple of
minutes and so on. In the workstations doesn't exist any internet
access problems.

DNS is configured in the following way:
- The workstations search the IP of the server and then they are
forwarded to the router.
- The server is configured in the same way.

What does this mean? It is only the DC for DNS?

Thank's in advance for any help or tip

I'm not sure this is DNS but lets start there.
Verify the DC using only its own IP for DNS.
So far as that goes the Win2k machines must only use the DC for DNS, too.
You should run nslookup against the internal DNS server to verify it is
properly resolving names. It is very important that all domain members use
the internal DNS server only, this is not necessary for the Win9x machines.
If the internal DNS server is having problems resolving internet names, you
should verify that the DNS servers it is using as a forwarder are capable of
doing recursive lookups. That means your DNS server forwards the query to
your ISP's DNS, which does the lookup and returns the answer. Also your DNS
server should be able to do recursive lookups using its root hints.

What names are in the DNS search list?
Any name in the search list is appended to all DNS queries, so it should
only have the DNS name of your local domain, this keeps DNS from having to
search a lot of domains before giving the answer.

An unedited ipconfig /all will help us diagnose your problem.

 

[Michael Johnston [MSFT]]

You need to test name resolution first. During the outage, are you able to resolve the name of the website you are trying to reach? You can use the
NSLOOKUP utility to query DNS for this info. Just run "NSLOOKUP" from a command prompt. Then at the ">" prompt, type in "www.yahoo.com" and press
enter. This should return the IP addresses for this website. Verify that the correct answer is returned. Use www.dnsstuff.com on one of the working machines to
figure this out. If you get the wrong answer, update your antivirus software with the latest signatures and scan the box immediately. There are a few viruses that
can cause DNS problems.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[LP]

Sorry about not answering until now but I needed time for learning and
testing. The problem is solved and I want to thank you for your help.
It was really nice from you.

Although I tried several things the answer to the problem was as
simple as using ONLY the IP of the DC for DNS.

Thanks again