Windows Event content

The server could not bind to the transport \Device\NetBT_Tcpip_{A1E0D4B2-6F23-4EE8-B58B-1F65BA98B7DC} because another computer on the network has the same name. The server could not start.

字面理解无法解决，因为是自己的路由器，上级网络里面应该是没有同名的计算机。遂google;

结论

This can safely be ignored. It’s the result of the Browser service trying to figure out which computer on the network subnet is the most trustworthy. It’s a throwback to Windows NT 4 days.

In a peer-to-peer Windows network, Windows computers try to maintain a list of computers on the same network subnet. On each computer maintains it’s own list, but also the computers will participate in a “master browser election” on the network which will determine who is the most authoritative computer. An election process can be called for by any computer, and computers seemingly call for elections at the drop of a hat.

If all the computers on your network were running NetBIOS/NetBEUI or IPX/SPX and you lacked a WINS server this would be a much more valuable service, but DNS has essentially completely replaced this service (as well as WINS). If you ever go to Network or My Network Places, the devices you see here were populated by the Browser Service. In my experience, this list is also generally incomplete. Windows 2000 computers don’t talk well with Windows XP and later systems, for example, because protocol changed to TCP/IP. Browser doesn’t work through most software firewalls, either.

The service is present on Windows Vista and 7, but it is not necessary and is safe to disable. It’s there completely for legacy support.

闲话

这TM又是microsoft的锅，如果真如上述描述的那样，为什么win11还会有这个问题。