Solved

Users unable to logon after switch to windows 2003 domain from windows nt4.0

Posted on 2006-06-15
6
354 Views
Last Modified: 2010-03-19
hi,
this is extermemly urgent, as per instructions in an attempt to upgrade our domain to active directory/win2003 server i introducted a temp nt 4.0 server to our nt domain and prompoted to pdc, i then took it off line and upgraded to 2003 server, all appeared to be ok but now users are finding they can log on but cna't connect to another windows 2003 server which contains all application data etc.  the only other change to the server that they can't log into is that i prompoted it to a global catalog server.  help!  there are two nt 4.0 bdc's on online (mail server) and one offline in case of problems!  

users are getting the following error when attempting to access a network drive : r:\is not accessible.

an attempt was made to logon, but the network logon server was not started.

i noticed that the netlogon service on the existing server tha tusers can't access is stopped and reports the following error when i try to start it :  could not stat the ntelogon server on local computer.  error 1355 :  the specified domain does not exist.  

any help would be greatly appreciated.  tony
0
Comment
Question by:spower22
6 Comments
 
LVL 4

Accepted Solution

by:
shard26 earned 500 total points
ID: 16912282
you should post this under
Operating Systems - Windows Server 2003

It will get answered faster.
0
 

Author Comment

by:spower22
ID: 16912374
thanks
0
 
LVL 4

Expert Comment

by:ansh_gupta
ID: 16912677
check the DNS..
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
LVL 7

Expert Comment

by:Kumar_Jayant123
ID: 16914059
Hi,

I have some questions befor we proceed.

What is the name of your domain. In NT days the name of the domains would be single level and in windows 2000-2003 domain names are FQDN. If in the upgrade process you havent changed the name to FQDN the DNS will not process properly. (I.e In NT your domain name is "DOMAIN" and in 2003 it should be "domain.com").

Check this out.
http://support.microsoft.com/kb/300684

If this is the case you need to do that on the AD server and the client as well.

If you have already done this check the DNS and the client setting that they are pointing to the correct DNS or not.

Run Netdiag and DCDIAG and check for errors. It will be in the support tools on the windows 2003 CD.

Hope this helps
Kumar
0
 
LVL 10

Expert Comment

by:Sorenson
ID: 16915141
you promoted the temp pc to pdc, then removed it from the network?
The old bdc should be removed from the network, not the pdc. PDC should stay on network during upgrade process, the bdc (as a backup to revert to the nt domain) removed and until upgrade is complete then brought back into the network to sync.

The server that cannot be accessed, can it see the other servers?  What type of errors are in its event log?
After you upgraded the temp server to 2003, did you bring it backonline with the other servers?  Did it have time to syncronize?
The server that users cannot connect to, was it a member server and then promoted to a DC after the temp server was brought online?
Make sure all servers point to the temp dc as DNS and make sure that the domainname specified in the ip properties is the AD domain name that you choose during the upgrade process.




0
 
LVL 10

Expert Comment

by:Sorenson
ID: 16915160
sorry - didnt notice duplicate thread was already worked out.. glad to hear things turned out well.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

830 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