Windows XP Pro and a Win2k Domain

  • Thread starter Thread starter Mike Rechtien
  • Start date Start date
M

Mike Rechtien

I have 23 workstations that run XP Pro. I have many many
more that run '98. We'll forget those for now and
concentrate on the XP Pro boxes.

The Win2k domain controler is set up to issue IP addresses
(internal, non-internet routable -- 192.168.10.x) via DHCP.
Problem is that when I turn on the first XP box, it is
*usually* assigned 192.168.10.4. Even if there are no
other IP addresses in use. But since 10.4 isn't in use,
that box is OK.

So I turn on the second XP box. It also gets 10.4. Even
though the DHCP manager shows it in use. Once I 'ipconfig
/release' then 'ipconfig /renew', I get 10.5 and 10.4 shows
up as "invalid - already in use". But the first and second
box work. So, ok...

I turn on the third box. It gets assigned 10.5. Even
though it's in use by the second box. I /release, /renew,
get 10.6, and now 10.5 is listed as invalid/in use.

This goes on for as many XP boxes as I have. What I need
to know is *why*. I have been unable to find much of
anything via google (and even the knowledgebase as I don't
know how to properly word my search query for the problem
I'm having).

Thanks in advance for your help! (And, if you do reply, if
you could shoot me a message at my email address so I know
you replied, I'd appreciate it! )

Mike
 
On the DHCP server properties there is a selection for conflict detection.
Turn it on and set it for 1. It will ping a given requested address before
it hands it out. If it is in use it will assign a different address as long
as there is no conflict. I leave mine on at all times. I never have
duplitcate addresses assigned. Also make sure there are no static entries
on your machines and try a ipconfig /release at a command prompt on one if
it still does it.
 
Any other DHCP servers running? The ipconfig /all will also return the DHCP
server the machine got it's assignment from so you can compare the problem
machines. While it probably doesn't hurt being set at two, the conflict
detection should probably be left at one. I think MS recommends it for
performance reasons. Any reservations on DHCP? Very weird.
 
Back
Top