Windows 10: Problem with Network Connectivity

Hi all,

I have recently set up a new PC. My problem is it randomly loses network connectivity and shows the yellow triangle next to the ethernet connection down in the system tray.

I have tested the network with a laptop connecting via the same cable and no problems.

The way I temporarily fix the problem is by disconnecting the cable and reconnecting it like in this video:

[youtube]kaE1FMHfTyE[/youtube]

The little yellow triangle will then reappear randomly between 10 minutes to 2 hours later.

I have tried removing the device from device manager and reinstalling and the same with the driver but that didn't help.

Does anyone have any advice or know of a solution?

Thanks

Mark

:)

 

Problem with Network Connectivity

Sometimes I will lose my internet connection. I noticed that my current network says "connected, no internet" When I hover my mouse pointer over the network icon on the taskbar it shows a network from a router that I don't use anymore. Rebooting system
seems to correct it for a while.

 

Problem with Network Connectivity

There was error with network connectivity in Windows 10, which you may fix through Windows Update.

Try run Windows Update and install all updates and then restart your PC.

 

The Triangle usually means limited connection, which is caused by the Gateway or Access Point. What does Ipconfig /all show when you put it into a Command Window.

 

Hey @bro67, sorry for the late reply!

I ran the ipconfig /all twice, once when the yellow triangle was showing and once when I removed and replaced the ethernet cable in the port. I'll paste them below:

ipconfig /all with triangle

Microsoft Windows [Version 10.0.14393](c) 2016 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>ipconfig /all[0x7FFB673E70E3] ANOMALY: use of REX.w is meaningless (default operand size is 64)Windows IP Configuration Host Name . . . . . . . . . . . . : SHOPFLOOR-HP Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter Ethernet: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connection Physical Address. . . . . . . . . : 00-0F-FE-D0-64-65 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::99:cbcc:1d74:bd92%3(Preferred) Autoconfiguration IPv4 Address. . : 169.254.189.146(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 67112958 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-60-FC-A2-00-0F-FE-D0-64-65 DNS Servers . . . . . . . . . . . : 192.168.0.1 0.0.0.0 NetBIOS over Tcpip. . . . . . . . : EnabledTunnel adapter isatap.{2946C95F-6C51-49EB-8344-9AC00C6D51E1}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel adapter Teredo Tunneling Pseudo-Interface: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesC:\WINDOWS\system32>



ipconfig /all without triangle

Microsoft Windows [Version 10.0.14393](c) 2016 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>ipconfig /all[0x7FFB673E70E3] ANOMALY: use of REX.w is meaningless (default operand size is 64)Windows IP Configuration Host Name . . . . . . . . . . . . : SHOPFLOOR-HP Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter Ethernet: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connection Physical Address. . . . . . . . . : 00-0F-FE-D0-64-65 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::99:cbcc:1d74:bd92%3(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : 07 November 2016 12:05:48 Lease Expires . . . . . . . . . . : 07 November 2016 14:05:48 Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 67112958 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-60-FC-A2-00-0F-FE-D0-64-65 DNS Servers . . . . . . . . . . . : 192.168.0.1 0.0.0.0 NetBIOS over Tcpip. . . . . . . . : EnabledTunnel adapter isatap.{2946C95F-6C51-49EB-8344-9AC00C6D51E1}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel 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:382c:3f5e:adb9:4e69(Preferred) Link-local IPv6 Address . . . . . : fe80::382c:3f5e:adb9:4e69%4(Preferred) Default Gateway . . . . . . . . . : :: DHCPv6 IAID . . . . . . . . . . . : 134217728 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-60-FC-A2-00-0F-FE-D0-64-65 NetBIOS over Tcpip. . . . . . . . : DisabledC:\WINDOWS\system32>


I on't know if there is a difference between the 2 but I thought I'd post just in case!

Thanks in advance.

M

 

One thing is when disconnected you loose your IP and get the192 default one which wont work. The IP lease is very short go onto the router and increase the dhcp lease to 5 days when your lease runs out thats why it drops it can't renew or you could set a static ip

 

One thing is when disconnected you loose your IP and get the192 default one which wont work. The IP lease is very short go onto the router and increase the dhcp lease to 5 days when your lease runs out thats why it drops it can't renew or you could set a static ip
You have NetBIOS disabled enable that and disable ipv6 it's not used and increase traffic

 

I beg to differ Samuria: on a LAN with DHCP available, and NAT between that LAN and the Internet, the 192.168.x.x addresses are well known as "private IP addresses," perfectly valid for LAN use. They don't work on the Internet, to be sure, but they do work fine for accessing the Internet as long as Network Address Translation (NAT) service is available and active on the boundary device between the LAN and the Internet. Here, for example, is my own basic ipconfig info:



The upper red arrow points to my current local IP address for the PC I'm working on at the moment, while the lower address is for the Internet Gateway that connects my LANs to my ISP's CATV local loop. Note that both addresses begin with 192.168, which indicates they belong to the Class C Private Address range defined in RFC 1918.
The problem is something else. I don't even think the short lease period for DHCP is responsible. We don't know enough from the OP yet to diagnose his problems.
Let me recommend this to the OP: the next time you see the yellow triangle, run the network troubleshooter and report back what it tells you. If you type "troubleshoot network" into the Cortana/Search box, it will come right up, and you can click it to run it. Try it, please, and let us know what you find out.
Sorry for your trouble & HTH,
--Ed--

 

Download my script here. When you have the issue again, run the script and get the log file created on your desktop uploaded and we should be able to determine the issue. https://windowsforum.com/threads/net...mation.223812/

 

Thank you to everyone who posted, especially @Samuria, I assigned a permanent IP to the PC through the router which solved the problem.

Apologies for taking a while to come back to you all.

Thanks again!

Mark

 

MAC to IP on the router/gateway side is always the best. That way you do not end up with an IP conflict. The changes made in all OS's are not really in line with what the firmware that is somewhat dated for Gateways, especially IPTables.

 

I should really remember to go to the router first in future!

 

It is a lot easier to do it that way. Especially with devices like the Raspberry Pi, which for some reason the Pi Foundation has messed up assigning a Static IP from the OS side.

Set a unique name for the device when you do it. I try to stay close to the Netbios name that I use.

 

Will do, thank for your advice!