Cant login with secondary domain controller windows server 2003

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 10.0.0.1, and my secondary is 10.0.0.5
All clients have DNS 10.0.0.1 and 10.0.0.5 (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.

_the_reverendAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bruno PACIIT ConsultantCommented:
Hi,

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


0
bluntTonyHead of ICTCommented:
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.
0
_the_reverendAuthor Commented:
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.
dcdiag.txt
netdiag.txt
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

bluntTonyHead of ICTCommented:
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...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
_the_reverendAuthor Commented:
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.
0
Bruno PACIIT ConsultantCommented:
Hi,

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 : 10.0.0.5 (the good one) and 201.134.44.172 (a bad address coming from the Realtek NIC).
When your first DC is offline, clients request the secondary DNS 10.0.0.5 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 201.134.44.172. 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 :

IPCONFIG /FLUSHDNS
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.