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

Very slow login into my DC on server 2008

G'day
Server 2008
It is a VM
I've read about this problem regarding clients logging into a domain where it would take up to 4 minutes on the Welcome screen and 6 minutes on the 'Applying User Settings'. My problem is me the domain admin logging into the server itself as domain admin. It takes pretty much 10 minutes to login. Just started happening about a month ago. No updates have been applied. I have deleted the mapped drive it had 3 weeks ago but it still happens. No printers are installed. There are 2 DC's but it's just the one that has the problem. This is a VM.
2 events are logged. The first one happens when the Welcome screen changes to 'Applying User Settings'
Event ID: 6005
Source: Winlogon
Description: The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (Logon).
and the 2nd event happens when the desktop finally comes up
Event ID: 6006
Source: Winlogon
Description: The winlogon notification subscriber <GPClient> took 313 second(s) to handle the notification event (Logon).
Seeing that it takes pretty much 10 minutes every time I'm trying to find out where I can make a change.
Any ideas?

Thanks all,
BW
0
bwinkworth
Asked:
bwinkworth
  • 3
  • 3
  • 2
2 Solutions
 
Joseph MoodyBlogger and wearer of all hats.Commented:
Are any folder redirection policies being applied? Have you enabled verbose mode (Computer Config\Administrative Templates\System\Veborse vs normal status messages =enabled).
0
 
nettek0300Commented:
I would start by checking your DNS settings on the DC.  Make sure the IP addresses of the DNS server are valid and that it is not pointing to itself for the primary DNS server.
0
 
bwinkworthAuthor Commented:
The server is the DNS/DHCP server and the DNS settings on the IPv4 properties do point to itself for the preferred DNS server and the other DC is the Alternate DNS server. Pretty sure it's always been like that. IPv6 is disabled as well

BW
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
nettek0300Commented:
I would put in a different server for the primary DNS, then reboot and see if it corrects the problem.  Most times when this has happened to me, the issue was with DNS.  Good luck!
0
 
bwinkworthAuthor Commented:
Jmoody10: No there are no folder redirections happening.
What would I put in for the primary DNS because it is the primary DNS? You mean like an external DNS IP?
0
 
Joseph MoodyBlogger and wearer of all hats.Commented:
0
 
nettek0300Commented:
If you have two DNS servers on your network, i.e. 192.168.1.2 and 192.168.2.2, then set the primary DNS server on server 192.168.1.2 to point to 192.168.2.2 and set DNS server on server 192.168.2.2 to use 192.168.1.2 for the primary DNS  (Your IP addresses, will of course be the IP's of your personal servers and not the ones above.  This is just an example).
0
 
bwinkworthAuthor Commented:
Thanks for the answers guys. Haven't tested it yet but gotta go.

BW
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

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