Windows Forum

Ask something
Discussion Locked

DNS problems

0 helpful
5 replies

by rcdoferreira

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

I have a Win2k DNS server on a network with aproximately
20 PC clients some of them running Windows98 and the
others running windows 2000 pro.
I have a Dial-Up router as my default gateway to the
internet.
The problem is that my DNS connects to the ISP every 5
minutes and stays connected during 1m:40s and then
disconnects himself. I think that the problem has
something to do with primary to secondary SOA record
transfers. This problem occurs even if no one is
connected to theinternet at that time.
I had the same problem in a NT 4.0 server but i solved it
by applying the service pack 6.0. Microsoft has declared
that in Windows NT 4.0 this was a know bug.

Is it the same with Win2K?
Should i apply the service pack 2 for Win2K?
How can i solve this?
Thanks

5 replies

by joseph moore

Irregardless of your DNS problem, you should be running SP2! Plus a few patches past SP2!
The reason for that is the CodeRed virus was propagated by Win2K servers with IIS that did not have a post SP2 patch!
So, load SP2 on your machine now!
Then, get the post SP2 patches.

SP3 for Win2K is out now. I have not had any problems with it for 2 weeks now (since it came out). I am just not entirely sure I like all of SP3's features. The new automatic Windows Update I am not comfortable with. It reports your system information back to Microsoft before it performs its updates. I am still uncertain how I feel about that!

So, run SP2, then get the patches you need after SP2, and see if it happens to take care of your DNS problems.

by jeffrey.williams

We have the same problem on our network. We are one site in a global config. For some reason, our clients lose contact with the local DNS server after 2 hours or so, but maintain contact with our global DNS.
Clients = win2k w/sp2
Server = win2k w/sp2
Our only solution has been to hard-code TCP/IP entries into the Host file. Definitely not a long term fix.

This discussion is closed to new replies.