W
webb4789
I have an Intel NUC i5-4250U with integrated Intel Ethernet 1218-V.
I use Windows 10 Pro 64-bit.
Windows updated to Version 1909 recently. This update disabled the ethernet connection somehow. I rolled back to the previous windows version, but it made no difference.
I used a USB-to-ethernet adapter and for a while this worked (until windows retried the update to 1909).
While the the USB-ethernet connection was working, I was able to download the Intel Driver & Support assistant and have updated all the indicated drivers etc. to the latest.
Windows reinstalled Version 1909 and now the USB-ethernet connection is also disabled.
The symptoms are weird. The ethernet works enough to get an IP V4 address (using DHCP), but then says the default gateway (which supplied the IP address) cannot be contacted and I cannot ping it.
I CAN ping another PC connected to the same switch, so the ethernet hardware & cable seems to be working up to a point. The other PC is also working normally using the same switch and the same router/path to the internet. I did reboot the router (just in case), but no change. Trying to use a fixed IP address instead of DHCP makes no difference.
This seems like a clash between the ethernet drivers and the windows update, but none of the troubleshooters have helped. A windows network reset also makes no difference.
Following some suggestions I found on the microsoft pages, I removed the latest Intel drivers for the ethernet adapter and re-booted, so now it is using a Microsoft driver, but with the same problem.
I have turned off the firewall and uninstalled MacAfee altogether (following some google suggestions), but still no success.
Does anyone else have this issue. Has anyone found anything which works. I'm now on day 3 of trying to get internet access back to the NUC without any luck.
As I type, I have 2 pings going, one to the router (alternates between "Request timed out" and "Destination host unreachable".). The other ping is to a local PC which shares the same switch and path to the internet, the ping to this machine is fine.
Continue reading...
I use Windows 10 Pro 64-bit.
Windows updated to Version 1909 recently. This update disabled the ethernet connection somehow. I rolled back to the previous windows version, but it made no difference.
I used a USB-to-ethernet adapter and for a while this worked (until windows retried the update to 1909).
While the the USB-ethernet connection was working, I was able to download the Intel Driver & Support assistant and have updated all the indicated drivers etc. to the latest.
Windows reinstalled Version 1909 and now the USB-ethernet connection is also disabled.
The symptoms are weird. The ethernet works enough to get an IP V4 address (using DHCP), but then says the default gateway (which supplied the IP address) cannot be contacted and I cannot ping it.
I CAN ping another PC connected to the same switch, so the ethernet hardware & cable seems to be working up to a point. The other PC is also working normally using the same switch and the same router/path to the internet. I did reboot the router (just in case), but no change. Trying to use a fixed IP address instead of DHCP makes no difference.
This seems like a clash between the ethernet drivers and the windows update, but none of the troubleshooters have helped. A windows network reset also makes no difference.
Following some suggestions I found on the microsoft pages, I removed the latest Intel drivers for the ethernet adapter and re-booted, so now it is using a Microsoft driver, but with the same problem.
I have turned off the firewall and uninstalled MacAfee altogether (following some google suggestions), but still no success.
Does anyone else have this issue. Has anyone found anything which works. I'm now on day 3 of trying to get internet access back to the NUC without any luck.
As I type, I have 2 pings going, one to the router (alternates between "Request timed out" and "Destination host unreachable".). The other ping is to a local PC which shares the same switch and path to the internet, the ping to this machine is fine.
Continue reading...