XP DNS resolution, Anyone have an answer yet?

  • Thread starter Thread starter Steve Crandall
  • Start date Start date
S

Steve Crandall

I wrote the subject heading that way because I've come
across several posts with no visible solutions yet.

Here is my story....

I can ping DNS servers by Ip addresses but not by name. My
main problem is not being able to browse the net or
receive e-mail.

Here is a snippet of the results of a ping www.yahoo.com
and a nslookup on www.yahoo.com

***************************Start
Snippet**********************************
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\WINDOWS\SYSTEM32>ping www.yahoo.com
Ping request could not find host www.yahoo.com. Please
check the name again.

C:\WINDOWS\SYSTEM32>nslookup www.yahoo.com
*** Can't find server name for address 192.168.1.33: No
response from server
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.33

*** UnKnown can't find www.yahoo.com: No response from
server
***************************End
Snippet************************************

The 33 address is a firewall/proxy server. Gateway and
DNS settings point to this address and where working on
this laptop before, all other machines on our intranet
have the same settings and work with no problems.

I can browse and access local resources in our workgroup
with almost no problem from this laptop. Most of the time
I can map a drive to another machine by name, other times
I have to use IP addresses.

I have renamed the registry settings for Winsock2 and
Winsock. The Winsock2 key was regenerated on a reboot but
the Winsock key was not. I exported the same Winsock key
from another XP laptop and merged it into the problem
laptop. (I still have the original Winsock key saved) I
also performed the "netsh int ip reset c:\resetlog.txt"
command to refresh the TCP/IP in XP.

However, the main problem still is there. I cannot surf
the web, nor can I get email from this machine.

Thanks in advance for any help/suggestions.

Regards,
Steve
 
Steve,

I posted the same problem on 9/5, and have tried every
suggestion with the same results. I keep seeing this issue
posted, so at least we're not alone...
 
Mark,

I've found a situation that was similar to mine that
provided my much needed solution. There is a post with a
subject "dhcp doesn't work/"not a socket"/renew reset
doesn't either" dated Tuesday September 9th at 7:06 p.m.
that provides some insight to the problem.

After reading the part of the post from Mark Wickes, I ran
the "winmsd" program and checked the protocol section for
any bad entries. I was very suprised to see that it was
blank! According to Mark, if the list is empty you may
have to rebuild the catalog for TCP/IP from scratch.

Following Mark's instructions for rebuilding the catalog
from scratch worked for me. I know have proper internet
access back. Cheers to Mark!

Hopefully this will help you as it did me. Post a message
to this thread if you have a problem finding the
previously mentioned thread or if you have any questions I
might be able to answer.

Good Luck, HTH.
Steve
-----Original Message-----
Steve,

I posted the same problem on 9/5, and have tried every
suggestion with the same results. I keep seeing this issue
posted, so at least we're not alone...
-----Original Message-----
I wrote the subject heading that way because I've come
across several posts with no visible solutions yet.

Here is my story....

I can ping DNS servers by Ip addresses but not by name. My
main problem is not being able to browse the net or
receive e-mail.

Here is a snippet of the results of a ping www.yahoo.com
and a nslookup on www.yahoo.com

***************************Start
Snippet**********************************
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\WINDOWS\SYSTEM32>ping www.yahoo.com
Ping request could not find host www.yahoo.com. Please
check the name again.

C:\WINDOWS\SYSTEM32>nslookup www.yahoo.com
*** Can't find server name for address 192.168.1.33: No
response from server
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.33

*** UnKnown can't find www.yahoo.com: No response from
server
***************************End
Snippet************************************

The 33 address is a firewall/proxy server. Gateway and
DNS settings point to this address and where working on
this laptop before, all other machines on our intranet
have the same settings and work with no problems.

I can browse and access local resources in our workgroup
with almost no problem from this laptop. Most of the time
I can map a drive to another machine by name, other times
I have to use IP addresses.

