DHCP on W2K3 not working with remote site clients

I have a Windows NT4 (PDC) running DHCP, DNS and WINS. I want to migrate or
reconfigure the W2K3 Server to take over these services.

When I configure the W2K3 Server with the exact same scopes. I have found
that all my remote site clients are not finding the new DHCP Server
(10.0.0.20). The old DHCP Server (10.0.0.2) is still showing up in the local
clients ipconfig screen even after doing a release and renew.

Clients that are on the local subnet are getting new address assigned by the
new DHCP Server successfully, only my remote sites are not.

Local subnet are using 10.0.0.x
Remote subnet sites are using:
10.1.0.x
10.2.0.x
10.3.0.x and so on.

--
Troy Titus
Network Administrator

Since DHCP discovery uses broadcast and the latter one doesn't "travel"
across the subnet boundary (router), you will need a relay agent that can
pass the BOOTP traffic through.

Here's an article which sheds more light on the subject:
http://www.windowsitlibrary.com/Content/329/06/5.html

--
Arek Iskra
MVP for Windows Server - Software Distribution


"Troy Titus" <(E-Mail Removed)> wrote in message
news:E473D218-F16C-4286-9BC7-(E-Mail Removed)...
>I have a Windows NT4 (PDC) running DHCP, DNS and WINS. I want to migrate
>or
> reconfigure the W2K3 Server to take over these services.
>
> When I configure the W2K3 Server with the exact same scopes. I have found
> that all my remote site clients are not finding the new DHCP Server
> (10.0.0.20). The old DHCP Server (10.0.0.2) is still showing up in the
> local
> clients ipconfig screen even after doing a release and renew.
>
> Clients that are on the local subnet are getting new address assigned by
> the
> new DHCP Server successfully, only my remote sites are not.
>
> Local subnet are using 10.0.0.x
> Remote subnet sites are using:
> 10.1.0.x
> 10.2.0.x
> 10.3.0.x and so on.
>
> --
> Troy Titus
> Network Administrator