• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 380
  • Last Modified:

Login process never completes

We originally setup a fairly basic Windows network. It included Windows XP Pro clients connected to a single Windows 2003 Server. The server did hand off some tweaks in the domain policy and all worked well when connecting to this server.

A couple of months ago we migrated the all of these workstations to connect to another Windows domain managed by a different W2003 Server with a different AD (and we also demoted the original W2003 server so it was simply a member server).

Now on random occassion when a user try and login they are able to enter their user id and password, but after they click ok the login process never completes. The screen goes to a blank blue screen and hangs. Often I force a shutdown on the workstation, wait a minute and then log back on and then the login process completes as it should.

Any suggestions on how to rectify this situation?
0
bnrtech
Asked:
bnrtech
  • 4
  • 2
  • 2
1 Solution
 
AmitIT ArchitectCommented:
Increase RAM in your Domain controller. I assume DC is unable to process all login request. Did you made any changes to kerberos life time age? By default it is 10 hours
0
 
ChiefITCommented:
If these are DHCP clients, DHCP will pass down the DNS server's IP address. After demoting your server, you also probably removed DNS and/or removed it from the network. So, your clients are looking for a DNS server that doesn't exist, AND that DNS server is suppose to point to the direction of your authentication server, (which it can't find now).

Log onto the DHCP scope options, remove any non-existing DNS servers.
0
 
bnrtechAuthor Commented:

amitkulshrestha - I will check out the memory on the DC on Monday

ChiefIT - All clients have been assigned a static IP. I will reconfirm that they have the correct IP for the active DNS server
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
bnrtechAuthor Commented:

Also I am not 100% certain this is the case, but I do believe what I am about to detail is true. At least informally I have noticed this pattern to be true.

Recall that originally we were connected to a Windows domain (Domain A) and then migrated to a new Windows domain (Domain B).

With that said, I am pretty certain that the login process not completing is specific to user that were originally created on Domain A and then migrated to Domain B. I have not seen the issue occur for users that had their user account created after we completed the migration to Domain B
0
 
AmitIT ArchitectCommented:
Move user to different OU and block all GPO iheritance and then test it. If it logs in fast. Then you need to look into GPO or any script which is used while login process
0
 
ChiefITCommented:
You will probably have to rejoing the new domain.
0
 
bnrtechAuthor Commented:
sorry for the delay. it was an operational nightmare with the security folks. the approved answer was to wipe and rebuild the computers and no they are ok.
0
 
bnrtechAuthor Commented:
This was the solution that we implemented to resolve the matter
0
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

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

  • 4
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now