AD Domain Controller Issue

  • Thread starter Thread starter JohnB
  • Start date Start date
J

JohnB

Scenario - 2 DC's, DC1 and DC1, primary DNS is DC1, DC2 is
alternate DNS, when I shutdwon DC1 to test the DC2 DNS it
takes along time to logon on and the logon script that
handles the drive mappings takes forever to run. The drive
mappings all error out because no logon server is
available to handle the logon request. DC2 is up and
running, why are the drive mappings erroring out? DC2 is
up and functioning.

Any help would be appreciated!

Thanks - John
 
You are not testing DNS you are testing the lose of DC1. What happens when
you stop the DNS service on DC1.
 
Do you see any replication issues between these two (ie; event logs errors
etc and you can create a junk user on one and see it appear on the other
etc). Do both dc's have good dns info in their forward lookup zone for your
doamin (you can ping the domain name and get a reply as well as the full dns
name of each server). Are these two dc's addresses for dns both being
handed out via dhcp or statically assigned to your clients? Clients need to
be pointed to both for dns, and Nowhere else. If you need outside dns
resolution (ISP etc) set up a Forwarder. If the clients do have other dns
addresses listed, clear them out then run "ipconfig /flushdns" and then
"ipconfig /registerdns".

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
I created an junk user and it replicated fine. I guess my
main issue is why the drive mappings don't work when DC1
is down? DC2 is on the same subnet as DC1. The DC ip
addresses are statically assigned.
-----Original Message-----
Do you see any replication issues between these two (ie; event logs errors
etc and you can create a junk user on one and see it appear on the other
etc). Do both dc's have good dns info in their forward lookup zone for your
doamin (you can ping the domain name and get a reply as well as the full dns
name of each server). Are these two dc's addresses for dns both being
handed out via dhcp or statically assigned to your clients? Clients need to
be pointed to both for dns, and Nowhere else. If you need outside dns
resolution (ISP etc) set up a Forwarder. If the clients do have other dns
addresses listed, clear them out then
Click to expand...
run "ipconfig /flushdns" and then
 
You are correct I want to test the loss of DC1. The loss
of DC1 shouldn't affect any logins should it? DC2 is up
and running and should be able to handle all logon
requests correct? User's cannot get theeir drive mappings
when DC1 is down, that is my main concern.

When I shutdown the DNS service on DC1 I still ping by
name and IP and still reach the net.

Thanks!

Can't stop the DNS service on
-----Original Message-----
You are not testing DNS you are testing the lose of DC1. What happens when
you stop the DNS service on DC1.

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
Scenario - 2 DC's, DC1 and DC1, primary DNS is DC1, DC2 is
alternate DNS, when I shutdwon DC1 to test the DC2 DNS it
takes along time to logon on and the logon script that
handles the drive mappings takes forever to run. The drive
mappings all error out because no logon server is
available to handle the logon request. DC2 is up and
running, why are the drive mappings erroring out? DC2 is
up and functioning.

Any help would be appreciated!

Thanks - John
Click to expand...


.
Click to expand...
 
Has DC2 taken on the FSMO roles?
If not you'll need to seize them, via users & computers
mmc - change operations master. If not via the mmc, then
by using ntdsutil.
I suspect once you get DC2 to take on the FSMO roles
you'll have things working again.
Iain
 
Back
Top