couldn't start..

  • Thread starter Thread starter sushil
  • Start date Start date
S

sushil

I have a main domain controller(DC) which has been
replicated to another domain controller. The problem i am
facing is that i couldn't start the MAIN DC unless and
untill the replicated DC isn't turned on. The MAIN DC just
keeps trying to start with "preparing network connection"
message before logged in. what could be the reason for
this? couldn't i start the MAIN DC untill i turned on the
replicated DC in my network? pls help.
 
Probably a DNS client configuration issue. Check both DC's IP properties. If
both DCs are DNS servers, point the first one at the other DC and the second
entry at itself. You can also make them point to themselves as the first
entry, then the other for the second, but the latter is recommended.

I'm also bettin you're using your ISP's DNS in the entries too. That should
be removed. For efficient Internet resolution, suggest to use a Forwarder.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
thanks ace!!! for your suggestion but i still have a
problem. as i have already mentioned, my MAIN DC named
MAINSERVER & replicated DC named PROSERVER. the MAINSERVER
trying with the message "Preparing for network connection"
before the log in and i couldn't log in unless and untill
i switch on the PROSERVER.

in MAINSERVER TCP/IP properties, the PREFERRED DNS SERVER
has the IP address of MAINSERVER which is the main DC of
my network and the ALTERNATE DNS SERVER has the ip address
of replicated DNS server, PROSERVER, of my network. i had
used the ISP'S DNS in the forwaders in the main DC but i
have removed it. is there any impact of this? hope to get
solution.
 
In
sushil said:
thanks ace!!! for your suggestion but i still have a
problem. as i have already mentioned, my MAIN DC named
MAINSERVER & replicated DC named PROSERVER. the MAINSERVER
trying with the message "Preparing for network connection"
before the log in and i couldn't log in unless and untill
i switch on the PROSERVER.

in MAINSERVER TCP/IP properties, the PREFERRED DNS SERVER
has the IP address of MAINSERVER which is the main DC of
my network and the ALTERNATE DNS SERVER has the ip address
of replicated DNS server, PROSERVER, of my network. i had
used the ISP'S DNS in the forwaders in the main DC but i
have removed it. is there any impact of this? hope to get
solution.
Click to expand...
If the mainserver's config looks like this:
DNS1=mainserver
DNS2=mainserver

and the proserver looks like this:
DNS1=proserver
DNS2=mainserver

Then I don't see why the problem is occuring. If not, try this config. Keep
in mind this may cause 5781 errors. The idea is normally point to the OTHER
server as first and itself as second on each machine, but this is assuming
that both servers are always operational and UP ar all times or at least the
other server is up. Why would you create another DC and keep it offline
anyway?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top