It's working now and I can ping my pfSense box, I figured that would only make sense if it was down.That was a lot of words to not answer "Can you ping your router?"
Yes it seems to appear that way.
OK, so instead of disabling the adapter next time it happens, disconnect the VPN (I assume you don't have split tunnel enabled?) and see if you can still ping your firewall. If you can, it's not the NIC. If you can ping the router, then try pinging something outside your network like 208.67.222.222 (OpenDNS server). Let us know what you find.Yes it seems to appear that way.
Not using split tunneling. For some reason It typically loses connection overnight so go figure. I tried removing the driver but soon as I searched for hardware changes it just reloaded the same one it was using. I have 7 systems that run 24/7 and this is the only one having issues.OK, so instead of disabling the adapter next time it happens, disconnect the VPN (I assume you don't have split tunnel enabled?) and see if you can still ping your firewall. If you can, it's not the NIC. If you can ping the router, then try pinging something outside your network like 208.67.222.222 (OpenDNS server). Let us know what you find.
It went down again around 2:15 this morning. I tried pinging but it couldn't reach anything on the network or on the outside ie: router, printer, other PCs... the only thing I could ping was itself. In the event viewer I get a lot of codes for 27 & 57, basically it's disconnecting and then reconnecting over and over.OK, so instead of disabling the adapter next time it happens, disconnect the VPN (I assume you don't have split tunnel enabled?) and see if you can still ping your firewall. If you can, it's not the NIC. If you can ping the router, then try pinging something outside your network like 208.67.222.222 (OpenDNS server). Let us know what you find.
Have you reached out to MSI to see if there's a firmware update for the NIC?It went down again around 2:15 this morning. I tried pinging but it couldn't reach anything on the network or on the outside ie: router, printer, other PCs... the only thing I could ping was itself. In the event viewer I get a lot of codes for 27 & 57, basically it's disconnecting and then reconnecting over and over.
I think at this point I'll actually reach out to MSI support but I've read lots of threads where others have RMA'd their boards only to have the same problems, one person did it 4 times and it always came back.
Yes I just registered it and opened a new ticket. I honestly thought their forums would get me somewhere but others are having issues as well with the i226-v.Have you reached out to MSI to see if there's a firmware update for the NIC?
Yes I have tried using a different cable and another port on the switch. I didn't feel it was proper for me to say this on the MSI forums but there really needs to be a class action lawsuit against Intel and all the other manufacturers over these defective chips. I don't really know how old this motherboard is but did have a fairly recent bios which can be used as an indicator, it wasn't the latest but was enough to work with the 14th gen CPUs. The support person didn't answer my question about the possibility of receiving a good board. I have read on other forums that people have RMA'd theirs back to MSI multiple times but even someone did it 4 times all within in a year.I didn’t really read this thread too carefully but I have not any issues and I suspect most of the computers I’ve built the past year or two use that same Intel network chip.
Do the RMA and hopefully that will solve your problem.
I’m assuming you have tried different cables? I had a bad batch of brand new cat6 cables from monoprice once (usually a decent vendor, although I switched brands after that). Super frustrating - out of like 50 I ordered like 1/4 were duds or died within a few months. I didn’t think I had multiple bad cables so I chased my tail on that for a while before I got a cable tester and ripped open every baggy and tested them all and figured it out.
Funny you mention bad luck with ASUS, my experience has always been the opposite, have had great service from them.Yes I have tried using a different cable and another port on the switch. I didn't feel it was proper for me to say this on the MSI forums but there really needs to be a class action lawsuit against Intel and all the other manufacturers over these defective chips. I don't really know how old this motherboard is but did have a fairly recent bios which can be used as an indicator, it wasn't the latest but was enough to work with the 14th gen CPUs. The support person didn't answer my question about the possibility of receiving a good board. I have read on other forums that people have RMA'd theirs back to MSI multiple times but even someone did it 4 times all within in a year.
Basically you have few options, if under warranty you can RMA with MSI or return/exchange with the reseller. If not then you basically have a paperweight, either use another network adapter ie: PCIe, USB, etc... or replace the board itself. Newegg must've changed their return policy but honestly I've had very few returns, they even provided a UPS return label and gave me 14 days to get it entered into their system, the website showed I had 6 days left which was to start the return process. I would've had to pay the shipping to MSI but the return would've been free. Honestly I never really understood the whole 30 thing, soon as you purchase the item the clock starts ticking from that moment and you loose a week or so just for the shipping.
I think @OVERKILL is correct about MSI, honestly I've had very few problems with them over the years but after the way I was treated on the AIO cooler and now this board I am really going to have to start considering other options, I don't like Asus, they are overpriced and I always have the worst luck with them. I do have a 2060 where the fan failed and they replaced the whole card but it wasn't the same one I received back and ran way hotter than what I had. I think when they can MSI will stand behind their products but after warranty not so much but really that's most anyone.
And it's not just MSI but Gigabyte and other manufacturers use these chips from Intel. Realtek also has a 2.5gbe but even they have problems. I have 2x Gigabyte x570s boards with Intel i225-v and they've been rock solid.
MSI told me there was not a firmware update available, now with that said it's probably in-house so they are not providing them to the end users. I ended up purchasing the Gigabyte version which actually has 1 more USB port in the rear but also only 2 of the m.2 slots, MSI has 3... not that big of a deal just cleans up a few extra lanes but only if you were using all of them. I'm hoping the memory I have will work which is why I went with the MSI they actually listed it as compatible but Gigabyte just hadn't tested it.Funny you mention bad luck with ASUS, my experience has always been the opposite, have had great service from them.
So, is the chip itself defective, or is it just the firmware? If it's just the firmware and Intel has released an update and the motherboard providers aren't giving that to the end users experiencing the issue, then it isn't really an Intel problem. On the other hand, if it can't be resolved with a firmware update, then it is definitely Intel's issue.
I'm always amused by the laundry list of firmware updates for servers, including for NIC's, that we don't see for desktops because the margin just isn't there to provide the same level of support.
OK, and you tried another cable, right? I believe that was covered earlier in the thread?Something else is at hand here... I have been using the Trendnet adapter and yet it still disconnected. I have 2 cable testers so going to use both and also I have a Qnap switch that I had replaced with the Trendnet so I will swap it back in. It could just be an odd issue where for some reason they don't like each other... extremely odd but is totally possible.
With the Trendnet USB I made sure not to turn off the device to save power and energy efficient ethernet is disabled.
The other cable tester wouldn't even work with another set of batteries, however the cable tested good and for now I've moved the cable to the other Trendnet switch. I had it connected to the TEG-S750 which is a 5 port 10gb switch that supports 100/1000/2.5/5/10, the other switch is the TEG-S591 which has 8x 2.5gbe ports and 10gb uplink.
Yes I tried a CTG 25ft cat6 cable earlier but that was also from the S750 switch, I currently have it connected to the S591. From reading the Amazon reviews there are others with connectivity issues that seem to stem from ver. 1.0R. I think for now I've seen enough and need to swap that back out for the Qnap, I want to give this thing to a friend who works in IT to test it but he is more on the end of managing the servers but he also has a nice setup in his basement with a lot more extensive knowlege of the inner workings of a network than I do especially troubleshooting over the network. When I worked in IT it was mostly providing end user support, installing switches, APs, installing LCD projectors, network troubleshooting, mostly the physical layer, I've replaced tons of RJ45 keystones due to bent pins.OK, and you tried another cable, right? I believe that was covered earlier in the thread?
Could definitely be the switch.