Discussion Locked

Random DNS problem on Win2k Pro

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

I have 3 computers on a small network in my home using a Linksys router to share my cable modem connection. For the most part, everything works fine, except that on my two Win2k PRO machines (my win2k server is unaffected) I'm having problems with DNS. For some reason, at times the machines will stop connecting to the DNS servers. This happens randomly, sometimes not for a couple days, sometimes every couple hours. Services like Instant Messanger, mIRC, and FTP/HTTP to a direct IP address work fine but it will stop resolving the names so I'm unable to get to websites the normal way. Rebooting the machine solves the problem until it randomly does it again. I checked my Event Logs and the message is listed below:

Event ID: 11050
Source: dnscache
Message:
The DNS Client service could not contact any DNS servers for a repeated number of attempts. For the next 30 seconds the DNS Client service will not use the network to avoid further network performance problems. It will resume its normal behavior after that. If this problem persists, verify your TCP/IP configuration, specifically check that you have a preferred (and possibly an alternate) DNS server configured. If the problem continues, verify network conditions to these DNS servers or contact your network administrator.

There really doesn't seem to be a rhyme or reason to when/why it's doing this. If anyone has had this problem and can suggest a solution I would really appreciate it. Thank you.

15 replies

by cportman

Do you have your clients pointed at your Server's DNS or your ISP's DNS?

I have same DSL router and it works fine when clients point at my server's dns.

cp

by jbuys

The router acts as a DHCP server and all 3 machines are using that to grab the DNS server from my ISP.

by cportman

The clients are probably trying to register themselves in DNS and since your ISP most likey is rejecting their request, they are thinking there is some networking problems.

by jbuys

By why would it work some of the time and then randomly stop working at other times?
FYI - I've tried letting it obtain DNS server settings automatically, explicitly typing in my ISP's DNS servers, and using other DNS servers.
All have the same problem

by lordinfidel

I have noticed that win2k, even though it is rooted in dns, some times blows up and stops resolving names.

I beleive this is happening because the resolver cache is saying hey, look at me first and then does not want to continue looking further.
Instead of rebooting, try this command. It works every time for me.

Open a command prompt (start/run/type cmd/run)

In the command line type the following

ipconfig /flushdns

This will flush the local dns cache.

Then try going to thesite. The reason it works after a reboot is because the cache is flushed automatically on shutdown.

Hope this helps.

by lordinfidel

Before I forget:

You said that you have a local lan. Is your 2K server the gateway for the network.

And how do you have everything set up? Is this an AD domain and your DC is multihomed?

If so this can be a source of confusion for your clients.

by lordinfidel

----------------

There is a way to turn this off. (dns caching)

Go to services on the local machines and choose the DNS client service. Go ahead and stop it and then disable it. That will stop the machines from trying to cache names.

by jbuys

Tried all of that.. Tried replacing the network cards/cables... nothing. I've tried everything I can possibly think of but it still does it... and also now randomly boots me completely.

The only other thing I can think of is that when they installed the cable, they used a bad/weak splitter and since the cable runs up through the attic, the attenuation might be making the signal drop occassionally

by lordinfidel

Here it what I believe is happening.

I am going to go out on a limb and describe your network.

You have 3 machines. 1 server and 2 clients.

The server is handing out DHCP address'. (Question: what address' is it handing out?, it needs to be pvt address')

It is pointing DNS to your ISP's DNS.

The issue here is routing. Your clients can not route out past your server to get out to the public net.

If you are using pvt IP's on your side and your ISP has 1 public address assigned to you. You will have to ask yourself, How are my clients supposed to talk to the public net if they are unable to route to it. (Pvt IP's are non-routable)

There is a solution to this, and if you have 2K server it is easy. You will need to install routing and remote access on the 2k Server and you will need 2 nics.

1 Nic goes to your router, the second is for your pvt network that is connected to a hub.

Point all clients GW to the PVT interface of the server.

On the server side you need to specify in RRA, to forward requests from the Pvt to public. You will also need to install NAT (network address translation), It is in the RRA.

If you have NT4 server, the solution is different, because you will need proxy server.

I highly doubt that it is due to attenuation.

by jbuys

My network configuration is as follows. I have 3 PC's. Two run Win2k Pro, the other Win2k Server. The "server" doesn't really do much at the moment except run a few websites and an FTP site.
All 3 machines connect to a Linksys router whichis connected to my cable modem. The router uses NAT and functions as my gateway and DHCP server, assigning IPs to all 3 PC's on the network.
As for network settings... I've tried setting the machines to use DHCP to get all the settings (as the router manual instructs)... I've tried manually typing in my ISP's DNS servers, using public DNS servers, spoofing the MAC address on the router, disabling the DNS client...
An attenuation problem does seem extremely unlikely but I'm running out of ideas.

by lordinfidel

Do this test...

Fire up all 3 systems, set all 3 clients up to receive DHCP.

Open up a command prompt on each machine,
(start/run type cmd press enter)

Type in ipconfig on each machine.

What is the IP address of each client; are they the same or different?

Do they have an IP adress in one of these 3 networks 10.x.x.x, 172.16.x.x or 192.168.x.x.

If it is something other than those 3 address, then DHCP at your router is not giving address properly. To test this type:
ipconfig/release_all at the prompt (enter)then ipconfig /renew_all (enter)

Then type in ipconfig. Did the address change?

I have not worked with a linksys router before. But I would double check the DHCP scope on it.

Another way to do this, especially if you are interested in learning 2K. Is to setup your 2K server as a router. It is pretty easy to do using the methods above.

Take a look at the following post that I gave someone else so you can get an Idea of how to set it up.

https://www.techrepublic.com/forumqa/thread_detail.jhtml?thread_id=65251

Instead of 3 nics in the router, you would need only 2.

I would definitely look long and hard at the router configuration. That is the source of your woes.

by jbuys

The router assigns the computers with IP's in the scope of 192.198.1.10x

Everything works fine for the most part... I even have port forwarding enable for my web/ftp servers.

The only problem is that, at random intervals, it will stop resolving DNS names and/or boot me offline completely... sometimes not for days.. other times, every hour or so.

I've suspected that it was the router for a while but the settings seem fine and everything looks normal... which is what led me to believe that it might be a NIC/cable/attenuation problem.

I'm really at a loss on this one.. I've never seen anything like it.

I might be replacing my LinkSys router with a Linux box to serve as a router and to connect to a VPN for work so maybe that would solve the problem.

by lordinfidel

Did you mistype the pvt subnet of 192.198.x.x

The 192.198.x.x is not a valid pvt subnet.
That is a public subnet.

RFC1918 defines the 3 valid pvt subnets as
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

If you want to take this offline, you can e-mail me at mmorell@vdat.com

Let me know what version of linksys router you have and I can see if there are any online docs for it.

by jbuys

As far as I can tell, the problem was with my Linksys router. It doesn't like to function as a DHCP server if you have port forwarding enabled. I set static IP addresses and it works now. It still drops the connection every once in a while but it's only for a second or two and I suspect that has something to do with Road Runner.

I'm awarding the points to LordInfidel since he was the most helpful

This discussion is closed to new replies.