I can browse everything from my IE9 64-bit browser (even windows update) and I am starting this question using the same computer I am having trouble with. DNS from a DOS prompt. My RPC service is working correctly (I think). I have no proxies enabled. I get the same result in normal mode or in safe mode with networking. I have run several AV programs but most said no issues and one said it found problems but it was just cookies. I have tried disabling my firewall. IE9 32-bit and anything that connects thru the IE9 32-bit internet connection path doesnt reach the internet. When I try using the diagnostic program that pops up it says my connection is fine. I have tried reinstalling my Winsock, repaired my TCP/IP, and manually added exceptions into my firewall but none of this has helped. I didnt add any new programs, prior to it breaking. I did have Norton but when they tried to help me they had me delete the app and I lost the logs so I dont know what virus initially started this mess. Initially I used system restore to try and fix this but it didnt help. (went back two weeks) Whatever is different between how IE9 64-bit and how IE9 32 bit access the internet is the source of my problem. And other applications that connect the same way as IE9 32bit does also do not access the internet. One caveat to this is uTorrent. I changed an ini file and told the application the ip addresses rather than the DNS name and this worked. UTorrent was then able to access those two servers and downloaded the file I was trying to get. Also, when I ping, or use nslookup from a DOS prompt my DNS is fine. DNS apparently is not being passed to these applications correctly but it is working correctly with my IE9 64 bit browser (no other browser works, not Firefox, Chrome, or Safari. Also when I tried to fix my Asp.net 4.0 the error it gave me was: WinHttpDetectAutoProxyConfigUrl failed with error: 12180 Unable to retrieve Proxy information although WinHttpGetIEProxyConfigForCurrentUser called succeeded I have looked this up what feels like forever and engaged windows support but they wouldnt help me without paying. There has to be someone out there that is smart enough to help me. James Be Yourself, but, Be Your Best Self.

Hi Two things you can try: 1. Disable automatic detection of proxy in Internet Options. 2. Run sfc /scannow from the Command Prompt. Regards Lionel

Sorry did both no luck. Just a heads up however, I downloaded Fiddler2 to troubleshoot the http issue. When I point my IEx86 broswer at the fiddler2 proxy my browser works fine. If I turn fiddler off it stops working again. Why wont my IEx86 browser application pass requests to the internet correctly?Be Yourself, but, Be Your Best Self.

Sorry did both no luck. Just a heads up however, I downloaded Fiddler2 to troubleshoot the http issue. When I point my IEx86 broswer at the fiddler2 proxy my browser works fine. If I turn fiddler off it stops working again. Why wont my IEx86 browser application pass requests to the internet correctly? Be Yourself, but, Be Your Best Self. Try downloading Microsoft Network Monitor, start capturing and try to open a basic HTTP connection. It should give an indication of what's going on. You should see an HTTP connection showing up.MCP Windows Server MCTS .NET

What is the difference between Microsoft Network Monitor and fiddler?Be Yourself, but, Be Your Best Self.

What is the difference between Microsoft Network Monitor and fiddler? Be Yourself, but, Be Your Best Self. Fiddler is a logging proxy, Network Monitor is packet capturing software. You could also try Wireshark. Fiddler acts as a proxy between your browser and the internet, so your browser is making a local connection (so we know that works), and Fiddler is making the connection to the internet. Most likely the connection from IE to Fiddler will not even be using DNS. What I'd like to see is what packets are actually being sent when the connection fails. Is it actually making an HTTP connection? Could you also check connecting to an IP vs connecting to a hostname? As you mentioned, you suspect an issue with DNS resolution. Also try running your browser with add-ins disabled.MCP Windows Server MCTS .NET

I had faced a similar situation long back when I had my ESET AV + Firewall installed and the ESET GUI was removed from startup. ESet(prior to removing GUI from startup) used to give me popups to allow/deny apps from accessing firewall, but since the GUI was stopped from startup, the popups were not shown, at the same time the app was blocked silently. I understand that you may not have installed ESET firewall / any 3rd party firewall, but have you taken a look at Windows default firewall settings. Is the program you are trying to access internet excluded in Windows Firewall Regards Ashok J Prakash If a post solved your problem, click Mark as Answer on the post. If a post helped you, click "Vote As Helpful" on the left side of post.

the network capture didnt help at all because nothing is passed to the network from my x86 browser unless I have fiddler proxy enabled. The Network Diagnostics Framework has completed the diagnosis phase of operation, but no network problem was identified. Be Yourself, but, Be Your Best Self.

Basically I have isolated the issue. The browser is not passing data to the network with out fiddler running. If I turn fiddler off nothing is passed to wireshark network packet capture on the network card. I am guessing someing is wrong with the registry for the x86 browser. Anyone out there smart enough to fix this? Reverting to the base browser in windows 7 and then upgrading/reinstalling IE9 didnt fix the problem. Any help would be appreciated. so far I have been using fiddler for all my applications that wouldnt work before (Microsoft Update, google mail notifier, malwarebytes updates, utorrent, or basically any app that is broken because it uses the x86 internet connection process is fixed by using fiddler as a proxy to the internet. thoughts? Oh and BTW if I leave fiddler running but turn off IE x86 from using a proxy, then the browser stops working again even though fiddler is still running. If I tell IE9 x86 to use a proxy again (fiddler uses 127.0.0.1:8888) the x86 browser starts working. My 64 Bit browser works weather that proxy is running or not. Be Yourself, but, Be Your Best Self.

Hi James Sorry I have no help to offer. I am actually wondering (realizing it's months later) if you had any success? I am having the same problem.