Win 2k Server as test station in a workgroup

[Robbie]

We have an enviroment of win2k pro/xp/98. I have recently
added a win2k server into our workgroup for testing
purposes for some new software, I will not use it as our
network server. When I put it on the network it kicks the
same user who is running w2k pro off the network. Ip
addresses are not the issue. we both go thru the same
print server. However we can't be on the network at the
same time. When we are I try to connect to the print
server and I get the error same name exists on network. I
guess I have misled you a bit- we are not kicked
completely off we can connect to other users. WE have
checked the print server user rights and can't seem to
resolve this problem. Have tried to make the win 2k server
its own workgroup but we get the same issue.

 

[Jim Bean]

I'm thinking that even though you can name the PC's more
then 13 letters, Active directory really only uses the
first 13. So these two names will kick each other off.

server_testing01
server_testing02

They will both be registered as
server_testin

Hope this help.

JB

 

[Danny Slye - [MSFT}]

The problem is with NetBIOS over TCP/IP. NBT only recognizes the first 15
letters of the name, so it sees both machines as server_testing0, thus the
duplicate name on network error.
163409 NetBIOS Suffixes (16th Character of the NetBIOS Name)
http://support.microsoft.com/?id=163409
--------------------

I'm thinking that even though you can name the PC's more
then 13 letters, Active directory really only uses the
first 13. So these two names will kick each other off.

server_testing01
server_testing02

They will both be registered as
server_testin

Hope this help.

JB

__
Danny Slye
Microsoft Support Professional
MCSE

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!