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 System channel, you see:
Log Name: System
Source: Server
Date: 10/25/2021 3:01:46 PM
Event ID: 2505
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: darbydoo
Description:
The server could not bind to the transport \Device\NetBT_Tcpip_{C0E1EDC5-9B33-4911-A3B3-AE69C8115AF6} because another computer on the network has the same name. The server could not start.
This can be seen when booting up, repeatedly disabling and enabling a RDMA NIC, or by a network adapter that goes offline and online for some reason. This leads to multiple SMB server service notifications about the same network interface that has already been bound to the SMB server. You can ignore this event's description, there is not a duplicate computer and the Server service is not stopped. This SMB event is purely cosmetic. We plan to fix this in a later update to Windows.
Update 8/8/2022
Hi everyone. I've been gone for a few months, not ignoring your comments. Important clarifying point: your reported issues of network disconnects have nothing to do with this SMB event and blog post. You have a legitimate but separate issue. The SMB event is just a symptom of a disconnected network in general - there's nothing going on here with SMB and no way for me to help you, as much as I'd like to. You need to work with your PC's manufacturer or MS Support to troubleshoot the networking itself.
- Ned Pyle
Microsoft
