Try this
Inside Chrome click onon the Far right side on the toolbar
Select Settings.
Click Show advanced settings.
In the "Network" section, click Change proxy settings. This will open the Internet Properties dialog.
Click LAN settings .
Deselect the "Automatically detect settings" checkbox.
Real life is keeping me busy. I still do not have much time to spend on these forums... so I've not re-read every post in this thread - forgive me if this has been asked/answered:
Can other devices (laptops, cell phones...) work on this network?
I'm looking for something to backup Firefox's claim that it is not using a proxy to get out of your network. I know that there is not normally a proxy in a home network, but that is how this computer is acting.
WDO has it's own OS and it could not get to the internet from your network... I just don't know if WDO attempts to read network settings from the OS that it is checking. Maybe others in this thread can suggest an operating system that you can download and run from a CD or DVD... I would suggest Ubuntu or Linux Mint, but both of those can also install from the CD/DVD if you click the wrong option. Maybe there is a portable version that has no risk of formatting the drive of the host computer.
Changing the internet settings proved moot, unfortunately. Same error.
Phones and directly connected computers do work on this network. I tried using a direct connection but that didn't change anything.
It doesn't make sense that only FireFox can connect after all this. Maybe the solution lies in figuring out what Skype, FF, GoogleTalk and uTorrent have in common with regards to connecting to the internet. Those are the only programs I've tested so far that work.
Does that mean that other computers (when connected via your Tellus box) also have this problem?
I installed GoogleTalk into a Virtual Machine and then lied to the Operating System's Internet Properties Connection tab by telling it that I was behind a proxy. Process Monitor showed GoogleTalk attempting to resolve addresses via the bad proxy info, but then it timed out and tried a direct connection. It worked via the direct connection. My guess is that uTorrent does much the same thing.
Installed Chrome into that same VM and what it does is just weird. It tried the direct connection (no proxy) first and it did not get a reply (for reasons unknown). Then it tried the fake proxy and timed out - but Chrome was able to state that it was unable to connect to the proxy server (much like the proxy feedback that IE10 gives).
BTW, I have the DNS service turned off during these tests because that forces each application to try and resolve web addresses to IP addresses. It is easier to watch the network traffic on an app by app basis. When the DNS service is turned on, each app asks the DNS service to resolve web addresses... so all DNS requests come and go thru one of the svchost processes.
Edit: I reverted the VM back to IE8 to see if Chrome was using any part of IE10 to determine if the connection problem was proxy related. (The OP has IE9. IE8/IE9 do not seem to know/give specific info about the proxy failing to respond). Chrome was still able to tell me that the fake proxy was not responding... so it does so using it own diagnostics.
The OP is not seeing this type of error in Chrome - so maybe proxy settings are not the issue.
Last edited by UsernameIssues; 15 Jul 2013 at 14:41.
Quote
