NWLink still won't bind for Server Services

[Bob]

I need the help of someone who really knows the NWLink Protocol under XP. On
a standalone PC (no network cable attached) what would cause an event error
2505 claiming a "same name" found:

Date: 9/13/2008
Time: 3:22:48 PM
User: N/A
Computer: PC70
Description:
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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 34 00 00 00 4...

Remember, not connected to the network, completely standalone. What setting
change can I make to stop the PC from finding a "same name" and permit the
Server to Start? I have other XP boxes with NWLink installed and they provide
Server Services just fine. And I have tried to duplicate those functional
settings on the PC with the problem. Still won't run correctly. Please, I
need a real expert.

Client services work. Plug the cat5 back in and connect to a Win98 box with
ONLY NWLink installed there (no TCP/IP). But can't go the other way. Help...

 

[Bob]

Found the ms support page below.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q103470

Seems to imply that the "same name" problem is caused by multiple copies of
netbios in use. I only have one network adapter with one defined connection.
NWLink installs with a line labeled NWLink Netbios. And TCP/IP includes a
WINS Netbios default. These settings DO seem to work on my other XP PCs
running NWLink. Server Services under NWLink are available on these other
machines. So what gives?

Doesn't anybody have any idea what is going on with this error under XP
installing NWLink?