logon very slow

  • Thread starter Thread starter patrice
  • Start date Start date
P

patrice

Some users are confronted to long delay during process
logon. Users have to restart their computer several times
before to get a normal logon process.
the computers are in a domain and problems seem to appear
when several users log on at the same time.
I have log files (netlogon.log,winlogon.log) but I can't
see problems in this files.
Have You seen some problems like this one ?
 
SteveC said:
Check that the DNS server used by your clients is only your server.
Do not list any of the ISP DNS server.

The server should also only use 1 DNS server, itself.

If you're running pre windows 2000 computers, using a WINS server
will help speed things up.
Click to expand...

I'm a little confused here, because some posts say "Use the DNS of your
ISP", and others say, "Use only the DNS of your server".

What is the criteria for doing one over the other?

I'm on a University campus, so we have two DNS machines, that are not
Windows servers, but most likely some Unix flavor. We also have
departments running their own Windows Networks and Domains, and some of
them have their own Win2k servers, running their own DNS on them.
Anecdotally, I've found that the machines that log on to these domains
and point to the Win2k DNS's run crappy, while the ones that point to
the Unix DNS's run faster. Is that because the Win2k DNS's are set up
incorrectly? Clients are generally XP. I don't see any advantage to
running ones own DNS on the server, even if it IS apparently recommended
SOP for Win2k servers....
 
When talking about problems with DNS,
I'm a little confused here, because some posts say "Use the DNS of your
ISP", and others say, "Use only the DNS of your server".

What is the criteria for doing one over the other?

I'm on a University campus, so we have two DNS machines, that are not
Windows servers, but most likely some Unix flavor. We also have
departments running their own Windows Networks and Domains, and some of
them have their own Win2k servers, running their own DNS on them.
Anecdotally, I've found that the machines that log on to these domains
and point to the Win2k DNS's run crappy, while the ones that point to
the Unix DNS's run faster. Is that because the Win2k DNS's are set up
incorrectly? Clients are generally XP. I don't see any advantage to
running ones own DNS on the server, even if it IS apparently recommended
SOP for Win2k servers....
 
It really depends.

In a Windows 2000 AD Domain, you really need to point to some DNS Server
that supports dynamic updates. This is so the servers and clients can auto
register their DNS records. In most cases you point to an internal DNS, that
then forwards out to your ISP. This will allow the clients to login
internally and then also be able to access the Internet.

I hope that clears it up a bit. :)
--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.
 
Windows 2000 and XP machines that are members of a Windows 2000 Active
Directory domain must use a dns server that is configured with the domain
zone including the _srv records and really needs to support dynamic updates.
Generally this means a Windows 2000 domain controller, though bind can be
configured to support an Active irectory Zone. In a Windows 2000 domain, dns
is used as a resource locator to find the domain controller, global catalog
server, kerberos server, etc in addition to name resolution. If performance
is poor, that generally means there is a configuration issue with the domain
controllers or domain clients. Configuring the domain clients in their
tcp/ip properties with dns servers other than those for Active Directory
often cause performance issues, especially ISP dns servers. Dcdiag and
netdiag can be very helpful in troubleshooting these issues. See link for
more info. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
 
aha.
So what if you've got Windows 2000 servers that have not implemented
Active Directory? does using the Win2k DNS or the ISP's DNS make a
difference if Active Directory isn't involved?
 
If they are accessing resources on W2K domain computers, then it may make
sense since they still will use dns to locate those computers. If that is
not the case then ISP dns servers will be fine. Keep in mind that if
multiple dns servers are configured in the tcp/ip properties of computer,
that the dns server down the list from the top preferred one will only be
accessed if the first dns server is not responding to any queries. If the
first dns server used does not resolve a host query, the process stops. I am
not familiar with large networks of W2K computers not using Active
Directory. You may also want to post in the win2000.dns newsgroup. ---
Steve
 
Back
Top