Cant connect to internet via Ethernet,plz help!
Cant connect to internet via Ethernet,plz help!
Author
Discussion

kowalski655

Original Poster:

15,237 posts

174 months

Tuesday 8th January 2019
quotequote all
Hi, hoping(REALLY hoping!) that PH can save my sanity.
I have a Win10 desktop connecting to a Plusnet Router via ethernet(as router is at main BT socket that some idiot put upstairs!) 2 other PCs connect no problem via ethernet, mine wont, no matter what
I have tried, in no particular order:
Resetting router(just as my son was about to win a game of Fortnite-he was NOT happy smile)-Win10 diagnostics say that "Ethernet has no access to gateway
Setting DNS from auto in IPv4 properties to the fixed +Net one, Win10 diagnostic says "Default gateway is not available"
ipcongfig/flush & renew
turning off net card's ability to turn off PC in power management
Unplugging & resetting all the ethernet adaptors
Swapping plugs for my adaptor
swapping cables to the adaptors
Connecting via +Net wifi-same results
Connecting via EE mobile hotspot-that gets me online now
ETA:reset drivers from list on PC
Disabled/re-enabled ethernet device
deleted ethernet device to get W10 to recognise it
And probably a few others that I have forgot about
Next step is to take a hammer to it biggrin
+Net say its all right on their end, guy not able to diagnose my PC obviously but went as far as he coul, he did mention that its odd DHCP didnt show up in the wifi section of IPconfig
So Im really really hoping the IT gurus of PH can point me in the right direction before I go crazy at the lack of decent internet
Thanks all


ETA to add a few more things I remembered


Edited by kowalski655 on Tuesday 8th January 15:19

LordGrover

34,189 posts

243 months

Tuesday 8th January 2019
quotequote all
What is the default gateway, and is it the same as other computers?

IP and mask would be useful too.

kowalski655

Original Poster:

15,237 posts

174 months

Tuesday 8th January 2019
quotequote all
IP Address is 192.168.1.69
Subnet mask 255.255.255.0
Default gateway is 192.168.1.254
Preferred DNS server is 212.159.6.9
Alternative DNS is 212.159.6.10

These are the ones I set the IPv4 ,info from the +Net forum IIRC


Freakuk

4,882 posts

182 months

Tuesday 8th January 2019
quotequote all
So your PC is getting an IP address, can you ping anything i.e. an IP address and a URL?

Feels like a DNS issue...

Lemming Train

5,567 posts

103 months

Tuesday 8th January 2019
quotequote all
Your post is too rambly and confusing. Too clarify : have you connected the non-working PC direct to the master socket with a known to be working ethernet cable from one of your existing PCs? Is so then disregard this post. I mention it because I went through exactly the same as you and after several days of head scratching and troubleshooting it turned out to be the ethernet cable

kowalski655

Original Poster:

15,237 posts

174 months

Tuesday 8th January 2019
quotequote all
Freakuk said:
So your PC is getting an IP address, can you ping anything i.e. an IP address and a URL?

Feels like a DNS issue...
Thats what I set the ethernet adaptor to following a forum post.When I pinged it in cmd box there was no response,75% packet loss

LordGrover

34,189 posts

243 months

Tuesday 8th January 2019
quotequote all
kowalski655 said:
IP Address is 192.168.1.69
Subnet mask 255.255.255.0
Default gateway is 192.168.1.254
Preferred DNS server is 212.159.6.9
Alternative DNS is 212.159.6.10

These are the ones I set the IPv4 ,info from the +Net forum IIRC

Are your other computers on the same subnet, using the same gateway?

i.e. 192.168.1.?

...and not 192.168.1.69!

Harpoon

2,551 posts

245 months

Tuesday 8th January 2019
quotequote all
Can you ping the default gateway (router) from the PC?

If not, can you put another PC on the end of the same cable and re-test (pinging the router)?

kowalski655

Original Poster:

15,237 posts

174 months

Tuesday 8th January 2019
quotequote all
Lemming Train said:
Your post is too rambly and confusing. Too clarify : have you connected the non-working PC direct to the master socket with a known to be working ethernet cable from one of your existing PCs? Is so then disregard this post. I mention it because I went through exactly the same as you and after several days of head scratching and troubleshooting it turned out to be the ethernet cable
I have swapped the cables from the adaptors upstairs around-no joy
To try to clarify graphicallyfrownjust ignore the dots
original..
PC1 ............. PC2 ............ PC3(dud)
| ...... .......... | ................ |
wall ......... wall .............. wall

wall ............ wall ............. wall
| ... ................ | ....................... |
Port 1 ........... Port 2 ........... Port 3

Repair attempt
PC1 ............. PC2 ............ PC3(Still dud)
| ...... .......... | ................ |
wall ......... wall .............. wall

