NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PC Looses Network Connection
I have a Dell Precision 3460 PC (Intel 1219-LM, WIN 11Pro) which for about 10 days now seems to loose it LAN connection after 15-30 minutes. I stuck in an ASUS Wireless adapter, which works better, but will fail in about a day. When they fail, the PCs network functions seem to get corrupt (ie Network Connections => Enable\Disable and others changes hang and need to be shut down with Task Manager).
It's a new PC and Dell was unable to diagnose it and replaced the motherboard, so it's not hardware, and I have assumed it to be the PCs network config. Yesterday I took it from the clients location to my shop, and now it seems to work with no issues.
On site it's connected to a Netgear R7800 on FW V1.0.2.90. It has a static IP set as 10.1.10.100, subnet mask of 255.255.255.0 and gateway of 10.1.10.1. The sole DNS is set at 10.1.10.1. I also have the devices IP set as Reserved in the LAN Setup. The only router testing I did was to change ports, and the fault followed the device. I DNR if we tried just the reservations with no static IPs.
In my shop, I have "another" brand of router and ran it overnight on DHCP, then assigned it a static IP in my routers range (192.168.50.211) and can not get the PC to crash.
All other PCs seem to work fine, including the old Precision this replaced with nearly identical network config
Until now I have pretty much been convinced this is the PC, but now thinking that for some reason these 2 just do not like each other. Any thoughts?
9 Replies
Something you might check with ASUS about if this is something new and seems to cause problems.
The failure of the LAN adapter occurred prior to connecting the ASUS wireless.
The ASUS was added only to test if the issue was the LAN Hardware, expecting that if it did not fail it was the Intel 1219-LM hardware.
As both adapters fail with similar results, though different time frames, I expect it's software. As the computer does not fail on a different network, I expect it's some type of communication issue with the router, but in my decades of doing this, not seen anything like it.
Is this the only PC that does this?
Might try a factory reset on the router and setup from scratch with a wired PC:
https://kb.netgear.com/24233/How-do-I-erase-the-configuration-settings-on-my-Nighthawk-router
https://kb.netgear.com/22697/How-do-I-install-my-NETGEAR-router-using-the-router-web-interface
RangerZ wrote:I have a Dell Precision 3460 PC (Intel 1219-LM, WIN 11Pro) which for about 10 days now seems to loose it LAN connection after 15-30 minutes. I stuck in an ASUS Wireless adapter, which works better, but will fail in about a day. When they fail, the PCs network functions seem to get corrupt (ie Network Connections => Enable\Disable and others changes hang and need to be shut down with Task Manager).
It's a new PC and Dell was unable to diagnose it and replaced the motherboard, so it's not hardware, and I have assumed it to be the PCs network config. Yesterday I took it from the clients location to my shop, and now it seems to work with no issues.
On site it's connected to a Netgear R7800 on FW V1.0.2.90. It has a static IP set as 10.1.10.100, subnet mask of 255.255.255.0 and gateway of 10.1.10.1. The sole DNS is set at 10.1.10.1. I also have the devices IP set as Reserved in the LAN Setup. The only router testing I did was to change ports, and the fault followed the device. I DNR if we tried just the reservations with no static IPs.
In my shop, I have "another" brand of router and ran it overnight on DHCP, then assigned it a static IP in my routers range (192.168.50.211) and can not get the PC to crash.
All other PCs seem to work fine, including the old Precision this replaced with nearly identical network config
Until now I have pretty much been convinced this is the PC, but now thinking that for some reason these 2 just do not like each other. Any thoughts?
A couple of settings on this specific Windows PC you want to check.
Go in to the Network Status setting and confirm the network profile is set to private and not to public. Occasionally Windows updates will change this without any indication.
Go in to the Windows power save options on the control panel. When the machine is set to go to sleep to save power, there is usually an option to power down the network connection (saves additional power when using a laptop on battery). When it wakes back up, the machine has lost the connection while asleep. Make sure you set the network connection to not power down when the machine goes to sleep. This is a buried option in the network adapter settings.
Hi, thanks for sharing.
Yes, it's a private network.
As for the Power Plan, the machine is used as a "server" to host a database, which needs to be always available, so the power plan is set to Sleep: Never. That said, I did change the Link State Power Management from Max Power Savings to Off, though not sure it makes a difference if it never sleeps. Good thought.
I am thinking there may be something with the fixed IP and the DNS assignment. When we set the fixed ip on the PC, it defaults the DNS to the router, I notice a number of DNS warnings in the PCs logs, but have assumed this to be a result as opposed to a symptom (ie no network, DNS lookup fails)
So just read the manual, going to try a reserved IP, and drop the fixed IP on the PC. Manual (P61) does not state if the Reserved IP addresses should be inside or outside of the DHCP range. I generally think it should be outside, but have seen it both ways.
What is the DNS setting in the router configuration? The DNS supplied by your service provider or a public one like Cloudflare, Google, Next, or etc?
Do you have the router DNS configured for and enabled for both IPv4 and IPv6?
I also have seen the reserved IP address both inside and outside the DHCP range. Should be easy enough to test one way or the other to verify if one works and one doesn't. I have found you can reserve an IP address within the router configuration or set a fixed IP address on a device itself. Some people do both and I was never comfortable with that setup. Personal preference was to set a fixed IP address within the device itself. Such as IP cameras, NAS, or wired access points. That way I was certain of the path into the configuration panel of the device.
