How to resolve "server could not bind to the transport \Device\NetBT_Tcpip_<UUID> because another computer on the network has the same name" errors?

7,660

Check all your network adapters (under Settings>Network & internet>Advanced network settings) and see if there is a network device, created by some application, that is no longer needed. Delete that network device (Disabled is not enough) using Computer-Manage (Uninstall and also remove driver). I had a similar problem, when trying to connect to a VPN using FortiClient. That error message - EventId 2505 appear. Until I've figured it out, I run command ipconfig /registerdns in order to connect to see the VPN network (after running the command the LAN network start to respond after a around 90 seconds). After clean the unnecessary network adapter, problem was solved. Operating system: Windows 11 Pro Workstation

Share:
7,660

Related videos on Youtube

whattodo
Author by

whattodo

Updated on September 18, 2022

Comments

  • whattodo
    whattodo almost 2 years

    What is the meaning of the below event viewer error and how to resolve it?

    The server could not bind to the transport \Device\NetBT_Tcpip_{645D56E9-F6B3-44C1-B7C9-B5A0503A76ED} because another computer on the network has the same name. The server could not start.

    • Community
      Community over 2 years
      Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking.
    • spikey_richie
      spikey_richie over 2 years
      Sounds like you have 2 machines with the same hostname.
    • whattodo
      whattodo over 2 years
      I did check the local network but it doesnt have other machines with the same name. I have a few VMs running on the same host machine where this error came up but even those havent been named the same.
    • Seth
      Seth over 2 years
      Are those VMs cloned from each other and/or happen to share e.g. the MAC or use the host interface directly?
    • whattodo
      whattodo over 2 years
      No just docker on WSL2. I believe they must be sharing one of the virtual NICs
    • Steerpike
      Steerpike about 2 years
      I'm seeing this issue with a brand-new laptop (windows 11 home). I've recently renamed the laptop and it's still happening. This is a home network and there are only 3 active computers at the moment, and names are definitely different.
    • Admin
      Admin about 2 years
      I searched in regedit and it is related to a VMnetAdapter (from vmware) found in Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Cla‌​ss\{645D56E9-F6B3-44‌​C1-B7C9-B5A0503A76ED‌​}\x where x is a sequential number (identifier). If you don't need vmware, uninstalling it could help or disable NetBIOS over TCP/IP on your vmware adapters.
  • Community
    Community over 2 years
    As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.