wall ............ wall ............. wall
| ... ................ | ....................... |
Port 1 ........... Port 3 ........... Port 2

Funk

27,807 posts

240 months

Tuesday 8th January 2019
quotequote all
OP: on the PC that won't connect - check Control Panel > Internet Options > Connections Tab > LAN settings > ensure 'Automatically Detect Settings' is unchecked.

This setting being ticked has, in the past, caused the same issues for me as you've mentioned in your post.

Penelope Stopit

11,209 posts

140 months

Tuesday 8th January 2019
quotequote all
Have you tried it with your firewall disabled, I may not be close

kowalski655

Original Poster:

15,237 posts

174 months

Tuesday 8th January 2019
quotequote all
Lemming Train said:
Your post is too rambly and confusing. Too clarify : have you connected the non-working PC direct to the master socket with a known to be working ethernet cable from one of your existing PCs? Is so then disregard this post. I mention it because I went through exactly the same as you and after several days of head scratching and troubleshooting it turned out to be the ethernet cable
As above I have wapped cables at the router end. I didnt swap the cable at the PC end but just did-no connection still frown
LordGrover said:
Are your other computers on the same subnet, using the same gateway?

i.e. 192.168.1.?

...and not 192.168.1.69!
I tried to ping 192.168.1.69 from sons PC,it was not available,100% packet loss.
His ethernet card uses the"find automatically" option
Harpoon said:
Can you ping the default gateway (router) from the PC?

If not, can you put another PC on the end of the same cable and re-test (pinging the router)?
What would be the router address to use?
Cant drag another PC im afraid

Harpoon

2,551 posts

245 months

Tuesday 8th January 2019
quotequote all
The default gateway from your post above is 192.168.1.254

Funk

27,807 posts

240 months

Tuesday 8th January 2019
quotequote all
Funk said:
OP: on the PC that won't connect - check Control Panel > Internet Options > Connections Tab > LAN settings > ensure 'Automatically Detect Settings' is unchecked.

This setting being ticked has, in the past, caused the same issues for me as you've mentioned in your post.
Kowalski, did you check this yet?

kowalski655

Original Poster:

15,237 posts

174 months

Tuesday 8th January 2019
quotequote all
Apologies for delay,I was trying a different cable at PC end(no joy) & stopping AV(Win Defender only) that caused a restart. Turning it off made no difference frown
As to the LAN settings,from Control Panel I can only find "Proxy" that offers the option to turn off-it is turned off.
Also turned off in Chrome
But still no internet-when connecting via ethernet it says it doesnt have a valid IP configuration frown

Funk

27,807 posts

240 months

Tuesday 8th January 2019
quotequote all
kowalski655 said:
As to the LAN settings,from Control Panel I can only find "Proxy" that offers the option to turn off-it is turned off.
It's this you need to check:



Have you got 'Automatically Detect' unchecked? You want to have nothing ticked at all on that Settings option. Sorry for labouring the point.

deckster

9,631 posts

286 months

Tuesday 8th January 2019
quotequote all
Funk said:
OP: on the PC that won't connect - check Control Panel > Internet Options > Connections Tab > LAN settings > ensure 'Automatically Detect Settings' is unchecked.

This setting being ticked has, in the past, caused the same issues for me as you've mentioned in your post.
Disagree strongly. For a home network like this, you want the PC to auto-discover its IP settings. Setting values manually is almost never needed for a domestic network. Edited to add: and randomly putting in settings from somebody else's configuration is practically guaranteed to fail. If you don't know specifically which addresses to put here for your router and network, then you definitely don't want to even try.

If it's not automatically getting the IP settings from the router then there is something more fundamentally wrong. What happens if you plug the non-working PC, with automatic settings enabled, into one of the sockets that the working PCs use?


Edited by deckster on Tuesday 8th January 16:33

a7x88

795 posts

179 months

Tuesday 8th January 2019
quotequote all
You've set them from the Plusnet forum but we don't know for certain that your Plusnet router is using the same address range.

To rule the most obvious out - can you give us the IP address of one other device connected to the internet (and working)?

kowalski655

Original Poster:

15,237 posts

174 months

Tuesday 8th January 2019
quotequote all
Funk said:
...... Sorry for labouring the point.
No need to worry, im useless at more than basic PC stuff
Found that tab (finally smile) and it IS unchecked

Deckster, I have swapped the cables at the router end of the ethermnet, so was using a router port that worked, but that didnt help

Funk

27,807 posts

240 months

Tuesday 8th January 2019
quotequote all
kowalski655 said:
Funk said:
...... Sorry for labouring the point.
No need to worry, im useless at more than basic PC stuff
Found that tab (finally smile) and it IS unchecked

Deckster, I have swapped the cables at the router end of the ethermnet, so was using a router port that worked, but that didnt help
OK, cool. Try enabling the Auto detection in that case and see what it does...