Ethernet not working, Wifi works perfectly!

[TairyHesticles]

Hi everyone,

On Friday night my Ethernet started lagging a little (dropping from 60Mbps to 5Mbps) and then after an hour of restarting the router/unplugging everything and back again it dropped completely! At first I thought it was our internet dropping out but out of the 6 computers in the house mine was the only to stop working .... apart from on WIFI! 🙁

I've uninstalled the drivers/reinstalled them and updated the whole of networking settings to no avail.

It seems that it does not recognize the cable or the server!

Any help would be much appreciated - I have looked at the other forums with similar issues and no results yet! :/

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Caeron Roberts>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Computer
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 08-60-6E-88-44-31
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::40f4:f5d1:3aae:5ddb%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.13(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 22 February 2015 16:54:08
Lease Expires . . . . . . . . . . : 23 February 2015 19:07:28
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 168321134
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F0-36-37-08-60-6E-88-44-31

DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 44-94-FC-F8-17-F9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter WiFi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR WNA3100M N300 Wireless Mini USB A
dapter
Physical Address. . . . . . . . . : 44-94-FC-F8-17-F9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c5b1:459b:2b9f:a9be%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.14(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 22 February 2015 19:06:10
Lease Expires . . . . . . . . . . : 23 February 2015 19:06:14
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 222598396
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F0-36-37-08-60-6E-88-44-31

DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:c2f:3161:a9ed:a858(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::c2f:3161:a9ed:a858%4(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 318767104
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-F0-36-37-08-60-6E-88-44-31

NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Caeron Roberts>

 

[Solandri]

Shut off, disable, or remove your wireless adapter so we know we're only dealing with your wired network.

1) Start up Windows in safe mode with networking, and see if you can access website with the wired network. This should narrow down if you're dealing with a software problem or a hardware problem. Based on your ipconfig it's probably not a hardware problem, but just to be sure... Boot back into regular Windows when you're done.

2) From the command prompt, try to ping 192.168.0.1. If that works, try to ping 8.8.8.8. If you notice some dropped packets, try ping -n 999 192.168.0.1 so you get a better idea what percentage of packets are being dropped.

3) Is the Teredo tunneling interface something you installed? It's used for certain VPNs and anonymizing services so it's necessarily a red flag. But if you don't use such services, it could be an indication that a virus or malware installed it, and it has been redirecting all your network traffic through someone else's computer, where they could pick out your passwords and bank account info. Your connection may not be working because your computer is trying to forward your traffic to that other person's computer, but that computer is offline.

4) I've seen similar symptoms due to the IPv6 address is interfering with IPv4. The ping test should tell you if that's the case - you'll get the ping reply in IPv6 addresses instead of IPv4.

 

[reedo_43]

I agree with Solandri. If you are dropping any packets, you could just have a bad cable. Also if you ping 127.0.0.1 and you get dropped packets, your ethernet adapter is bad or failing.

 

[Tairyhesticles2]

Hi both,

apologies for the late reply.
@Solandri, didnt boot into Windows Safemode, tried pinging 192.168.0.1 no dropped packets and same story with 8.8.8.8 and -n 999 192.168.0.1 , I have no idea what Teredo tunnelling interface is - I've uninstalled it regardless. Finally how can I tell the difference between a reply in IPv6 instead of IPv4? I'm currently running the -n 999 192.168.0.1 with replies from 192.168.0.1: bytes=32 time<1ms TTL = 64

@reedo_43 pinged 127.0.0.1 with no dropped packets

It would be worth mentioning that for a brief period (2 days) the ethernet was back up and running again perfectly fine, but it has since reverted to this again!