Ok, unfortunately I've been forced into making this account in the hopes that someone can help me solve an issue I've seen all over TH threads and various other tech help sites, but I've reached a point where I have no clue how to proceed. As the thread title states, my ethernet connection either gets terrible latency (5000-10000ms) or just cuts out completely. However, on wireless, the connection is fine. I'll try to be as transparent as possible in this initial post so as to make it clear where I stand at this moment. Now I wouldn't say I'm incredibly knowledgeable when it comes to networking, so any help would be appreciated.
(No overclocking or anything like that)
CPU: AMD FX(tm)-6300 Six-Core Processor, 3500 Mhz, 3 Core(s)
Motherboard: M5A78L-m/usb3
GPU: AMD Radeon R9 200
12GB Ram
725W PSU
OS: Windows 10 Home(64bit)
So I'll start by explaining the problem and all solutions I've attempted so far. I recently started using a Netgear Powerline 1000 adapter to utilize a wired connection to my desktop, which is far away from the router upstairs. For about a week, it worked perfectly, until I noticed the connection start cutting in and out a lot. However, the wireless worked fine. After a bunch of scouring forums for solutions, I discovered how to ping my loopback (127.0.0.1) essentially, to test my NIC. At this point I was using the onboard adapter, so I bought a new Gigabit Ethernet PCI Adapter and installed it. Now, my ethernet connection will either cut out completely, or I'll get terrible latency. After installing this new ethernet adapter, pinging my loopback came back with no packet loss, and less than 1ms response time for each packet sent. However, when I ping my router's IP, it'll either get terrible latency(4000+) or simply "request timed out". When this happens, windows troubleshooter most often delivers "DNS server not responding", but it also occasionally would say "Invalid IP Configuration" or "Your computer appears to be correctly configured, but the device or resource (DNS server) is not responding". I have all my adapter settings set to automatically retrieve IP and DNS addresses, and there's no issue with wireless. I've narrowed down the issue to my desktop, as all other devices in the house have no issues, and I know it's not the ethernet cable as I've tested multiple on several devices, they work fine. I'm almost positive it's not the powerline adapter, as I've tested the exact outlet and cable by plugging into my laptop, which receives perfect connection, yet as soon as I switch it to my desktop, it starts to fail. One last interesting detail, I've noticed that when I boot my computer, in the first few minutes before it's had ample time to boot, I've run ping tests to my router, and even forced a trial of 100 pings, and I got 0% packet loss, 15ms average response time. Obviously, this is exactly how the connection should be, but five minutes later, I'll run the same test and get either insane latency or request timed out. This led me think more along the lines of software/firewall issue, but any input will be appreciated. I'll list all the solutions I've already tried, none of which have seemed to fix it.
Power cycle (powered off and unplugged router and computer for extended period)
Reinstalled adapter drivers
Updated BIOS
Altered duplex and speed settings on adapter
ipconfig release renew
flushdns registerdns
netsh winsock reset
Enabled and disabled adapter(s) (wireless adapter is disabled, only functioning ethernet adapter enabled)
Temporarily disabled firewall
Uninstalled common problem software (like Bonjour)
Virus and malware scanned
Tried a separate adapter
Disabled IPv6
As far as I can remember at this moment these are all of the potential solutions I've already tried, and none have solved this issue, any suggestions would be appreciated, or even help as to how to better diagnose and pinpoint the issue. I've tried tracert but almost every response has timed out when attempting that as well.
Edit: I'm not sure how important this is, but I've also come to realize that if I set my speed and duplex on my adapter to anything but auto-negotiate, I get "Unidentified Network" and even if it IS set to auto negotiate, the pc will boot up with the right network, however if the adapter is reset, even with the auto-negotiate setting it will revert to "Identifying network..." until it eventually settles onto unidentified network. Should any screenshots of my pc's services or adapter settings or command center logs be required I would be happy to do so if it helps at all.
Cheers
Cameron
(No overclocking or anything like that)
CPU: AMD FX(tm)-6300 Six-Core Processor, 3500 Mhz, 3 Core(s)
Motherboard: M5A78L-m/usb3
GPU: AMD Radeon R9 200
12GB Ram
725W PSU
OS: Windows 10 Home(64bit)
So I'll start by explaining the problem and all solutions I've attempted so far. I recently started using a Netgear Powerline 1000 adapter to utilize a wired connection to my desktop, which is far away from the router upstairs. For about a week, it worked perfectly, until I noticed the connection start cutting in and out a lot. However, the wireless worked fine. After a bunch of scouring forums for solutions, I discovered how to ping my loopback (127.0.0.1) essentially, to test my NIC. At this point I was using the onboard adapter, so I bought a new Gigabit Ethernet PCI Adapter and installed it. Now, my ethernet connection will either cut out completely, or I'll get terrible latency. After installing this new ethernet adapter, pinging my loopback came back with no packet loss, and less than 1ms response time for each packet sent. However, when I ping my router's IP, it'll either get terrible latency(4000+) or simply "request timed out". When this happens, windows troubleshooter most often delivers "DNS server not responding", but it also occasionally would say "Invalid IP Configuration" or "Your computer appears to be correctly configured, but the device or resource (DNS server) is not responding". I have all my adapter settings set to automatically retrieve IP and DNS addresses, and there's no issue with wireless. I've narrowed down the issue to my desktop, as all other devices in the house have no issues, and I know it's not the ethernet cable as I've tested multiple on several devices, they work fine. I'm almost positive it's not the powerline adapter, as I've tested the exact outlet and cable by plugging into my laptop, which receives perfect connection, yet as soon as I switch it to my desktop, it starts to fail. One last interesting detail, I've noticed that when I boot my computer, in the first few minutes before it's had ample time to boot, I've run ping tests to my router, and even forced a trial of 100 pings, and I got 0% packet loss, 15ms average response time. Obviously, this is exactly how the connection should be, but five minutes later, I'll run the same test and get either insane latency or request timed out. This led me think more along the lines of software/firewall issue, but any input will be appreciated. I'll list all the solutions I've already tried, none of which have seemed to fix it.
Power cycle (powered off and unplugged router and computer for extended period)
Reinstalled adapter drivers
Updated BIOS
Altered duplex and speed settings on adapter
ipconfig release renew
flushdns registerdns
netsh winsock reset
Enabled and disabled adapter(s) (wireless adapter is disabled, only functioning ethernet adapter enabled)
Temporarily disabled firewall
Uninstalled common problem software (like Bonjour)
Virus and malware scanned
Tried a separate adapter
Disabled IPv6
As far as I can remember at this moment these are all of the potential solutions I've already tried, and none have solved this issue, any suggestions would be appreciated, or even help as to how to better diagnose and pinpoint the issue. I've tried tracert but almost every response has timed out when attempting that as well.
Edit: I'm not sure how important this is, but I've also come to realize that if I set my speed and duplex on my adapter to anything but auto-negotiate, I get "Unidentified Network" and even if it IS set to auto negotiate, the pc will boot up with the right network, however if the adapter is reset, even with the auto-negotiate setting it will revert to "Identifying network..." until it eventually settles onto unidentified network. Should any screenshots of my pc's services or adapter settings or command center logs be required I would be happy to do so if it helps at all.
Cheers
Cameron
Facebook
Twitter
Instagram