Re: New XP home PC, added signed NWLink protocol, but server won't
- From: smlunatick <yveslec@xxxxxxxxx>
- Date: Fri, 12 Sep 2008 10:03:40 -0700 (PDT)
On Sep 12, 1:14 am, Bob <B...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
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!
"Pavel A." wrote:
Maybe you need to disable netbios over tcpip, or smth. like that.
-pa
Bob wrote:
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?
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.
.
- Follow-Ups:
- References:
- Prev by Date: Re: Win2k8 - Guest FTP Access issue
- Next by Date: Problems with Internet Access through VPN
- Previous by thread: Re: New XP home PC, added signed NWLink protocol, but server won't
- Next by thread: Re: New XP home PC, added NWLink protocol, server claims same name
- Index(es):
Relevant Pages
|
