DNS Problems with W2K

  • Thread starter Thread starter Harry Maddur
  • Start date Start date
H

Harry Maddur

Hi,

We have a Windows 2000 Client which is unable to resolve
the IP addresses on the Internet.

I am using Explorer 6.0 and have no problems accessing any
Wed Sites when i use a Dial Up connection.

When i use my LAN connection (with DSL) i am having a
problem accessing external Web Sites. The search times out
with a DNS error after 30 Secs. For example i cannot
access www.yahoo.com but can access it's actual IP address
(66.218.71.87). It looks like i am having a name
resolution problem in DNS specific to this client.I am not
sure what files have been corrupted or missing. It had
been working for the last 1 year with the same settings
but is not working since i applied the Patch from
Microsoft to prevent the MSBlaster Virus.

All our other Windows 2000 Client machines have no
problems accessing the Internet with the same settings.

Let me know how to fix this W2K machine to resolve this
problem.
 
Have you done ipconfig /flushdns and registerdns. Where is the client
pointing to for DNS. Can you ping the local DNS server by name and it return
the FQDN? Can you telnet to your dns servers IP address on port 53 (example:
telnet 192.168.1.1 53), can you telnet to 4.2.2.1 53 and get a blank screen
Is the DNS client service running? Can you provide a ipconfig /all. Can you
nslookup from the client.
go to command prompt
type nslookup
(what is the first thing listed)
then type set type=all (hit enter)
then type yahoo.com
What does it return
 
We have a Windows 2000 Client which is unable to resolve
TIM ROBERTS said:
Have you done ipconfig /flushdns and registerdns. Where is the client
Click to expand...

Interesting suggestion, especially since FlushDNS and RegisterDNS
are completely separate and unrelated command (except that they
have SOMETHING to do with DNS.)

Flush might be useful with this problem; Register is (totally) irrelevant.

Below are a bunch of good suggestion though:
 
Had exactly the same problem and after days of trying to
resolve I was fed up and unplugged (from the wall) the
computer. guess what? On restarting everything was
working. This also occured after applying update. Give it
a try.
 
Back
Top