Ok, I am the end of the thether with this. I can NSLOOKUP names but PING and TRACERT can't resolve names. WINS names work from PING and TRACERT but not DNS names FQDN's. Tried different drivers, the netsh int tcp set global autotuninglevel=disabled trick but no luck. How the hell do you change the BG color back to transparent in this WEB news reader from MS? Any ideas? Please help.

Found that it is IPv6, dunno how to uninstall it because disable in the network card settings does not solve it. PING -4 www.microsoft.com worked, but without the -4 there is no luck.

Did the disabling IPv6registry change fromhttp://www.microsoft.com/technet/community/columns/cableguy/cg1005.mspx, can see that all IPv6 stuff is gone from IPCONFIG /ALL. But still PING and TRACERT needs -4 to resolve names, not to mention that IE7 can't resolve the names either.

Screw this, I added a proxy in IE7 and at least that is working, maybe I can gert some updates now from MS thart fix this.

Ok, downloaded 2 updates but that did not fix it. Seems like the default name resolution in Vista is trying to do IPv6 resolution and if that fails you are stuffed. This sucks big time.

glad its not just me thats having this issue.I've unticked IPV6 from the TCP/IP Properties also so nothing should be relating to this.The only thing that seems to clear it is a net stop & net start of dnscache. It works for a little while then goes again.So created a batch file to run whenever it happens.hope this helps

I'm having a similar issue in XP, except that doing a net stop/start doesn't help at all.From what I've found on google, under the circumstances you describe, permanently stopping dnscache should fix the issue.I'm still stuck though. I guess I'll keep looking...

Did you find a solution to this? I seem to be having this problem now and haven't had much luck finding a working solution.

net stop dnscache worked for me.

yes this done the trick for me. the dnscache service is permanently disabled and ping, tracert are fine with name resolution. dnscache works fine for me in xp, but not vista. might be worth disabling it in xpto see if it had any effect.

it's said that when ping or tracert or ie-browse, sometimes,the package sent is not DNS but netbios, which results failure. so to solve this problem, you should force the system to send DNS package.anybody knows how to?

KingMario wrote: it's said that when ping or tracert or ie-browse, sometimes,the package sent is not DNS but netbios, which results failure. so to solve this problem, you should force the system to send DNS package.anybody knows how to?you are very right!I use Microsoft network monitor to capture net packages, found that, It id not send DNS packages, but BetBios packages.Anybody knows why?Thank you!

Got the same problem here, on the network it looks like the name resolving is only using NetBios. Saw some LLMNR packets every now and then but they contained no query name like on netbios. It does contain 22bytes of data but I cannot recognize a name in it.On the icon for the network is states "access local network only", tried all what I could find in the forum about that., no luck so far.What is working? - local networking, netbios over tcp - nslookup is resolving internet names- all other systems on the same network, vista , xp and linuxWhat is not working?- all programs wich relay on name resolving, ping, traceroute IE email etc.Helpdesk vendor does not know what else except for reinstalling every thing. All network software is reinstalled and checked on version. Microsoft helpdesk does not take action, stating responsability is at vendor, has to do with network adjustments of vendor.Checked some parameters in the registry, at least the ones I understood, found those in the knowledge base.It cannot be possible we have to reinstall all sw when there is a clearly describable problem? Any one a solution / suggestion??Running windows vista home premium service pack 1 on a sony vio vgn-nr31

I proposed mgibson85's post as the answer with the notion that dnscache is permanently disabled. This is the only thing that worked for me. I could have attempted to rejoin the domain which fixed this issue on another computer. But some services, such as Certificate Authority, will not allow the computer to be unjoined/rejoined to a domain. So thank you very much for this answer! Disable dnscache permanently worked wonders!

Ok, I think I figured it out. This is what happened to me: I was using Windows Server 2003 SP1. Then I upgraded to SP2 and that is when the problem first appeared. I tried everything and the following is what actually worked for me: 1. Download the following and install NOTE: DO NOT RESTARTWindowsServer2003-KB951748-x86-ENU.exe 2. Download the following and installhttp://support.microsoft.com/default.aspx/kb/299357/ 3. Restart now Notes: I do not have ipv6 enabled I am using opendns IP addresses as DNS servers Any additional questions are welcome.

I was having the same issue, but wasn't able to resolve it using any of the methods discussed here. I finally found a post somewhere that mentioned a MS security update to the DNS client (KB 94553). Although this update wasn't the culprit, it had been functioning for almost a year with this update installed, it did point me to the files that were the problem. It looks like one or both of the files in this update (dnsapi.dll, dnsrslv9.dll) had been corrupted.I uninstalled the update and it corrected the issue with the ping name resolution.I hope that this helps someone in the future.J

I was having the same issue, but wasn't able to resolve it using any of the methods discussed here. I finally found a post somewhere that mentioned a MS security update to the DNS client (KB 94553). Although this update wasn't the culprit, it had been functioning for almost a year with this update installed, it did point me to the files that were the problem. It looks like one or both of the files in this update (dnsapi.dll, dnsrslv9.dll) had been corrupted. I uninstalled the update and it corrected the issue with the ping name resolution. I hope that this helps someone in the future. J In case anyone was wondering, the correct KB for this was 945553, it was missing a 5 so I had to look and track it down. This worked for me in a case where a network card died and a huge number of other fixes (winsock xp fix, tcp/ip repair, nbtstat refresh, net stop dnscache etc) didn't help the problem of not being able to ping external dns names when I could ping internal hosts by name. Thanks JE7383 for finding this update. You can navigate to C:\WINDOWS\$NtUninstallKB945553$\spuninst\ and run spuninst.exe to remove the update.

I was having the same issue, but wasn't able to resolve it using any of the methods discussed here. I finally found a post somewhere that mentioned a MS security update to the DNS client (KB 94553). Although this update wasn't the culprit, it had been functioning for almost a year with this update installed, it did point me to the files that were the problem. It looks like one or both of the files in this update (dnsapi.dll, dnsrslv9.dll) had been corrupted. I uninstalled the update and it corrected the issue with the ping name resolution. I hope that this helps someone in the future. J In case anyone was wondering, the correct KB for this was 945553, it was missing a 5 so I had to look and track it down. This worked for me in a case where a network card died and a huge number of other fixes (winsock xp fix, tcp/ip repair, nbtstat refresh, net stop dnscache etc) didn't help the problem of not being able to ping external dns names when I could ping internal hosts by name. Thanks JE7383 for finding this update. You can navigate to C:\WINDOWS\$NtUninstallKB945553$\spuninst\ and run spuninst.exe to remove the update. Just wanted to thank everyone involved with this thread, this lead to to the fix for the aftermath of a terrible malware infection! Uninstalling the KB or disabling DNS Cache was not the solution for me, but replacing the dnsapi.dll, dnsrslv9.dll files using ones from the SP3 cab files did the trick!

Hi, I have this problem now, and I tested to uninstall kb951748, restart the machine Windows 2003 SP2 and there are no problem now, working fine. I tested installing the kb951748 and it working fine.