Problem: nslookup succeeds, tracert fails

  • Thread starter Thread starter Mark Olbert
  • Start date Start date
M

Mark Olbert

Every morning when I turn on my client XP machine I am unable to access any of the development
ASP.NET websites on my Win2K server. In other words, browsing to them all return the Page Not Found
error.

When I open a command window on the client and run both nslookup and tracert I get the following:

C:\Documents and Settings\Mark.MAKEITSO>nslookup scef.arcabama.com
Server: maestro.arcabama.com
Address: 192.168.1.200

Name: scef.arcabama.com
Address: 192.168.1.153


C:\Documents and Settings\Mark.MAKEITSO>tracert scef.arcabama.com
Unable to resolve target system name scef.arcabama.com.

Can someone explain to me how in the world nslookup can succeed but tracert can't find the
system?????

God I hate Windows servers.

- Mark
 
Hi Mark.

I mention that because even if you are not using dhcp in your network, the dhcp
"client" service will still need to be enabled/started on your computers or you may
have dns name resolution problems as explained in KB article. For some reason that
service is needed for it. --- Steve
 
Steven,

Okay, thanx, that makes sense. BTW, I checked, and both the client and the server have the DHCP
client service running.

One other thing I noticed over the last day: the problem occurs after the intranet sites have been
"idle" for a few hours (i.e., not been accessed). Suddenly they become inaccessible again.

But if I do a ipconfig /registerdns on the command line, they instantly become accessible again.

Any thoughts about why that should happen?

- Mark
 
I had a problem on my laptop one time where I had the D-link wireless adapter
configured via the D-link software to use power saving mode and experienced somewhat
the same thing where my connection would die after being idle until I finally
disabled the power saving setting. I believe I have heard other people mention
similar problems, so you may want to check any power settings in client software, XP
power management, and maybe even the computer cmos. Also check your network adapter
properties and try disabling any autosense for network speed and set it as 10 or 100
as appropriate. I don't know why the ipconfig /registerdns works as registering your
ip address in the dns zone [or attempting to register] as it should not matter for
proper dns name resolution of another computer. It must have some sort of refreshing
effect of your network connection. Ipconfig /displaydns and ipconfig /flushdns can
also be useful in seeing what is going on with dns name resolution on a client. ---
Steve
 
Back
Top