From: John Beckett 

"Hrvoje Mesing"  wrote in
message news::
> First DC, win2K3 server, file server, 3Com PXE server, DHCP service started,
> still, Scope is disabled
> Second DC, Win2K3 server, DHCP started and Scope enabled.
>
> When machines start, they get DHCP lease from Second DC server, still, they
> are pinned into the First servers ARP table as Static and cannot be accessed
> (nor vice versa).

I'm not quite sure what you mean (the arp table as shown by 'arp -a' at
command prompt?). However, I think that disabling the scope on a DHCP
server is a bad idea. You will probably find that the DHCP server is
listening, but since it has nothing to offer clients it sends a NAK
(negative acknowledgement), telling them to go away. I think it would be a
little bit of luck, depending on timing etc, as to whether the second DHCP
server provides the required lease. You certainly won't get a good result.

On the DHCP server with the disabled scode, at command prompt: netstat -an
| find ":67"

I expect you will see that the server is listening on UDP port 67 (despite
the fact that it has no IP settings to offer clients).

I believe you need to disable the DHCP service to temporarily turn it off.
I have done this ... can't quite remember ... I think I just found the DHCP
service in services.msc and stopped it and set Startup = Disabled.

John

--- BBBS/NT v4.01 Flag-5