Windows 10 fails to recognize Ethernet cables.

F5F Stay Refreshed Power Users Networks Windows 10 fails to recognize Ethernet cables.

InoueAlice
Senior Member

677

09-29-2016, 07:40 PM

I possess an Ethernet wire extending from your router to your laptop, yet the internet remains unavailable. On Ubuntu it works smoothly, but the Windows 10 troubleshooter prompts for a connection.

InoueAlice

09-29-2016, 07:40 PM #1

I possess an Ethernet wire extending from your router to your laptop, yet the internet remains unavailable. On Ubuntu it works smoothly, but the Windows 10 troubleshooter prompts for a connection.

Benwade3
Junior Member

09-30-2016, 01:06 AM

No, you haven't installed the driver for your Ethernet card yet.

Benwade3

09-30-2016, 01:06 AM #2

No, you haven't installed the driver for your Ethernet card yet.

Tykos
Junior Member

10-05-2016, 02:02 AM

I didn’t alter anything; it functioned properly the previous night and when I powered it up this morning, it didn’t work at all.

Tykos

10-05-2016, 02:02 AM #3

I didn’t alter anything; it functioned properly the previous night and when I powered it up this morning, it didn’t work at all.

Fluffycakes123
Senior Member

696

10-05-2016, 04:26 AM

It provides network configuration details such as IP addresses, subnet masks, gateway, and DNS settings.

Fluffycakes123

10-05-2016, 04:26 AM #4

It provides network configuration details such as IP addresses, subnet masks, gateway, and DNS settings.

Sjittham
Member

10-05-2016, 06:36 PM

It might be a negotiation point. Open Device Manager, right-click the network card, select Properties > Advanced. Look for the Speed & Duplex setting and attempt to adjust the speeds. If it functions at 100Mbps duplex but not at gigabit, the problem lies there.

Sjittham

10-05-2016, 06:36 PM #5

tsnyder01
Member

171

10-06-2016, 12:00 AM

Uncertain about why most reboots failed, but once you switched to Ubuntu and then back to Windows 10 it resolved the issue.

tsnyder01

10-06-2016, 12:00 AM #6

Uncertain about why most reboots failed, but once you switched to Ubuntu and then back to Windows 10 it resolved the issue.