Wireless works, but wired doesn't?

Soldato
Joined
29 Jul 2004
Posts
6,650
Location
Esher
Hi All,

How rare is it for a computer connected to a Homehub 3 by ethernet cable not work but the wireless aspect does work?

What possible solutions are there?

The server at www.google.co.uk can't be found because the DNS look-up failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network.
Here are some suggestions:
Reload this web page later.
Check your Internet connection. Reboot any routers, modems or other network devices that you may be using.
Check your DNS settings. Contact your network administrator if you're not sure what this means.
Try disabling network prediction by following these steps: Go to Spanner menu > Settings > + Show advanced settings and deselect "Predict network actions to improve page load performance." If this does not resolve the issue, we recommend selecting this option again for improved performance.
Add Google Chrome as a permitted programme in your firewall or antivirus software's settings. If it is already a permitted programme, try deleting it from the list of permitted programmes and adding it again.
If you use a proxy server, check your proxy settings or contact your network administrator to make sure that the proxy server is working. If you don't believe you should be using a proxy server, adjust your proxy settings: Go to the spanner menu > Settings > + Show advanced settings > Change proxy settings... > LAN Settings and deselect the "Use a proxy server for your LAN" checkbox.
Error 105 (net::ERR_NAME_NOT_RESOLVED): Unable to resolve the server's DNS address.

This is the error code that comes up when I connected via wired, and tried to access Google.

I've reset the router a number of times but no joy :(
 
Reset all your network adapter settings, set them all to auto.
Try new drivers.

It is possible, although it's a rare occurance that the port is physically broken.


I'd check in this order...


-set adapter IP settings to auto
-check the cable works!
-try another ethernet port on router
-reset adapter settings
-install new network driver

-reset windows firewall to defaults
-disable any 3rd party firewall

To rule out the port is physically broken, boot a ubuntu live cd and test it in that
 
Last edited:
Just an update, I believe it was done to this DCHP stuff on my router.

I think wires were getting crossed somewhere, because when I was tinkering with that it started working perfectly :o
 
I've seen this recently on someones laptop who had a new HH3. They took it to their friends house and it wouldn't work their either on the lan, but hooked it to another switch and it works fine????
 
Back
Top Bottom