Jump to content

Ethernet connection randomly stopped working

Go to solution Solved by Nergale,

Do you know your gateway routers IP? (The IP Address of the router that should connect you to the internet - something like 192.168.1.1)

If so, try to ping it. To do so open your command line (windows + x, press "run" and type cmd. Then in the black window type "ping *yourroutersip*"

  • If that fails, your layer 2 connection to your router is not working correctly. You might want to check your IP first:
    • 1. Are you in the same subnet as your router?
    • 2. Can you ping any other client within your own subnet?
  • If you succeed, and you get a response, then you should check your routing table. If your client doesnt know where to send your packets to, it will simply drop them.
    • Open the command line again, type "route print".
    • Look for your default route, it will look something like this:
0.0.0.0		0.0.0.0		*yourroutersip*	*yourip*

If you happen to have 2 of those routes or none, then you need to fix that, but we'll cross that bridge only if we need to.

So I was in the middle of a game and my ethernet connection cut out. Wifi still works but whenever I try to reconnect to the ethenet it says there's no internet. My Ethernet is hooked up to a powerline adapter but they are still paired and say they are connected to internet I tried swapping cables, reinstalling drivers, and rebooting my router. The only thing I can think of is the motherboard port somehow died randomly. But when I plug the Ethernet cable in it lights up like it always does. Is there anything else I could try?

Link to comment
https://linustechtips.com/topic/879673-ethernet-connection-randomly-stopped-working/
Share on other sites

Link to post
Share on other sites

Seems like you've covered a lot of your bases. Maybe see if connecting to a different device? Like try connecting a different device to the Ethernet port on the powerline or try connecting something other then the powerline to the port on your computer? That might decipher which device the port went bad on if a port did indeed fail.

Link to post
Share on other sites

Do you know your gateway routers IP? (The IP Address of the router that should connect you to the internet - something like 192.168.1.1)

If so, try to ping it. To do so open your command line (windows + x, press "run" and type cmd. Then in the black window type "ping *yourroutersip*"

  • If that fails, your layer 2 connection to your router is not working correctly. You might want to check your IP first:
    • 1. Are you in the same subnet as your router?
    • 2. Can you ping any other client within your own subnet?
  • If you succeed, and you get a response, then you should check your routing table. If your client doesnt know where to send your packets to, it will simply drop them.
    • Open the command line again, type "route print".
    • Look for your default route, it will look something like this:
0.0.0.0		0.0.0.0		*yourroutersip*	*yourip*

If you happen to have 2 of those routes or none, then you need to fix that, but we'll cross that bridge only if we need to.

Link to post
Share on other sites

12 minutes ago, Nergale said:

Do you know your gateway routers IP? (The IP Address of the router that should connect you to the internet - something like 192.168.1.1)

If so, try to ping it. To do so open your command line (windows + x, press "run" and type cmd. Then in the black window type "ping *yourroutersip*"

  • If that fails, your layer 2 connection to your router is not working correctly. You might want to check your IP first:
    • 1. Are you in the same subnet as your router?
    • 2. Can you ping any other client within your own subnet?
  • If you succeed, and you get a response, then you should check your routing table. If your client doesnt know where to send your packets to, it will simply drop them.
    • Open the command line again, type "route print".
    • Look for your default route, it will look something like this:

0.0.0.0		0.0.0.0		*yourroutersip*	*yourip*

If you happen to have 2 of those routes or none, then you need to fix that, but we'll cross that bridge only if we need to.

I decided to try and download the drivers directly from Realtek's website and now it's working. Thanks though

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×