Takes to long to login...

[tenzan]

Hello

After computer a part of a domain, it takes too long to login after I
enter login name and password.
I think this is one of the oftenly occured problem.
Does anybody know how it can be solved?

Thanks,
askar

PS I feel this problem would be solved if I reinstall windows, but this
is not the best way, isnt it?

 

[Guest]

By far the most common reason is a DNS problem.

On the workstation, the domain controller needs to be FIRST in the list of
polled DNS servers.

On the server, the DNS service needs to be setup with the AD extensions.

 

[Steven L Umbach]

I agree with Ian that it most likely is DNS related. Remember NEVER list an
ISP dns server in the tcp/ip properties of any domain computer. You can use
ipconfig /all to check tcp/ip settings. Check the application log of the
computer in question and you probably will find some error/warning for
userenv or such that would verify that there is a problem
contacting/locating a domain controller or possibly a different problem. The
support tool netdiag is also very helpful in checking the domain and network
health of any domain computer. See the link below if you have any questions
on how DNS must be setup in an Active Directory domain. -- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

 

[Guest]

After computer a part of a domain, it takes too long to login after I
enter login name and password.

One other thing that can cause this is if there are a lot of NTFS file ACL
permissions for a lot of files and folders being set via Active Directory
Group Policy for that domain.

I'm curious as to whether it's quicker to sign in if you unplug the network
cable right before you enter your password? That should use the locally
cached password to authenticate, instead of the domain controller.

PS I feel this problem would be solved if I reinstall windows, but this
is not the best way, isnt it?

Well, if your computer is the only one having the problem, that might not be
a bad idea. At least you'd know whether the problem was something on your
computer or was something wrong with the domain.

 

[tenzan]

Thanks to all a lot!!!
The computer with loging time problem was using even not ISP's dns
servers.
I don't remember who put that ips.
As the 1st DNS server I put, Domain Controller's IP address, as it also
acts as DNS server. As a second dns server I put ISP's primary DNS.
After these changes loging in quite fast.
Thanks a lot!!!
Tell me, if I still did smth wrong.

Thanks,
askar

 

[Steven L Umbach]

You do NOT want to have an ISP DNS server listed. Use only domain
controllers that also have the DNS zone for your domain which may be all of
them. If you leave the ISP DNS server listed you will have problems as at
times the secondary DNS servers will be used even if the primary DNS server
is running but does not respond in a timely fashion. The domain controller
can and should be configured to resolve internet domain names for domain
computers if internet access is needed. Domain controllers can either use
"root hints" or forward to your ISP DNS server in DNS Management Console
properties.

Steve

 

[tenzan]

You do NOT want to have an ISP DNS server listed. Use only domain
controllers that also have the DNS zone for your domain which may be
all of
them. If you leave the ISP DNS server listed you will have problems as
at
times the secondary DNS servers will be used even if the primary DNS
server
is running but does not respond in a timely fashion. The domain
controller
can and should be configured to resolve internet domain names for
domain
computers if internet access is needed. Domain controllers can either
use
"root hints" or forward to your ISP DNS server in DNS Management
Console
properties.

Steve

Thanks, Steve!
Let me confirm...
You mean I should not to put any IPS's DNS name server in TCP/IP
properties of lan card, should I?
As you said, "The domain controller
can and should be configured to resolve internet domain names for
domain
computers", where is it done if not in TCP/IP properties of lan card?

thanks,
askar

 

[Steven Umbach]

Yes that is correct. The domain controller needs to be configured via the DNS
Management Console to either use root hints or to forward to your ISP DNS
server. The KB articles in the links below explains in more detail.

Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
http://technet2.microsoft.com/Windo...235e-4fd4-b4da-7e57e70ad3821033.mspx?mfr=true
http://support.microsoft.com/default.aspx?scid=kb;en-us;323380