Heya folks, Ned here again. A few customers have reported this known issue on Windows 11 machines & you may see this event at boot up and perhaps occasionally afterwards. In the Event Log, in the Sys...
Updated Nov 07, 2022
Version 4.0
Blog Post
I am taking a moment to post my experience with this error since I encountered it on my Windows 11 laptop and was trying to find a post that had a possible solution. Here are some insights that I gleaned around this topic:
1) I primarily noticed this error shortly after connecting to built-in L2TP RAS connections I use for VPN however it would occasionally appear in the form of Windows Explorer freezing up.
2) The VPN tends to work for somewhere between ten seconds and a couple minutes and once the error occurs, the fix to get any internet back required forcibly disconnecting from VPN followed by disconnecting and reconnecting WiFi adapter
3) I would receive a few messages leading up to the 2505 event in the Windows Event Viewer (system log):
* Event 172 Connectivity state in standby: Disconnected, Reason: NIC compliance
* 8000 - Miniport Halt flow (driver disable)
* Event 2505 The server could not bind to the transport \Device\NetBT_Tcpip_{GUID} because another computer on the network has the same name. The server could not start.
4) I tried jimmyc2365 solution and switched the "disable netbios over TCP/IP" for each of the virtual L2TP adapters but unfortunately the internet still froze up.
5) I went back to my error message to double check the bind error on the network adapter and realized that I had disabled netbios on the L2TP but the adapter in question was actually my wifi card. Opening command prompt as administrator I typed netsh wlan show interfaces to confirm this. For folks who use an ethernet cable, simply change this command to netsh lan show interfaces
6) I disabled TCP/IP V6 (worth a shot since I don't use it for making connections)
7) Went to the software manufacturer for my network card (in my case I have an Intel) and grabbed the newest Windows 11 driver which happened to be 22.110.1. I was on 22.70
😎 In device management I went to my wifi card and changed the "mimo power state mode" to NO SMPS
9) Rebooted
I also noticed that Windows Update had updated the Intel chipset recently which may or may not have contributed to this headache, but I did not attempt to find a newer chipset driver since the wifi driver update appears to have made my system happy. I have read other users post that finding a newer network driver wasn't the solution and some users were saying that going back to an older driver that was approved by the laptop/desktop manufacturer ultimately solved it. If you have landed on this forum, hopefully one or more of these steps will bring stability back until Microsoft can harden their OS enough to correct for this elusive error.