12
5
Update: jump to the end of this question for the happy conclusion to this epic tale.
Note: I have IIS7 installed locally for web development.
This is what happens in my browser for random sites:
That is, a totally gibberish URL resolves to my localhost webserver. (All gibberish hosts do this--not just the one.)
This affects several of us in the company...but doesn't appear to affect all of us.
Here's the troubleshooting I've done so far:
- Checked my proxy settings - all clear
- Checked my hosts file - all clear
- Checked other browsers - it affects Chrome, Chrome Incognito, and Internet Explorer
Ping/nslookup google and a random gibberish url:
C:\Users\mharen>ping google.com
Pinging google.com [74.125.228.98] with 32 bytes of data: Reply from 74.125.228.98: bytes=32 time=21ms TTL=51 ...
C:\Users\mharen>nslookup google.com
Server: (my dns) Address: 192.168.48.20
Non-authoritative answer: Name: google.com Addresses: 2607:f8b0:4004:803::100e 74.125.228.100 ... 74.125.228.98
C:\Users\mharen>ping somerandomsitesoaosoasda.com
Ping request could not find host somerandomsitesoaosoasda.com. Please check the name and try again.
C:\Users\mharen>nslookup somerandomsitesoaosoasda.com
Server: (my dns) Address: 192.168.48.20
*** (my dns) can't find somerandomsitesoaosoasda.com: Non-existent domain
So that is what I would expect--good domains resolve, bad ones don't. So what in the world is screwing with my browser?
Any troubleshooting tips?
Update: ipconfig /displaydns
I just ran ipconfig /displaydns
, which is pretty spiffy. Here's the interesting entry among a few dozen good records:
somerandomsitesoaosoasda.com
----------------------------------------
Name does not exist.
Update: Try new DNS servers:
In case pinging and nslooking wasn't enough to rule out my DNS servers, I followed Joshua's suggestion and switched over to Google's DNS. Unfortunately, the problem persisted.
Update: Fixed!
With help from the answer Joshua linked to, we determined that this command fixed the issue:
netsh winsock reset all
We ran this command before and after to see what it changed:
netsh winsock show catalog
Which revealed 10 entries like this were missing after the reset
command was run:
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry
Description: BarracudaWSA over [MSAFD Tcpip [TCP/IP]]
Provider ID: {FECB95F8-BE34-4B8A-A1ED-16A678A8ACC6}
Provider Path: C:\windows\system32\BarracudaWSA64.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Service Flags: 0x66
Protocol Chain Length: 2
Protocol Chain: 1016 : 1001
BarracudaWSA (Web Security Agent), it turns out, is a web filter installed by IT.
I like Joshua's suggestion of ensuring it's YOUR localhost. Just edit
C:\inetpub\wwwroot\iisstart.htm
, if you don't want to disable your local IIS. – xdumaine – 2013-04-26T15:43:33.137@roviuser it's definitely my localhost. Good idea, though. – Michael Haren – 2013-04-26T15:54:22.783