DHCP Nightmare...

[Steven]

Recently had a DHCP machine crash.

Installed new machine, using same name, same workgroup,
same domain. However, now, anytime a machine boots up,
they are receiving the error, "Duplicate name exists on
the network," and when I install new machines, they will
not allow me to join my specified workgroup...I receive a
similar message.

Any ideas out there in never-never land?

Thanx.

 

[Doug Sherman [MVP]]

This problem arises because client machines have address leases that your
new server knows nothing about. When clients boot up they attempt to renew
these no-longer-existent leases, and their old addresses may already have
been assigned to another machine. Eventually, the problem will go away as
the old leases expire - unless they were set to never expire.

You can go to each DHCP client and run: ipconfig/release. If this is
successful, you should be able to run ipconfig/renew and get a new address.
If ipconfig/release fails, the machine has assigned itself a private
address, and ipconfig/renew should work.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Steven]

I thought that is the way it should be happening as well,
but unfortunately it is not. The client leases were set
to one day...it's been a week now. And the error is
occuring even on the STATIC assigned workstations.

Is there just something I'm missing?

Thanx.

 

[Doug Sherman [MVP]]

Hmmm. Make sure that the server's old machine account is deleted in Active
Directory - you may want to have the server disjoin the domain, delete its
present account, and then rejoin. Make sure you exclude the DHCP server's
IP address from the scope and make sure the DHCP server is Authorized.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Steven]

All the below mentioned has been done.

I'm at a complete loss for why this is occuring. The only
thing that seems to keep the error from rearing its ugly
head is when I manually disable NETBIOS in the TCP/IP
properties...but we all know that is not a solution nor
an option.

Any other ideas?

Thanx yet again.

 

[Doug Sherman [MVP]]

Ooops - I forgot: Open the DNS console and delete any host and PTR records
for problem DHCP client machines.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Steven L Umbach]

In addition to Doug's advice you might also want to go into the DHCP Management
Console where you can select the server/properties/advanced and enter one or two for
number of conflict detection attempts for a couple weeks but I would make a note to
disable it after that as it will delay dhcp issue process a bit. . --- Steve

http://www.microsoft.com/windows200...en/server/help/sag_dhcp_imp_bestpractices.htm
http://tinyurl.com/36vh7 --- same link as above, shorter.

 

[Guest]

This may also be that WINS has machine names linked to old
addresses and to the same name but different IP for your
workstations. You may want to check and see if old IP's
are still linked to the computers and then have the WINS
scavenge for the new IP and machine names.

 

[Steven]

Any other suggestions, guys?

Thanx.

-----Original Message-----
In addition to Doug's advice you might also want to go into the DHCP Management
Console where you can select the

server/properties/advanced and enter one or two for

 

[Steven]

Cool...but I'm not using a WINS machine.

Any other suggestions?

Thanx.

P.S. I think this whole mess might have something to do
with that P.O.S. invention of Microsoft called "Master
Browser." Ideas?

Thanx.

 

[Jetro]

Just curious how the network's running in static configuration when this
DHCP machine ain't up.
Un-authorize DHCP server, disjoin the domain, recreate machine account, and
go reverse; Install DHCP server on any other DC/server etc etc etc - let's
locate it.

 

[Roland Hall]

I thought that is the way it should be happening as well,
but unfortunately it is not. The client leases were set
to one day...it's been a week now. And the error is
occuring even on the STATIC assigned workstations.

Static IP workstations do not communicate in the DHCP messaging.

Is there just something I'm missing?

No. We're missing something. Doug said you could ipconfig/release
ipconfig/renew manually at the workstation. You never stated whether or not
you tried that.

I went through the scenario you are in, except it was with NT Server 4.0 and
I moved the DHCP server to another server. All of my dynamic clients were
on a 2-day lease. Manually releasing/renewing was the only solution. Some
workstations experienced no issues at all, however, no static IP addressed
workstations were affected by the move.

--
Roland

This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose.

-Technet Script Center-
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/scriptcenter/default.asp
-MSDN Library-
http://msdn.microsoft.com/library/default.asp