DHCP and Site Link over VPN

Hi,
Were creating a router to router VPN between our home
office and a remote office. The home office has Windows
2003 with Active Directory and DHCP configured on it. The
remote office has Windows 2003 and will be connected to
the home server as an additional domain controller. We
wanted the remote office to receive its IP addresses from
the home office's DHCP server. Once the office are
connected with the VPN, should a new scope be created on
the DHCP server to accomodate the remote office, or
should we keep them on the same IP/Subnet range were
using?

After the VPN is created between the offices. I was going
to create a Site Link. Can you verify if these steps are
correct.

1. Create a site for the remote office in "Active
Directory Sites and Services". The home office
will already show up by default.
2. Under Inter-site Transport - Make sure both offices
are showing in the "DEFAULTIPSITELINK".
3. Subnet - Create subnet using the IP address of the
server Active Directory is on.

Thanks.

Abby

Why would you want DHCP to work across a VPN link? DHCP is essentially a
LAN application using broadcasts, and these don't cross WAN links. You would
need some tricky DHCP relay setup to get it working, and I really can't see
any point in doing it.

If they are connected by a VPN link, the two sites will be in different
IP subnets. The VPN link provides the means to route between the sites.

The AD Sites console does most of the work for you to set up a site,
move objects between sites and associate a subnet with a site.

"abby" <(E-Mail Removed)> wrote in message
news:1d26301c453d1$48e0f870$(E-Mail Removed)...
> Hi,
> Were creating a router to router VPN between our home
> office and a remote office. The home office has Windows
> 2003 with Active Directory and DHCP configured on it. The
> remote office has Windows 2003 and will be connected to
> the home server as an additional domain controller. We
> wanted the remote office to receive its IP addresses from
> the home office's DHCP server. Once the office are
> connected with the VPN, should a new scope be created on
> the DHCP server to accomodate the remote office, or
> should we keep them on the same IP/Subnet range were
> using?
>
> After the VPN is created between the offices. I was going
> to create a Site Link. Can you verify if these steps are
> correct.
>
> 1. Create a site for the remote office in "Active
> Directory Sites and Services". The home office
> will already show up by default.
> 2. Under Inter-site Transport - Make sure both offices
> are showing in the "DEFAULTIPSITELINK".
> 3. Subnet - Create subnet using the IP address of the
> server Active Directory is on.
>
> Thanks.
>
> Abby

So, I could just use the existing DHCP server at the
remote site for the users private IP addresses even
though this will be configured as an additional domain
controller to the home office?



>-----Original Message-----
> Why would you want DHCP to work across a VPN link?
DHCP is essentially a
>LAN application using broadcasts, and these don't cross
WAN links. You would
>need some tricky DHCP relay setup to get it working, and
I really can't see
>any point in doing it.
>
> If they are connected by a VPN link, the two sites
will be in different
>IP subnets. The VPN link provides the means to route
between the sites.
>
> The AD Sites console does most of the work for you
to set up a site,
>move objects between sites and associate a subnet with a
site.
>
>"abby" <(E-Mail Removed)> wrote in
message
>news:1d26301c453d1$48e0f870$(E-Mail Removed)...
>> Hi,
>> Were creating a router to router VPN between our home
>> office and a remote office. The home office has Windows
>> 2003 with Active Directory and DHCP configured on it.
The
>> remote office has Windows 2003 and will be connected to
>> the home server as an additional domain controller. We
>> wanted the remote office to receive its IP addresses
from
>> the home office's DHCP server. Once the office are
>> connected with the VPN, should a new scope be created
on
>> the DHCP server to accomodate the remote office, or
>> should we keep them on the same IP/Subnet range were
>> using?
>>
>> After the VPN is created between the offices. I was
going
>> to create a Site Link. Can you verify if these steps
are
>> correct.
>>
>> 1. Create a site for the remote office in "Active
>> Directory Sites and Services". The home office
>> will already show up by default.
>> 2. Under Inter-site Transport - Make sure both offices
>> are showing in the "DEFAULTIPSITELINK".
>> 3. Subnet - Create subnet using the IP address of the
>> server Active Directory is on.
>>
>> Thanks.
>>
>> Abby
>
>
>.
>

"abby" <(E-Mail Removed)> wrote in message
news:1daab01c4545a$590ed2b0$(E-Mail Removed)...
> So, I could just use the existing DHCP server at the
> remote site for the users private IP addresses even
> though this will be configured as an additional domain
> controller to the home office?

Yes.
DHCP is primarily a Layer3 entity dealing with Layer3 Networking settings on
machines. It has nothing to do with Windows and would work on Linux, Unix,
Macs, "you-name-it". The fact that DHCP is running on a Windows box is
almost irrelevant, you could almost as easily run it on anything capable.

Active Directory and Sites are a "Windows Networking" thing, it is related
directly to Windows only, and exists totally outside of the OSI Network
Layers. So in other words they live on two different planets and have very
little to do with each other.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com