New XP home PC, added signed NWLink protocol, but server won't sta

[Bob]

Got a new XP home PC. I have an old DOS PC that must run IPX/SPX (memory
issues) to connect to this new machine. When I installed the signed factory
included NWLink protocol to the new XP machine, the IPX/SPX connection would
not work. When I checked the Event Viewer I found two events with the ID
2505: "The server could not bind to the transport \Device\NwlnkIpx because
another computer on the network has the same name. The server could not
start." and "The server could not bind to the transport \Device\NwlnkNb
because another computer on the network has the same name. The server could
not start.". I then removed the NWLink protocol, disconnected the cat5
network cable (to eliminate all other computer names tho' I already knew
there are no duplicates) and rebooted. Then I reinstalled the NWLink
protocol. The event viewer gives me new editions of the same messages. With
no connection to the network. So why does it refer to a "same name"? Why
doesn't this work straight out of the box? The NWLink protocol is the signed
version that came with the PC. Shouldn't it work? And worse, I bought two of
these PCs and both behave the same way. What's going on?

 

[Pavel A.]

Maybe you need to disable netbios over tcpip, or smth. like that.

-pa

 

[Bob]

Thanks but no help. I have other XP home PCs on the network functioning fine
with the same NWLink network settings. The question to answer is: What would
cause the XP Programs/Administrative Tools/Event Viewer/System to record an
error event ID of 2505 and a description of "The server could not bind to the
transport \Device\NwlnkIpx because another computer on the network has the
same name. The server could not start"? In other words, how can the NWLink
Server detect a same name error when it is the only PC on the network (since
I have tried all this with and without the cat5 network cable connected)?
It's hard for me to imagine that I'm the only one to have encountered this
with these brand new PCs. I have added no other software except to do the
Windows Update to pick up the latest patches. If anyone can help I would
greatly appreciate it!

 

[smlunatick]

Thanks but no help. I have other XP home PCs on the network functioning fine
with the same NWLink network settings. The question to answer is: What would
cause the XP Programs/Administrative Tools/Event Viewer/System to record an
error event ID of 2505 and a description of "The server could not bind tothe
transport \Device\NwlnkIpx because another computer on the network has the
same name.  The server could not start"? In other words, how can the NWLink
Server detect a same name error when it is the only PC on the network (since
I have tried all this with and without the cat5 network cable connected)?
It's hard for me to imagine that I'm the only one to have encountered this
with these brand new PCs. I have added no other software except to do the
Windows Update to pick up the latest patches. If anyone can help I would
greatly appreciate it!

MWLink (SPX/IPX) was the original networking protocol used to connect
to a Novell Netware server (versions 2 to 5???.) It might be
searching for a Novell server but does not find one.

 

[Bob]

Thanks but the PC I'm trying to configure with NWLink is the server. And
adding a protocol successfully should not depend on finding any other PC on
the network. It might prevent completion if it did find a duplicate name as
seems to be happening here except for the fact that I have the PC in question
completely isolated (not connected by cat5 cable).

Nope, this problem is some sort of internal mis-configuration OR this
version of the MS NWLink protocol is intentionally designed to act as a
client only (bombs the server and records a misleading excuse in the event
viewer, choose your own reason why...). Why else would a new out of the box
PC come with a standard protocol that doesn't work. I've upgraded to SP3 and
all went fine. Still can't enable NWLink to provide server services.

 

[smlunatick]

Thanks but the PC I'm trying to configure with NWLink is the server. And
adding a protocol successfully should not depend on finding any other PC on
the network. It might prevent completion if it did find a duplicate name as
seems to be happening here except for the fact that I have the PC in question
completely isolated (not connected by cat5 cable).

Nope, this problem is some sort of internal mis-configuration OR this
version of the MS NWLink protocol is intentionally designed to act as a
client only (bombs the server and records a misleading excuse in the event
viewer, choose your own reason why...). Why else would a new out of the box
PC come with a standard protocol that doesn't work. I've upgraded to SP3 and
all went fine. Still can't enable NWLink to provide server services.

I doubt very much that you are setting a Novell Netware server. You
may have to "uninstall" an "Novell" client module that might show up
(Client Service for Netware, Client 32) and the "File and Printer
sharingf for Novell Netware."

 

[Bob]

Thanks for the reply. My current target is to simply install NWLink under the
XP OS without causing an error 2505 in the System section of the Event
Viewer.

Error 2505:
"The server could not bind to the transport \Device\NwlnkIpx because
another computer on the network has the same name. The server could not
start."

My Logic:
Since I am totally isolating the XP computer (no network cable, no wireless
NIC) no other PC is physically involved. So this "same name" error must stem
from some setting in the isolated XP computer itself.

The BIG question: What setting is causing this error 2505?