General discussion

Locked

Intermitt. DNS error IE5.5 & WIN2K Pro 2

By tmanting ·
The problem is I?m getting a ?Cannot find server or DNS Error? in IE 5.5 after a few hours using Windows 2000 professional SP1 when attempting to surf our Intranet. Internet sites are not affected. After I reboot, the problem goes away for a while.
Our Intranet uses a name structure of server.site.organization.org and DNS and WINS is running on one of our NT servers for the entire organization. I put a CNAME record in DNS pointing to the server in question and when I use the alias rather thanthe FQDN WIN2K Pro will browse to the server reliably!
Our network consists of several NT4 servers, a dozen or so NT4.0 workstations and about 60 Win9X PCs and this is the only machine I have this problem with. This leads me to believe this is a problem with WIN2K Pro SP1.
I?ve scoured the Microsoft knowledgebase to no avail. (I?m aware that Win9x had a similar problem that Microsoft has a fix for.) Can anybody help?
(I posted this previously, but I'll try it again for more points...)

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Intermitt. DNS error IE5.5 & WIN2K Pro 2

by TechWhizz In reply to Intermitt. DNS error IE5. ...

Hi,

Sounds like a problem I have seen before with IE. Further details can be found in the MS KB Article Q262981. Basically, the workaround is to add the IP Address of the Server(s) you are having difficulty accessing in the Execptions List in Internet Explorer. I hope this helps.

Regards,

Laurence

Collapse -

Intermitt. DNS error IE5.5 & WIN2K Pro 2

by tmanting In reply to Intermitt. DNS error IE5. ...

Thanks, but that only applies if you are using a proxy server. Nope, no proxy server here!

Collapse -

Intermitt. DNS error IE5.5 & WIN2K Pro 2

by DRDON In reply to Intermitt. DNS error IE5. ...

Check the WININET.DLL. We have found a similar problem. If you "hard code" the IP address of DNS server, it works, but if you you a script to access, it fails most times. It appears to have something to do with the size of the script used. If you "back rev" the WININET.DLL from the original install of Windows 2000 Professional, problem solved too. It is the version of the WININET.DLL from SP1 for WIndows 2000 as well as IE 5.5 that is the suspect in this mess.

HTH- Don

Collapse -

Intermitt. DNS error IE5.5 & WIN2K Pro 2

by tmanting In reply to Intermitt. DNS error IE5. ...

Tried it. Didn't solve the problem...

Collapse -

Intermitt. DNS error IE5.5 & WIN2K Pro 2

by whoiskevin In reply to Intermitt. DNS error IE5. ...

I don't have the solution yet but wanted to share that I have experienced the same problem. Just as a helpful work around I have been successful by simply restarting the dns client on my W2K SP1 workstation.

net stop dnscache
net start dnscache

That seems to make everything work again. Perhaps it is ultimately the .dll issue in answer 2. I haven't tried that yet and since this always takes a little time to reproduce it is slow to find the answer.

Collapse -

Intermitt. DNS error IE5.5 & WIN2K Pro 2

by tmanting In reply to Intermitt. DNS error IE5. ...

Short term solution...

Collapse -

Intermitt. DNS error IE5.5 & WIN2K Pro 2

by MCK In reply to Intermitt. DNS error IE5. ...

Here is one solution that I have found to work rather reliably. First to elaborate on the problem that I am having in similarity to the one listed. I have a network of a 1000+ NT and 95 workstations relying on DNS (both UNIX Bind and NT) to resolve, this works fine, as soon as I introduced a Win2000 workstation, I have a problem. The Win2000 workstations after about two hours will suddenly begin to fail on DNS lookups, although when using nslookup it responds with correct information I am still unable to ping or use aliases that I am sure are in DNS. This problem will occur on both statically assigned and machines using DHCP. This points me to believe that it is a Win2000 problem rather than the DNS servers itself. So considering theproblem only occurs after about two hours from boot I started to look at the "ipconfig /displaydns" output on Win2000 and found that as soon as the first entry in that expired after boot my resolution would fail. It would appear that the client side DNS cache is not able to refresh itself after a TTL has expired without manually flushing the client DNS cache (ipconfig /flushdns) and then reregistering (ipconfig /registerdns).

Now for the resolution that I have put in place. Open up Services on Win2000 Pro and for the service labeled "DNS Client" Stop it and Disable it so that it will not restart after a reboot. If you set this to manual and make any changes within the network settings in regard to DNS it will restart it, so I do recommend disabling it altogether. This should correct the above issue with names resolution. The second change that I would make in this environment is to uncheck "Register this connection's address in DNS" within network settings, this will disable the workstations DDNS ability and stop any unneeded traffic and errors that occur when trying to make an update to an NT4.0 server or Bind system that does not support DDNS.

Collapse -

Intermitt. DNS error IE5.5 & WIN2K Pro 2

by tmanting In reply to Intermitt. DNS error IE5. ...

Perfect. Helped my completely. Thanks!

Collapse -

Intermitt. DNS error IE5.5 & WIN2K Pro 2

by tmanting In reply to Intermitt. DNS error IE5. ...

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums