Installing 2nd AD Domain Controller

[jaso]

I have a W2K SBS Server which is PDC for the domain.com domain. It is on 192.168.1.2 ip address.

I wish to setup an additional domain controller on a seperate subnet 10.1.0.0 255.255.0.0 for the same domain name. I have its DNS currently pointing to 192.168.1.2

The routing between subnets is setup correctly. I can browse the PDC and pings are around 100ms and constant.

When i run dcpromo i select "additional domain controller" and am prompted to enter credentials, which are accepted for the domain.com domain. I then enter the domain.com name and click next. I accept all the default file locatons and finally enter my usual admin password for the domain.

The wizard then starts. It will sit at "chaging domain membership of this computer for around 4 minutes" then come up with an error message.

"The attempt to join this domain failed"
"The specified network name is no longer available"

No events are recorded in the event log but i think it could be related to DNS. I have verified connectivity to the PDC during the 4 minutes with a constant ping.

If anyone can shed some light on this i would be grateful.

TIA

 

[adejordan]

The main limitation of SBS2000 is that you CANNOT have more than the 1 DC in the domain, sorry!!!

Regards

Ade Adrian Jordan
MCSE,CCNA,CCA

 

[jaso]

I understood the limitations of the license were that SBS can be installed as the root/first Primary Domain Controller and that subsequent DC's had to be the full Win 2K Server but they could still be part of the same domain?

If i'm mistaken then what are my options for getting AD replication to my 2nd site on the 10.0.0.0 subnet?

 

[adejordan]

Jaso

Sorry, My bad, I was still thinking SBS 4.5.

As for why you cannot join the domain, try flushing the dns cache. Also have you defined the second subnet in AD sites and services? Adrian Jordan
MCSE,CCNA,CCA

 

[jaso]

Yes - ive checked everything. I have secondary DNS running fine on the server. The second subnet is setup in AD sites and services.

"The specified network name is no longer available" - What does that mean? Which network name?

DCPROMO logs show an error 0x40 but it's not documented anywhere.

 

[Sreelu]

Check this issue is with DNS.

check the DNS is Active Directory integrated or not.

if u are not using multiple network cards.. and all the system are connected to the same hub(as i think that.. this is a test u are doing in u'r lab).just install... the Net BEUI. it will solve.. the issue

becoz the problem is..

First u'r system is in u'r domain.com . and it follow the DNS of the domain. so when u wnat to make it a DC.. First it will dissjoin fro the domain.. so it can no longer resolve. name resolutions for domain.com. OK. so it cannot get the. ip of the domain.com ip address.(192...) so it prompot that the domain or network does not exist no more.

confiure the Default Gateway and DNS Server.. correctly.

let me know.. about the result

Srihari Maddula

 

[jaso]

Thanks for the info.

Server 1(DC with active directory) is on a separate subnet (192.168.1.0/24) to the server 2 i am attempting to join (10.1.0.0/16) therefore i cannot use NETBEUI. Both machines have only 1 NIC. I'm routing using hardware routers rather than RRAs.

Server 2 is currently in workgroup mode. Server 2 is listed in server 1's DNS config and that information is also replicated as secondary zones in server 2. Therefore i don't see how it can be losing the network name at this stage.

I agree is probably DNS related.

 

[adejordan]

Will the server join to the Domain as a Member Server?

If so then you should be able to promote it.

Adrian Jordan
MCSE,CCNA,CCA

 

[jaso]

No. I get the same error on simple member server as well.

 

[twiese1]

You need to open up dns in admin tools, open up dns, make sure you have all the correct entries for resources, like, domain, domain controllers etc... You should have all these created by default when you install dns. If you don't have all the proper entries, the new server may be able to ping your dc, but not understand that it is a domain controller. There is a tool called netdiag, it comes on 2000 server disk. I don't know about sbs, but it will check dns for proper entries, and if you use /fix switch it will correct problems in dns. I have used it on server but not on sbs. You may want to research it.

 

[jaso]

Thanks for the info.

I've run the tool on both computers. I can't spot anything obvious, no error messages are displayed and the /fix switch does'nt appear to do anything.

Could it be a SP3 issue? I've read somewhere the net connections service can time-out as it's set too short to 5 seconds. MS recommends increasing this to 15 seconds but i don't know the relevant key to do this. This could also be complete nonense ;-)