Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 2505 Source: Server

The server could not bind to the transport \Device\<device name> because another computer on the network has the same name. The server could not start.
This could also happen on a PC with 1 network card - when you have installed NetBEUI together with TCP/IP with NetBIOS over TCP/IP enabled.
I had more or less the same situation like EventID.Net mentioned before. In Virtual Server 2005 R2 I was not able to create a network from guest to home. On the administrative website I could see my network adapter, but when I clicked "OK" and viewed the configuration again, it switched to "None (guests only)”. I uninstalled the network-adapter, rebooted, restarted virtual machine services, and again created a virtual network. Then the configuration was correctly saved.
This event can occur on a Windows 2000 DC that has File and Print Sharing disabled. See WITP74363 for details.
I have two servers (W2k and W2k3). The W2K-Server is multihomed, running ISA-Server and DNS, and the W2k3-Server is running DNS and WINS. The problem occurred after uninstalling the ISA-Server and removing one NIC. After restart, I got error 2505 on the W2k-Server. I resolved the problem by deleting the WINS-entries for the W2K-server with the WINS manager on the W2K3-server.
As per Microsoft: "The server failed to start up a listening endpoint on the network with a given server name because there is another computer on the network that has the same name. Only one computer can host a given network name at any time". See MSW2KDB and ME887416 for more details on this event.

You can configure multiple network interface cards (NICs, also called network adapters) in a computer (multihomed) for use on the same network segment, but no two network adapters on the same segment in the computer can use NetBIOS. When you install NetBEUI on a multihomed computer, it violates this restriction.

In one instance the device, \Device\NetBT_Tcpip_{C8AFA44C-569D-475F-8366-B6E5F91BD740}) pointed to a VMWare virtual interface. The VMWare interfaces both attempted to use a DCHP server to get IP addresses so they got them on the same segment and as explained above, they conflicted as they tried to register the same NetBIOS name. If you can identify the card by searching the registry for the GUID value (for example for the example above search for C8AFA44C-569D-475F-8366-B6E5F91BD740)
Typically this event is followed by event id 4319 from NetBT suggesting to to use the nbtstat -n command to list the names of conflicting computers. Sometimes, the computer conflicts with itself for the reasons mentioned above (multihomed computer).

Examples of devices:
NetBT_Tcpip_{F3752012-F857-494F-AC43-E928094D91EF} - Cisco VPN virtual adapter
NetBT_Tcpip_{C8AFA44C-569D-475F-8366-B6E5F91BD740} - VMWare virtual interface
NetBT_Tcpip_{2B2F08F0-0F5A-4F6D-9EB7-1D88DBCB7363} - Intel network adapter

As per ME314872, this behavior can occur if the File and Print Service component was not selected during the initial setup of the server or if that component is no longer selected. When this occurs, the Server service does not bind to the NetBIOS interface. A Windows-based computer that becomes a backup browser but that does not have file and printer sharing turned on cannot share the browse list with clients. Any computer that is to be included in the browse list must also have file and printer sharing turned on.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.