Dns resolver problem in XP Pro

[NetGear]

Hi,

I have a problem with dns name resolution. When I boot a new laptop, I can
immediately reach the dns servers by their ip address But when I try to
ping these servers by their names there is a few minute delay before the dns
servers respond to the ping request. Obviously the web browsing is quite a
difficult during this delay.

The laptop has a private static ip address and the dns servers host AD
intergrated forward lookup zone with non-secure updates allowed. The laptop
does not log on to domain. It also does not register its name to AD
integrated dns zone.

I have upgraded the Marvell Gbit NIC drivers and I did reset the XP tcp/ip
stack also. I have tested the machine in three different locations where the
other computers work well.

Could it be a hardware related problem?

 

[Lanwench [MVP - Exchange]]

Hi,

I have a problem with dns name resolution. When I boot a new laptop,
I can immediately reach the dns servers by their ip address But when
I try to ping these servers by their names there is a few minute
delay before the dns servers respond to the ping request. Obviously
the web browsing is quite a difficult during this delay.

The laptop has a private static ip address

Why static?

and the dns servers host AD
intergrated forward lookup zone with non-secure updates allowed. The
laptop does not log on to domain.

I presume you mean, it's not joined to the domain....

It also does not register its name
to AD integrated dns zone.

You can try ipconfig /registerDNS

I have upgraded the Marvell Gbit NIC drivers and I did reset the XP
tcp/ip stack also. I have tested the machine in three different
locations where the other computers work well.

Could it be a hardware related problem?

Could be, if it's not working anywhere

Check your event logs.... you might also post an unedited ipconfig /all from
this PC and from your DC.

 

[Steven L Umbach]

Also try using nslookup to see what it shows for DNS servers and how fast
names resolve using nslookup. Try removing the entries for DNS server and
replace it with 4.2.2.2 [a Verizon DNS server] to see what happens. How are
the ping requests to other computers on the network and to internet IPs such
as 4.2.2.2 ?? You might try to go into the properties of the network adapter
and change the network speed from auto to 100 full duplex or vice versa to
see what happens. I would also try booting into Safe Mode with networking
[maybe do that first] to see what happens. If it works better in Safe Mode
with networking some startup/logon application/process is causing the
problem. Winsockfix may be worth trying if none of the above helps though I
would do a System Restore point before running it just in case..


http://www.softpedia.com/get/Tweak/Network-Tweak/WinSockFix.shtml ---
Winsockfix

Steve