A duplicate name exists on the network.

[Tyaan]

I have a farm of Windows 2000 Professional servers that contains about
700 machines without a domain. We're constantly swapping out and
re-imaging machines, releasing new builds, etc... Sometimes when
machines are re-imaged or replaced with an upgraded version, some of
my scripts start getting the error "A duplicate name exists on the
network". It's becomming more of a problem and is persistent. I
assume it has someting to do with the browse master caching a the
NETBIOS name and info of a server that's been changed. Is there any
way to fix this (other than by referencing machines by IP as this
would get ugly)? here is an example of what happens:

Z:\>psexec \\ws-g01 -u admin -p mypass -s ipconfig

PsExec v1.43 - execute processes remotely
Copyright (C) 2001-2003 Mark Russinovich
www.sysinternals.com

Couldn't access ws-g01:
A duplicate name exists on the network.

Z:\>psexec \\ws-g02 -u admin -p mypass -s ipconfig

PsExec v1.43 - execute processes remotely
Copyright (C) 2001-2003 Mark Russinovich
www.sysinternals.com



Windows 2000 IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : looksmart.com
IP Address. . . . . . . . . . . . : 192.168.0.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Cable Disconnected
ipconfig exited on ws-g02 with error code 0.



.................................................................
Posted via TITANnews - Uncensored Newsgroups Access-=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=-

 

[SaltPeter]

W2K Pro can't be a server in the pure sense of the word. What you have is
W2K Pro stations participating in a Workgroup or in multiple workgroups.

When deploying images, it's a good idea to run sysprep to regenerate the
GUID associated with the OS, names are for human consumption alone. As far
as name collisions in a netbios environment is concerned, you are right
about browse master caching names. But that hat list should scavenge any
remnant names after a total of 51 minutes following a replaced system's
disconnection from network.

Your problem is related to duplicate SIDs, run Sysprep.