Log on to W2K3 domain

  • Thread starter Thread starter Maida Dunn
  • Start date Start date
M

Maida Dunn

After upgrading I have noticed several servers and workstations taking a
long time

Applying Security Policy...............

Before the log on dialog box comes up. What's happing?

Thank you,
 
If workstations and servers are taking a long time to logon, you should
check their DNS settings. Make sure they are pointing at the correct DNS
server (and verify this server is functioning properly). Other things to
check would be subnet mask -i.e. less bits than required, e.g. 255.255.240.0
instead of 255.255.255.0. You also need to make sure there's at least one
GC available at the site.

If logon time is fine, but GPO processing is slow, there's a good chance the
GPO is being picked up from a remote server. Again, DNS is the first place
to look re. this.

Are you installing any applications via GPO?


Paul.
____________________________________
 
Forgive the ignorance, but what is a 'GC'?
-----Original Message-----
If workstations and servers are taking a long time to logon, you should
check their DNS settings. Make sure they are pointing at the correct DNS
server (and verify this server is functioning properly). Other things to
check would be subnet mask -i.e. less bits than required, e.g. 255.255.240.0
instead of 255.255.255.0. You also need to make sure there's at least one
GC available at the site.

If logon time is fine, but GPO processing is slow, there's a good chance the
GPO is being picked up from a remote server. Again, DNS is the first place
to look re. this.

Are you installing any applications via GPO?


Paul.
____________________________________



.
Click to expand...
 
Thanks Paul -
I'm not doing anything with GPO's yet. Logon's our okay it's before you get
the logon dialog box. I'll check on the DNS settings for those clients
complaining. My SMS Server took a long time this morning. It's obtaining the
IP and DNS settings from DHCP and the subnet mask is 255.255.254.0. I did
IPCONFIG /ALL and all the settings look okay.

Thanks for your help!
 
GC = Global Catalogue.

An essential aspect of AD, especially in Native Mode.



Paul.
___________________________________
 
Maida,

The applying security settings part of booting *IS* applying a GPO. There
are two default GPOs - Default Domain, and Default Domain Controllers.

Check your DNS server to make sure that all of the required SRV records are
present, e.g. _msdcs, _sites, etc.


Paul.
___________________________________
 
All the SRV records look good for both sites. However we did create a new
DNS domain name called gss.local.com and we still have the original
local.com.

We have dynamic updates set and all the machines or created under the new
DNS domain gss.local.com.

How do I go about decommission the old DNS domain name local.com? I have a
Exchange 5.5 mx record also. Could this be some of my issues?

Thanks :)
 
Hi Maida, sorry for the delay -brief holiday!!

Let me get this straight - you now have two DNS domains and want to get rid
of one of them because you've upgraded to AD?

If so, providing everyone is now a member of the new Active Directory and
therefore has the domain suffix of the AD DNS you can delete the old DNS
zone from DNS. Just make sure that no one is set to use this as their
primary DNS. You may also want to look at the DNS search suffix options on
the clients. Logon could be taking longer because clients are looking at
the wrong DNS server first.


Paul.
___________________________
 
Back
Top