Ping works fine to an IP address, but fails to resolve to a DNS address


I've seen this a few times as I'm a head technician and the only resolve I've had in the past was a reload of windows.  Thought I'd try and see if anyone else has seen this and found a solution.  

Here is a copy of the command prompt status that may help explain the difficulty of this problem:

C:\Documents and Settings\Nancy>ping

Pinging ► with 32 bytes of data:

Reply from bytes=32 time=343ms TTL=64
Reply from bytes=32 time=169ms TTL=64
Reply from bytes=32 time=168ms TTL=64
Reply from bytes=32 time=167ms TTL=64

Ping statistics for Où♠:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 167ms, Maximum = 343ms, Average = 211ms

C:\Documents and Settings\Nancy>ping
Ping request could not find host Please check the name and tr

C:\Documents and Settings\Nancy>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : nancysputer
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

PPP adapter CWI 56k - Paris:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
        Physical Address. . . . . . . . . : 00-53-45-00-00-00
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . :
        Subnet Mask . . . . . . . . . . . :
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . :
        NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Nancy>telnet 80
Connecting To not open connection to the host, on port 80.
The requested service provider could not be loaded or initialized.

C:\Documents and Settings\Nancy>telnet
Connecting To not open connection to the host, on port 23.
The requested service provider could not be loaded or initialized.

**Where the "Square" is, a symbol of an arrow pointing to the right shows up.

It seems that I've seen this when AOL 8 Plus has been installed on an XP Home version, but I don't know that is the case.

I have reset the IP interface several times with the log showing the below results:

reset   SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{35B1E4A3-BFDC-49A0-84FB-4FA94B269E06}\NetbiosOptions
            old REG_DWORD = 2

reset   SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{B54ADB43-85CB-4E96-AD0C-2D04A5E90386}\NameServerList
            old REG_MULTI_SZ =

reset   SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{B54ADB43-85CB-4E96-AD0C-2D04A5E90386}\NetbiosOptions
            old REG_DWORD = 2

deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{B54ADB43-85CB-4E96-AD0C-2D04A5E90386}\NameServer
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DontAddDefaultGatewayDefault
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpMaxDataRetransmissions
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevolution

**This log didn't seem to look like the others I have done in the past.

Any help would be appreciated as it seems I run into this problem about once every quarter or so.

Thanks guys!

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I'm not sure why the telnet attempts aren't working, but for DNS problems I would try this first:
ipconfig /flushdns
ipconfig /registerdns
blazetaylorAuthor Commented:
Trust me on this, it wasn't a simple DNS problem.  The Application layer on the XP machine wasn't interacting with the lower layers.  The answer to the solution was to delete the winsock and winsock2 entries from the registry, reboot, and install TCP/IP over the top of the TCP/IP that was currently "installed".  Had to point the Install to the "nettcpip.inf" in the windows/inf directory.  That allows TCP/IP to install over the top of the TCP/IP required for operation of Windows XP.

I have used the /flushdns and /registerdns commands to fix quite a few problems, but this was on a home users pc, and it didn't have anywhere to register to;)

Have a great day.  Hope this helps everyone that might run into this problem twice a year;)

If I were you, I would remove the whole TCP/IP stack, including registry and files.
It changes depending on the OS you are using.
Become a Certified Penetration Testing Engineer

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

blazetaylorAuthor Commented:
I've already got it working, but I don't know the process or even know if it's possible to "remove" the TCP/IP stack in Windows XP.

how did you get it working for future reference?
It is not possible to remove tcp from XP, it is considered a core component
but XP does have the netshell command;en-us;Q299357
blazetaylorAuthor Commented:
I used the process to remove the Winsock and Winsock2 key from the registry HKLM-System-CurrentControlSet-Services-(winsock/winsock2).  I removed these keys, rebooted.

After the reboot, I went into the Network Connection Propeties, selected install, went to "Have Disk", pointed it to the %SYSTEMROOT%/inf/nettcpip.inf file and then let it install.  Rebooted, and it all worked.  I tried the netsh command as you read above.  Didn't work, only this worked.

Hope this helps someone else!

Blaze, this was a life-saver. Thanks!

I had the exact same problem of Windows 2000 stuck with a tcp/ip configuration and not accepting my dhcp settings.
... followed your steps word by word and life is better now!


I have been working on a problem XP PC for 2 days straight - 16 hours...  I knew that TCP/IP was trashed, but I couldn't figure out how to fix it.

**** How did you know about the nettcpip.inf file?? How did you find this?? ****

I didn't even delete the winsock keys... I just went straight for the Network Properties Install button. After navigating to the nettcpip.inf file and then when it came back with a choice to install the TCP/IP protocol, I was shocked, to say the least! Everything started working immediately after a reboot!!

Through this whole process, I have come across a few people with the same problem, but no solution. I will now go back and pass this along! Thanks again!
blazetaylorAuthor Commented:
Yeah, I figured it out after allot of researc on the Registry and the INF chain in XP.  It worked once so I thought I'd pay to pass it along.  

Super glad this helped someone else!

Thank you BlazeTaylor

Brilliant! Worked perfectly.

I experienced this same problem just now for the second time on one PC. Last time (8 months ago)  I solved it using the Microsoft Knowledgebase article, but this time it just didn't work.

I am so glad I found this post.

Just another thank you post... had exactly the same problem on a friend's laptop just now and followed the process outlined by BlazeTaylor.

First delete the two keys from the registry:

Reboot. Then go to Network Connections, Local Area Connection, Properties, Install, Protocol, Add, Have Disk, C:\WINDOWS\inf, OK, Microsoft, Internet Protocol (TCP/IP), OK. Once it's installed, reboot again.

Note that unlike HighTechGeek's experience, it did not work without first deleting the Winsock keys.

blazetaylorAuthor Commented:
HAHA... All these "helped" people... and no points. :)

Hope this technical article makes your day better.


I'd give you some points if I could! :-)
I hope you're enjoying the reward of knowing that you helped us all out!
Thanks again!

... and the bringing people help (for no points) Blaze rollercoaster just keeps roaring on.  Like everyone else your method made networking work again.  Many thanks.
PAQed, with points refunded (500)

Community Support Moderator

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.