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 or ping 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: 192.168.67.xx
Child: 192.168.84.xxx
Subnet for both: 255.255.255.0

Thanks in advance.

Hi Mike,

This should work if you have setup your network correctly.

Check the packet trace from your child domain controller to your root domain
controller. E.g. if your child domain controller has IP address 192.168.84.1
and your root domain controller has IP address 192.168.67.1 then type this
in child domain controller

tracert -d 192.168.67.1

also run this on your root domain controller

tracert -d 192.168.84.1

This might give you some idea where packets stop (e.g. could there be a
filter setup on firewall or router...?).

After you fix this problem, my advice is to setup sites (in sites and
services MMC). This will enable your clients to find domain controller that
is nearest to them...

--
Mike
Microsoft MVP - Windows Security

"Mike" <(E-Mail Removed)> wrote in message
news:35AF1CF9-9AF3-485F-9EA0-(E-Mail Removed)...
>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 or ping 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: 192.168.67.xx
> Child: 192.168.84.xxx
> Subnet for both: 255.255.255.0
>
> Thanks in advance.