I'm running into an unusual issue where at seemingly random times, my Windows 11 Pro machine will disconnect from the Ethernet connection. When I look under Network & internet > Ethernet, it shows my Ethernet connection requiring action. To the right of the connection name, there is a 'Sign in' box near the expand category arrow.
I understand this type of Ethernet sign in is common for a Windows 11 Enterprise OS, but not for a Windows 11 Pro OS. Why am I getting this odd issue on my machine Windows 11 Pro machine? I don't even have sign in credentials setup for an Ethernet/Domain sign in outside of the Windows login.
Specs
Edition: Windows 11 Pro
Version: 23H2
OS build: 22631.3447
Experience: Windows Feature Experience Pack: 1000.22688.1000.0
Device: Dell Precision 5470
Dell Puck Adapters for ethernet connection for some devices on the switch.
Additional Information:
This is an physical Ethernet wired connection. If I click the sign in button, it says it's doing some type of authentication but just hangs. It never resolves the issue from the sign in option. After I click cancel, the issue will eventually resolve on its own at some point, usually within 10 minutes. This happens regardless of clicking the sign in option or not. However, some days it wont happen at all. Some days it will happen 4 or 5 times at seemingly random intervals.
This is on an organizational domain network and my computer is the only one I am aware of experiencing this issue. I work in the IT department here an haven't come up with any answers from the more senior IT staff or from online research.
Screen shot of Ethernet sign-in
RESOLUTION:
So interestingly, I discovered the issue and it wasn't what I expected. We make use of Dell Puck Adapters for connecting some of our devices to ethernet via USB-C thunderbolt. In this odd case, some of the Pucks were actually DOSing the Ethernet connection at the dumb switch. I don't know the exact reason yet, but in this case at least two of these Pucks were actually blocking the throughput to the other switch ports. My guess is that is that they were some how poisoning the ARP table of the dumb switch.
The reason I suspect this to be the cause is due to troubleshooting each Puck connected to the switch, one at a time. By removing the Pucks one at a time until the network returned to a working state, I then re-applied the Pucks until the network stopped working again. Not all the Pucks were causing this issue. Actually, of about 20, only 2 were causing this issue.
I think this might have something to do with the MAC passthrough being activated on the devices using the Pucks for Ethernet connections. Though, these same Pucks still caused the issue once they were reconnected to the network, even when no device was connected to them.
In either case, it has been a week now and the issue has not returned.