Win2K network issues

K

kevin

I have a Win2K SP4 application server running in a NT4
domain that is giving me weird network problems. The
event log shows the following 3 errors:

Event ID 2505 source Server
"The server could not bind to the transport XX because
another computer on the network has the same name. The
server could not start."
The server does have 2 nics but there absolutely is not
another computer on the network with the same name. The
only protocal running is TCP/IP. NBTSTAT -n shows:

C:\>nbtstat -n

Local Area Connection 2:
Node IpAddress: [161.120.120.157] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
SGTFEDI <00> UNIQUE Registered
SGTF.SGCNA <00> GROUP Registered
SGTF.SGCNA <1E> GROUP Registered

Local Area Connection:
Node IpAddress: [161.120.120.133] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
SGTFEDI <00> UNIQUE Registered
SGTF.SGCNA <00> GROUP Registered
SGTF.SGCNA <1E> GROUP Registered
INet~Services <1C> GROUP Registered
IS~SGTFEDI.....<00> UNIQUE Registered

Another error in the event viewer is event id 4319 source
NetBT
"A duplicate name has been detected on the TCP network."

Finally Event id 7024 source Service Control Manager
"The messenger service terminated with service specific
error 2119"
I have seen a couple of posts elsewhere about this code.
One talks about the username being the same as the
computer name which is not true for me and the other
talks tells me to rename the computer to a unique name.
Well all these errors are telling me that my name is not
unique on the network whereas I know that it is.

As far as applications running on the server, I do have
MS Services for Unix 2.0.

The problems I am having include: although I can ping by
name when I try to map to a share on the server I get "A
device attached to the system is not functioning".
Messenger service will not start. I cannot remotely
access event viewer, it gives me a permissions error.

Help would be appreciated. Thanks.
 
C

Chris Knapp

Looks like you have 2 NIC's in your machine, both plugged into the same
subnet. That's a no no (Unless you are using special loadbalancing or
teaming software provided by your NIC vendor.)
 
K

Kevin

I may have resolved this issue. A posted stated: Error
was due to WINS already having a static entry for the
server. Problem was resolved by deleting relevant
entries from WINS. Do a NBTSTAT -RR to update WINS
following a reboot.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top