Cant login with secondary domain controller windows server  2003

Posted on 2009-06-28
Medium Priority
Last Modified: 2012-05-07
Ive created a secondary domain controller, until now, Ive done this:

1. Installed 2003 server, joined the domain and runned DCPROMO
2. Ive installed and configure DHCP and DNS.
3.Ive checked that both servers are global catalog servers.

My Primary Sever ip is, and my secondary is
All clients have DNS and (configured through DHCP)

Ive made a test disconnecting the primary domain controller, and after rebooting all client computers are unable to login, they can only login with user credentials already used in that client.

Can you help me?
Thank you.

Question by:_the_reverend
  • 2
  • 2
  • 2
LVL 16

Expert Comment

by:Bruno PACI
ID: 24732432

Can you verify that the SYSVOL share exists on the second DC. A new DC does not bring up the SYSVOL share until it has successfully finished an Active Directory replication, and by the way it also refuse to authenticate anyone.

Did you install the "Support Tools" and check the result of DCDIAG and NETDIAG commands ? These commands will show you a precise report of Active Directory status.
(the support tools are on the Windows 2003 CD).

Have a nice day

LVL 27

Expert Comment

ID: 24732610
Hi there. As mentioned by PaciB, a DCDIAG and NETDIAG should root out any issues on the DCs.
Have you confirmed that the new IP config (ie both DNS servers listed) is actually applying to your clients? Did you configure these options on both scopes? If your first DC was also a DHCP server, your clients will continue to try to contact it to renew the lease. They won't automatically go through a full broadcast DORA process and speak to the new DHCP server until 50% (i think) of the existing lease has passed. From memory, they'll try to contact the source DHCP server, if they can't, then they continue with their existing lease, and therefore not get the config you have put on the new server. Just a thought.

Author Comment

ID: 24732640
Ive Attached the results of both diagnostics, but I dont understand them completley and as how to correct those tests that didnt pass.
Thank you.
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

LVL 27

Accepted Solution

bluntTony earned 2000 total points
ID: 24732661
Are these on the new or old server? I'm guessing it's the new?
Why has the NIC on this server got two IP addresses? Is this intentional? It would cause problems on a DC. Remove the .8 address in the properties of the NIC TCP/IP settings, then run the following commands on the DC:
ipconfig -flushdns
ipconfig -registerdns
net stop netlogon
net start netlogon
This should correct DNS records. Then jut check in your forward lookup zone that you only have one Host (A) record for the server, and that it points to the .5 address.
See if this helps...

Author Closing Comment

ID: 31597718
Thank you, that did it, we used a virtual IP (.8) to avoid SPAMERS using our SMTP server. Dont know how exactly but that was the reason. Why can this virtual ip cause problems to the DC?
Thank you.
LVL 16

Expert Comment

by:Bruno PACI
ID: 24732781

Your DC is a multi-homed server, meaning it has several netcards et several IP addresses.
You must ensure that your DC has NOT registered itself in DNS with bad IP, like these on the "Realtek NIC" : 201.134.44.xxx

If your DC is register in DNS with a IP address that is not reachable from clients you can have trouble like you described. As an exemple let's suppose your secondary DC is registered in DNS with multiple IP addresses : (the good one) and (a bad address coming from the Realtek NIC).
When your first DC is offline, clients request the secondary DNS asking for another DC for the ponderosa.local domain.
The DNS only knows one other DC : monterrey5.ponderosa.local... But it has multiple addresses for this DC. So the DNS server choose one of the addresses for monterrey5 and give it to the client.
Let's suppose the DNS choosed The client cannot reach the DC on this address. The the client suppose this DC is offline and ask the DNS for one more DC but there is no more DC in the list.

You can check which IP addresses are returned by the DNS server byt typing these two commands several times :

PING monterrey5.ponderosa.local

The first command force the client to empty its DNS cache
Now that the DNS cache is empty, the second command force the client to request the DNS server.

Doing this several times you will have several answers. In normal situation all the answer should give you the same IP address. If not then you DNS is polluted with bad IP addresses and you have to fix the IP configuration on the DC.

Have a nice day.

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
I've always wanted to allow a user to have a printer no matter where they login. The steps below will show you how to achieve just that. In this Article I'll show how to deploy printers automatically with group policy and then using security fil…
How to fix display issue, screen flickering issue when I plug in power cord to the machine. Before I start explaining the solution lets check out once the issue how it looks like after I connect the power cord. most of you also have faced this…
Through the video, you can check the migration process of Outlook PST file to PDF. Kernel for Outlook to PDF tool can convert Outlook emails with all attributes like Subject, To, From, Cc, Bcc and other folders such as Inbox, Outbox, Sent Items, Jun…

600 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question