Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
In some cases it can be damaged wires inside or outside your property. If the disconnections are intermitted it can be hard to find the exact problematic wire.
1. You tried different ports means you tried two different physical NIC ports on your PC? This means either your motherboard has two NICs (possible, but less common these days). Definitely clarify this one.
2. You tried two different ethernet cables.
3. You tried different ports on the router.
In my mind, if this is all correct, this rules out a bad cable (you tried two), it rules out a bad ethernet port (you tried two on both ends), and it may or may not rule out a "bad" NIC (unless both ports on your PC use a different NIC, then this doesn't rule out a particular NIC/driver issue under certain use cases). Again, clarity on that one would help. Is this onboard NIC and an add in card? Two onboard NICs? What exact NICs?
And if you're losing network connection, as opposed to retaining network connection but losing internet access (there's a difference), then this should also rule out an issue beyond your residence, as an issue beyond your residence would bring the internet down but not the network connection (you'll get the "no internet access" status instead of the "no network connection").
Assuming what I asked for clarity on is correct, I think this basically leaves a bad router or modem? Or one of the things you tried two of was bad luck and both were bad. Do you have a second PC you can test with to verify things?
get the correct ones from the mobo mfg or oem site
i have two on my mobo one is an intel i211 gig one and the other is a marvell aqc11c 5g i have tried both the marvell one always says not connected and i have tried 2 different cables one came with the router and the other was one i had brought i have tried 2 normal ports on the router and the 2.5gb port and all seem have no luck
i have also tried to update drivers but all are up to date apprently downloaded the intel driver and support app and says its up to date and the marvell one i havent been able to find an update for the driver
check the adapter properties, and see how long its been connected for
if that keeps resetting, then its the cable, or driver or maybe network switch or router
That is, since the Marvell NIC isn't connecting at all, it probably has one issue, and maybe the Intel NIC is working to begin with, but dropping the connection on occasion. I don't know about the i-221 but both the i-225V and i-226V were pretty bad NICs and had just that problem.
Since the one connecting is 1G and the one not connecting is 5G, I would have considered that maybe it's an issue with the cable, like maybe the cable that is too long/picking up interference/whatever, but... you said you tried two different cables. Are they both maybe too old/not the right type though?
It would help if you were able to get the Marvel NIC working to begin with because otherwise, you can't rule the Intel NIC out as the possible cause here.
So at this point, it could be the Router/Modem, or it could be the Intel NIC.
Power cycle the Gateway and Router approx once per week or month
EDIT:
Open Device Manager > Network Adapters > Select your NIC > Properties
Then go to Power Management tab and uncheck "Allow the computer to turn off this device to save power"
and will see how that goes
Now that you have the second one working, give it time to see if the issue continues.
If the issue does not continue, then there was likely something to the Intel NIC or its drivers that were causing it.
If the issue does continue, the issue isn't with either NIC (or both individually have it, haha) and that would suggest it's down to the router or modem I would think.