Server Error 2505 in Event Viewer
losada31
Posted messages
4
Status
Member
-
losada31 -
losada31 -
Hello
Every time I start my PC, I have two errors in the event viewer:
"The server could not bind to the transport \Device\NetBT_Tcpip_{ABC1506E-DDF4-4E68-B9EF-3FBA5E57082C} because another computer on the network has the same name. The server failed to start."
I changed the name of the PC but the same issue occurs. The PC is all alone without being on a network.
I don't understand what's happening.
Thank you in advance.
Every time I start my PC, I have two errors in the event viewer:
"The server could not bind to the transport \Device\NetBT_Tcpip_{ABC1506E-DDF4-4E68-B9EF-3FBA5E57082C} because another computer on the network has the same name. The server failed to start."
I changed the name of the PC but the same issue occurs. The PC is all alone without being on a network.
I don't understand what's happening.
Thank you in advance.
6 answers
Hello,
The error may stem from the fact that two network adapters (either due to a virtual machine or Ethernet/Wifi...) are using Netbios on the same segment.
https://www.betaarchive.com/wiki/index.php/Microsoft_KB_Archive/103470
In the presence of a virtual machine, the situation is more likely to occur if it is not configured in bridge mode (which uses the host's connection) and if each adapter does not have a fixed IP assigned as the gateway of the box or router.
Alternatively, if it remains functional for a specific network adapter, you can disable Netbios through Network and Internet settings - change adapter options - concerned adapter:
IPv4 protocol (if applicable) - properties - advanced - WINS.
Failing that, a hacky solution is to disable Netbios, which you don't need if you don't have a local network and which is also a potential security flaw:
In Windows services, switch to stop and disable Netbios assistance.
The error may stem from the fact that two network adapters (either due to a virtual machine or Ethernet/Wifi...) are using Netbios on the same segment.
https://www.betaarchive.com/wiki/index.php/Microsoft_KB_Archive/103470
In the presence of a virtual machine, the situation is more likely to occur if it is not configured in bridge mode (which uses the host's connection) and if each adapter does not have a fixed IP assigned as the gateway of the box or router.
Alternatively, if it remains functional for a specific network adapter, you can disable Netbios through Network and Internet settings - change adapter options - concerned adapter:
IPv4 protocol (if applicable) - properties - advanced - WINS.
Failing that, a hacky solution is to disable Netbios, which you don't need if you don't have a local network and which is also a potential security flaw:
In Windows services, switch to stop and disable Netbios assistance.