Re: Prove that there is no need for additional domain controller

From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 10/04/04


Date: Mon, 04 Oct 2004 09:13:01 -0400

This could be misconfiguration or overloading.

The question is why the delta? You need to keep track of where people are
logging in for that site. Set up a logon script for them and have it record
somwhere what their logon server is every time they logon (hint: Env var
logonserver) and what their site is (dump nltest /dsgetsite or something to the
log).

Then look through it and find out if people are authenticating outside of their
site. If they are, then something is wrong with the site/subnet configuration
(see log for what site they say they are) or you have DNS issues or you have a
DC with issues or you have overloaded the local DC.

If the logons are all happening on the local DC then you either have a long
running script, connectivity issues to other shared resources, large roaming
profiles, an issue with the local DC, or you have overloaded the local DC.

   joe

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net
Marlon Brown wrote:
> On a remote site users log in with accounts which has group policies applied
> to it and sometimes it takes about 50 seconds to complete the entire login
> operation. Logging on from the main site with same account it takes about
> the same 50 seconds. However, sometimes users complain that the same
> accounts when logging on from that site takes about 4 minutes. That's a T1
> connection between the remote site and main office and T1 utilization
> according to the network folks is supposed to be low.
> 
> Any tool to analyze how long it is taking to get settings from domain
> controllers and help me demonstrate if I would benefit from installing a
> domain controller there on the remote site ?
> 
> 
> 


Relevant Pages

  • Denying domain logon to certain users on W2K workstation?
    ... We have several computers on our network which attract casual users due to ... accounts that we'd like to deny any logon ability at those workstations. ... Is there a way to prevent domain users from logging into these workstations? ...
    (microsoft.public.win2000.security)
  • Logging in takes 20 minutes on SBS
    ... I have a windows 2003 SBS network with 40 users. ... logging in now takes between 15-20 ... accounts and it seems it does not happen on any machine that a user ... logged on to my machine tries to logon, ...
    (microsoft.public.windows.server.sbs)
  • concurrent logins
    ... How can I prevent users from logging in with their accounts more than once ... I they will have to logoff a pc before they can logon to ...
    (microsoft.public.win2000.security)
  • RE: Events 40960 & 40961
    ... the user etchee attempts to logon from workstation WS1, ... other users that can do so fine from this workstation. ... What am I looking for in the winlogon and userenv logging? ... Start Registry Editor. ...
    (microsoft.public.windowsxp.general)
  • Re: Login Errors Seem to indicate we are being hacked?
    ... I have turned on diagnostic logging on SMTP. ... we could turn something off on our own SMTP server to stop the devils from ... Logon Failure: ... Caller User Name: SERVER01$ ...
    (microsoft.public.windows.server.sbs)