Solved

Windows 2003 AD and NT 4 domains on same network, can't log on to NT 4 Domain

Posted on 2004-09-01
4
161 Views
Last Modified: 2010-03-18
Until this summer we have been running an NT4 domain on our campus.  We added (did not migrate) a Win2k3 Domain this summer and are partially through moving accounts to the new domain.  We have established trusts between the two domains (for access to each side during the move) and haven't had any problems up to today.  This morning we began receiving errors that machines couldn't log on to the NT4 domain because it wasn't avaliable.  We haven't changed anything on the network or servers since yesterday.

We can log on locally to the NT4 DCs, but when we try to log on from a client it won't authenticate.  We've restarted servers, the NETLOGON service specifically, and also tried promoting one of our BDCs to see if there was an issue with our PDC.  No matter what we try we can't log in to the NT4 domain any longer.  

Anyone have any ideas to check? I've double checked WINS and the 1b and 1c entries are resolving correctly. Any other paths to troubleshoot?
0
Comment
Question by:Northwestu
[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
4 Comments
 
LVL 6

Expert Comment

by:chumplet
ID: 11956039
Which domain is DHCP (if you're using that) coming from?  Can any of those boxes ping the PDC and BDC from the NT4 domain?  It sounds like clients are using DNS and/or DHCP from the new domain and thus aren't "aware" of the old domain controllers, but that's just a hunch.

Let me know what you find out!
0
 

Author Comment

by:Northwestu
ID: 11964819
To answer your question, yes, DNS and DHCP are being served from the new domain.  However we also have WINS setup with information for both domains being served and the WINS addresses are being handed out by the new DHCP.

We fixed the problem through a combination of steps.  First, promoted a new PDC for the NT4 side. Second, we recreated the two-way trusts between the domains. Finally, we restared DNS and WINS (which we had tried before all of this).  Don't exactly know why we had to go through this specific combination, but it cleared up our issue.
0
 

Accepted Solution

by:
modulo earned 0 total points
ID: 13181263
PAQed with points refunded (500)

modulo
Community Support Moderator
0

Featured Post

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

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

We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
This article offers some helpful and general tips for safe browsing and online shopping. It offers simple and manageable procedures that help to ensure the safety of one's personal information and the security of any devices.
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
Suggested Courses

622 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