I have renamed the registry settings for Winsock2 and
Winsock. The Winsock2 key was regenerated on a reboot but
the Winsock key was not. I exported the same Winsock key
from another XP laptop and merged it into the problem
laptop. (I still have the original Winsock key saved) I
also performed the "netsh int ip reset c:\resetlog.txt"
command to refresh the TCP/IP in XP.

However, the main problem still is there. I cannot surf
the web, nor can I get email from this machine.

Thanks in advance for any help/suggestions.

Regards,
Steve

.
Click to expand...
.
Click to expand...
 
We came across this problem 2 weeks ago on an XP Home machine. We tried everything but had no luck. The problem was specific to this machine. The connection worked fine if we plugged a laptop into the same modem

We could ping real IP addresses and get responses. We couldn' resolve any domain names or ping the DNS servers. The same DNS servers were reachable from other machines at the same time this box would fail trying to ping it

After about 20 hours of trying everything we could think of, someone suggested switching out the network card ( to get a new MAC address involved ). Believe it or not, it worked!!

We didn't know why and just were happy to see it working again

Now, the same EXACT problem appears on a different machine. This machine has an ethernet conneciton right in the motherboard, so we installed a NIC and tried using it. No luck; it behaves the same way

Basically, we can do everything we want with IP addresses.... except, ping the DNS servers

I'm considering going back to 2000 since this board seems to be full of people having the same UNSOLVED problem.
 
Did you happen to capture the settings for the network card before it was
subsequently swapped out? It would be very telling on what it's settings
actually were. Both the standard and also advanced settings are important
to view.

Paul.

Ted T said:
We came across this problem 2 weeks ago on an XP Home machine. We tried
Click to expand...
everything but had no luck. The problem was specific to this machine. The
connection worked fine if we plugged a laptop into the same modem.
We could ping real IP addresses and get responses. We couldn' resolve any
Click to expand...
domain names or ping the DNS servers. The same DNS servers were reachable
from other machines at the same time this box would fail trying to ping it.
After about 20 hours of trying everything we could think of, someone
Click to expand...
suggested switching out the network card ( to get a new MAC address
involved ). Believe it or not, it worked!!!
We didn't know why and just were happy to see it working again.

Now, the same EXACT problem appears on a different machine. This machine
Click to expand...
has an ethernet conneciton right in the motherboard, so we installed a NIC
and tried using it. No luck; it behaves the same way.
Basically, we can do everything we want with IP addresses.... except, ping the DNS servers.

I'm considering going back to 2000 since this board seems to be full of
Click to expand...
people having the same UNSOLVED problem.
 
No, I didn't... however, I believe I can reproduce the problem by putting that card back in. If that might help solve this problem, I'd be happy to give it a shot. Seems this same problem is troubling lots of XP users

What network card settings, specifically, are you interested in knowing

I am going to try Steve's suggestion on the second box today. I'll post results here
 
I tried what Steve suggested but had no luck. After re-installing the protocol, I had only two things show up in my 'winmsd' output. One was TCP/IP and the other UDP/IP.

I reset the modem several times. I tried another Network card. Nothing.

I did notice that there were several registry entries for 'NameServer'. Some blank, others filled with the name server IP and still others with invalid IP addresses. Very odd. I didn't have a nother machine to compare the it with though.

I gave up on it when I got call from my brother-in-law. It was working.

According to him, all it needed was a "re-boot".

So, now I have seen two XP Home boxes struggle with this problem and the two solutions were...
1) Replace the NIC
2) Do everything I did above and "re-boot".

I just wish I had more info to offer on this one because, for some reason, I feel I'm going to run across it again and be back here searching.
 
IPCONFIG /ALL would be useful.


Ted T said:
No, I didn't... however, I believe I can reproduce the problem by putting
Click to expand...
that card back in. If that might help solve this problem, I'd be happy to
give it a shot. Seems this same problem is troubling lots of XP users.
 
Back
Top