Solved

Wiindows 2003 Domin Controller not answering authentication requests.

Posted on 2007-11-19
3
189 Views
Last Modified: 2010-04-21
Hello,

I have an interesting problem with a small 2 DC domain:

Background:
My customer had a 2000 server DC and I installed a new Windows 2003 DC following  MS white papers, I did the 2000 to 2003 ADPrep and transferred the FSMO roles to the new 2003 DC.

The new DC is used mostly for file sharing, but it is configured with DHCP, DNS and WINS.

Problem:
Two times the old 2000 server suffered a hardware failure and would not boot, after this happened, only about half of the users could open their shared folder on the server, if I deleted their mapped drive and tried to re-map, it would ask for credentials and when supplied, it would give an error that the “login credentials” have already been tried and have failed.

I found out if I reboot the PC even though they have been rebooted many times before while the mapped drive was attached, then tried to map again it would ask for credentials and accept the login credentials creating the mapped drive.

I noticed that when you do a “set” command from the command prompt, the LOGINSERVER was the 2000 server and not the 2003 server. It seems that it’s using the cached credentials to log on, but not getting authentication from the 2003 server if the 2000 server is unavailable. The 2003 server is set in DHCP as the DNS server and WINS server.  I’m baffled as to why it will not authenticate users trying to use a share on itself.

Any ideas what I should be looking for here?
0
Comment
Question by:JDrobnick
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 30

Accepted Solution

by:
LauraEHunterMVP earned 500 total points
ID: 20316906
Confirm that the 2003 server configured as a Global Catalog server.

0
 
LVL 1

Author Closing Comment

by:JDrobnick
ID: 31410043
It looks like the 2000 DC was a GC, but the 2003 was not, thanks for the quick solution!
0
 
LVL 1

Author Comment

by:JDrobnick
ID: 20355640
Another thing I noticed is that after turning on the GC, I still have issues with some nodes not finding any server to authenticate to, so they use cached credentials. The 2000 DC is currently down with a hardware issue that will take another week to repair, I'm assuming that since the 2003 DC was just configured as a GC, that it is missing something from replication that it can't get because the 2000 DC is down?
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

by Batuhan Cetin Within the dynamic life of an IT administrator, we hold many information in our minds like user names, passwords, IDs, phone numbers, incomes, service tags, bills and the order from our wives to buy milk when coming back to home.…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

734 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