Ethernet connection suddenly stopped working

I just encountered a problem with my ethernet connection that I cannot fix on my own. Around two hours ago, my ethernet connection suddenly stopped working. Neither internet, nor local network connection works anymore. If I replug the cable or deactivate and reactivate the adapter through device manager, it actually works for around 15 seconds and then stops working again. The blinking ethernet light however will always stay on, indicating a physical connection. Windows will also still say it's connected through the ethernet cable, but any connection will fail. It is not a problem with the cable, I tried a different one and have the same problem. It's not the network switch, using a different port didn't fix it and other systems using the switch have no problem. Any other internet connection is fine, other systems work through Ethernet and Wifi works on the system, too. I can't find any interesting errors or messages in the Event Viewer either.

I use windows 10 22H2, all updates installed. It is a "Intel Ethernet Connection i219-V" Ethernet Adapter on a "MSi MPG Z390 Gaming Edge AC" mainboard. Windows device manager says the network adapter works fine. I also installed the newest driver from my Mainboards support website, which didn't fix the issue. Restarting Windows didn't change it either. If anyone has any idea what the issue could be, your help would be appreciated!

Edit for the **Solution**: Thanks to AussieJeffProbst I found out that my connection should work, because ping was always successful. After a 3 hour hunt, trying everything (e.g. ipconfig /flushdns, ipconfig /registerdns, netsh int ip reset reset.log) and multiple reboots, I ran out of tips from the internet. So I started checking my Ethernet Adapter settings in Windows. The only items in the list that looked like they could cause my problems where the "QoS Paket Sheduler" and "cFos Speed for faster Internet connections (NDIS 6)". I unchecked both, pressed OK and my connection immediately worked again! I re-enabled both again and it still works. I don't know why either of these two malfunctioned through multiple reboots, but temporarily disabling fixed it.