Solved New error in Event Log after upgrading to Windows 11.

After I upgraded to Windows 11 from Windows 10 I started seeing the following two error message in my event log after I boot W11. The event id is 2505

The server could not bind to the transport \Device\NetBT_Tcpip_{B4EE6689-32C7-4A57-B7CE-588FCE891CD5} because another computer on the network has the same name. The server could not start.

The server could not bind to the transport \Device\NetBT_Tcpip_{E21018FF-9450-49DE-AA46-F80745F508C7} because another computer on the network has the same name. The server could not start.

When I execcute nbtstat -n I get the following which indeed shows a name twice. I don't know if this is related to the event log error or not. My question is how do I fix it so I no longer get the error message? I tried a few things I found online but nothing helped. Network stuff is not in my wheelhouse.


VPN - VPN Client:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Ethernet 2:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Ethernet 3:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

VMware Network Adapter VMnet1:
Node IpAddress: [192.168.30.1] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
GARY-PC <20> UNIQUE Registered
GARY-PC <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered

VMware Network Adapter VMnet8:
Node IpAddress: [192.168.9.1] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
GARY-PC <20> UNIQUE Registered
GARY-PC <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered

Ethernet:
Node IpAddress: [10.0.0.101] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
GARY-PC <20> UNIQUE Registered
GARY-PC <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered

Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Wi-Fi:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Local Area Connection* 2:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Local Area Connection* 3:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Make sure File and Printer Sharing for Microsoft Networks is enabled on the interface.

I just took a look at my network adapters using a Nirsoft utility and the two errors point to my two VMware Virtual Ethernet Adapters The names end with VMnet1 and VMnet8. I don't see any duplicate names in the output of the utility and their IP addresses are different. I believe my WIndow VM's are also called Gary-PC. At least I have something to go by now. Disabling one or both of them might 'fix' the problem but then I would probably lose network access in my virtual machines.

I see the similar errors in my log too. But my system is fairly straightforward - no VM or VPN for example.

The server could not bind to the transport \Device\NetBT_Tcpip_{5DB53DEF-825B-46A5-98BE-8380AA827093} because another computer on the network has the same name. The server could not start.

The nbtstat out looks like this

C:\Windows\system32>nbtstat -n

Ethernet:
Node IpAddress: [192.168.1.149] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
RFSMITH <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
RFSMITH <20> UNIQUE Registered
WORKGROUP <1E> GROUP Registered
WORKGROUP <1D> UNIQUE Registered
☺☻__MSBROWSE__☻<01> GROUP Registered

WiFi:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Local Area Connection* 1:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Local Area Connection* 2:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Problem solved. For both of my VMware Adapters I disabled NetBIOS over TCP/IP. The internet works fine under my VM's.