Child domain IP addresses

I am replacing an NT 4 server of one of our branches with a new Win 2k3
system. For the purpose of configuring this server, I removed the external
trust to the NT server and delete from AD any reference to the domain and NT
server. I connected this new system to the LAN at the head office (win 2k3)
and run dcpromo to create the child domain.

My problem is that I was only able to setup DNS and AD when the IP address
of this new server is within the range used in the head office LAN. Now I
changed the IP address to reflect the one used at the branch but now I’m not
able to see the parent domain.

What do I have to do to setup 2-way connectivity between parent and child
and keep the IP addresses the way they are? This new server when deployed
will be linked by a VPN connection. We only use static addresses. Is there
something I have to add/or change in the Inter-Site Transports in AD?

Can a child domain have an IP addresses within a different range from its
parent and same subnet?

Parent: xxx.xxx.67.xx
Child: xxx.xxx.84.xxx
Subnet for both: 255.255.255.0

Thanks in advance.

Mike,

As far as I know you can...
Try these:
1) re-change the IP Address of child domain to original
2) try to connect within the same office (it should work) (these 2 steps are
precautionary measures)
3) try to create the VPN, ping from one end and another end
4) Then in AD Site, Create a new site & move the child domain with the
xxx.xxx.84.xxx IP address, & it will take a hell a lot of time to transter AD
objects over wait mate.

Hope this helps

It this does not work, you might need to create the Child domain from the
other end, since it

"Mike" wrote:

> I am replacing an NT 4 server of one of our branches with a new Win 2k3
> system. For the purpose of configuring this server, I removed the external
> trust to the NT server and delete from AD any reference to the domain and NT
> server. I connected this new system to the LAN at the head office (win 2k3)
> and run dcpromo to create the child domain.
>
> My problem is that I was only able to setup DNS and AD when the IP address
> of this new server is within the range used in the head office LAN. Now I
> changed the IP address to reflect the one used at the branch but now I’m not
> able to see the parent domain.
>
> What do I have to do to setup 2-way connectivity between parent and child
> and keep the IP addresses the way they are? This new server when deployed
> will be linked by a VPN connection. We only use static addresses. Is there
> something I have to add/or change in the Inter-Site Transports in AD?
>
> Can a child domain have an IP addresses within a different range from its
> parent and same subnet?
>
> Parent: xxx.xxx.67.xx
> Child: xxx.xxx.84.xxx
> Subnet for both: 255.255.255.0
>
> Thanks in advance.
>