Active Directory Windows Server 2003

[150580]

Hi All,

Am stack somewhere, I want to establish active directory btn two networks.The two networks are connected via cisco routers. The problem is the AD Server which is child domain can't reach the Domain i.e. using nslookup domain_name but I
can reach it through ping command.

Anyone with the solution?
thanks

 

[Zelandakh]

Have you opened up any ports between the 2 domains? Is 3268 open?

 

[TechyMcSe2k]

How is your DNS set up to resolve in both directions? Do you have DNS on the Child domain to resolve the parent domain? And if it is a child domain; how did it become that? Did you previously have a AD trust going over a vpn?

Did these networks function properly before your post and now it is broken?

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

 

[150580]

Zelandakh, Ports on Router or on the Server?

Thanks

 

[150580]

Techy,

Actually I only have the DC with DNS and its working fine, am sure of it, Now I want to create a child domain, but the thing is when am trying resolving with server to host child domain, I can not see the parent domain! i.e. Parent Domain resolution:- Server: server name
Address: IP Address

Name: Parent Domain name
Address: IP Address

Server to host child domain resolution:-
Server: Unknown
Address: Parent IP Address

DNS request timed out.
time out was 2 seconds.


DNS request timed out.
time out was 2 seconds.

***Request to UnKnown timed-out

Should I install DNS on this Server or just put Parent Domain DNS


Thanks.

 

[TechyMcSe2k]

How To Create a Child Domain in Active Directory and Delegate the DNS Namespace to the Child Domain

http://support.microsoft.com/kb/255248

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

 

[Zelandakh]

You need the routers to be allowing the traffic through. Follow the above guides but do check the ports are open.

 

[pasupport]

If the name of you DC does resolve publically (I recommend this) then you will need to point the new system to the correct DNS resolver for you internal domain.

So say you have your DC at 10.10.1.4 serving DNS and a secondary DNS service running at 10.10.1.5 you need to set the Preferred DNS and Alternate DNS server to 10.10.1.4 and 10.10.1.5

Also make sure your new DC is on a different subnet so if you are currently using 10.10.1.4/24 make the new on 10.10.2.4/24

Since the 10.10.x.x is non-routable you will of course need to setup a routing table to router 10.10.1.x and 10.10.2.x between the routers.

BTW if you are running EXchagne on your DC your going to have replication issues.


--
Visit my website site a pasupportsolutions.com for cool tips and tricks

 

[150580]

Thank You All.

I got the solution, these 2 commands were missing on both routers:- Domain Name and IP Name Server

Cheers!

 

[FredMackie]

By the way, there's some Windows Server 2003 Active Directory webcasts on

http://www.microsoft.com/events/series/windowsserver2003.aspx.