Extremely slow login issues

I hava client using a terminal server and they are having trouble logging on and off. here are a couple of error messages....

Event ID 1053
Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

Event ID 1517

Windows saved user DOMAIN\USER registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

 This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Event 1508
Windows cannot log you on because your profile cannot be loaded. Check that you are connected to the network, or that your network is functioning correctly. If this problem persists, contact your network administrator.

 DETAIL - Insufficient system resources exist to complete the requested service.


There are a few other ones as well.  

My question is this appears to be  HIVE error. Is this probably correct?

If So what are the best steps to take?

Thanks

Jeff
jaconentAsked:
Who is Participating?
 
ryansotoConnect With a Mentor Commented:
OK i reread your post this machine is a terminal server only right?
I thought it was a domain controller.  Since it is a terminal server its domain controller should not be itself it should be your internal DNS server.
Also to work on the profile issue use UPHclean
http://www.microsoft.com/downloads/details.aspx?FamilyId=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
0
 
ryansotoCommented:
First make sure all DNS point to themselves in TCPIP properties, they should NOT point to an ISP DNS.
Also make sure your clients are receiving dhcp info right - they should also be getting DNS servers internally.
0
 
jaconentAuthor Commented:
They Are using the Domain Controller for DHCP and DNS
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
ryansotoCommented:
Make sure you check the DNS setting on the NIC card on that domain controller
0
 
jaconentAuthor Commented:
should it be set to itself?
0
 
ryansotoCommented:
Yes
0
 
jaconentAuthor Commented:
It is
0
 
jaconentAuthor Commented:
THe Terminal Server is showing the DC as the DNS. The hang up is in the loading personal settings portion of the logon.

It takes 2-3 minutes to apply the personal settings.

I have installed the UPHclean and see if that helps.
0
 
jaconentAuthor Commented:
Thanks for the quick responses and the help!!!!

it worked. appreciate it.
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.

All Courses

From novice to tech pro — start learning today.