Re: slow log in

• Previous message: Richard G. Harper: "Re: Domain security policy and GPO"
• In reply to: DC Gringo: "Re: slow log in"
• Next in thread: DC Gringo: "Re: slow log in"
• Reply: DC Gringo: "Re: slow log in"
• Messages sorted by: [ date ] [ thread ]

Date: Sun, 2 Jan 2005 14:46:01 -0600

"DC Gringo" <dcgringo@visiontechnology.net> wrote in message
news:#KWjdVP8EHA.2608@TK2MSFTNGP10.phx.gbl...
> Herb,
>
> I was auditing a whole series of events that I have now turned off...I had
> switched them on recently to track down another unrelated problem. I do
> believe I was having this problem before doing that, but I will check
> anyway. It looks like a few hundred entries were being logged on startup.
> Do you think that alone could hold up a logon for 10 minutes?

I would not have PREDICTED that would slow
you up for even a minute, but if switching them
off corrects the problem that seems to be the
evidence.

Writing to the event log is probably not perceptibly
slower than writing to a file -- 100-1000 records is
not all that much.

Perhaps it means a little more initialization happening
early but that only means a little (few seconds delay.)

-- 
Herb Martin
> _____
> DC G
>
>
> "Herb Martin" <news@LearnQuick.com> wrote in message
> news:%23roEzCN8EHA.1524@TK2MSFTNGP09.phx.gbl...
> > "DC Gringo" <dcgringo@visiontechnology.net> wrote in message
> > news:esQp37F8EHA.3700@tk2msftngp13.phx.gbl...
> > > Pegasus,
> > >
> > > Yes, I am familiar with that problem, but I have the correct DNS
> > setting...
> >
> > Despite your confidence it would be my own practice
> > to post those settings and to have rechecked them.
> >
> > BUT based on your posts it also seems likely that
> > you are fighting a GPO/Script problem.
> >
> > You even indicated in your first post that it was during
> > Script processing.
> >
> > And although you say "slow log in" it seems that you
> > are reporting a slow login of the COMPUTER (technically
> > a logon but not the one most people think about.)
> >
> > > Do you know of a way I can trace each step of the logon process and
look
> > at
> > > it?
> > `
> > What about selectively removing your GPOs or scripts?
> >
> > How about instrumenting your startup scripts to log
> > their own behavior to a known file (with >> to append
> > the results)?
> >
> > If you log start/stop/major-events using something like:
> >
> > @echo %0:What I am doing now %date%  %time% >>c:\startup.txt
> >
> > %0 should give the script name that is running.
> >
> > -- 
> > Herb Martin
> >
> >
> > >
> > > _____
> > > DC G
> > >
> > > "Pegasus (MVP)" <I.can@fly.com> wrote in message
> > > news:uqgrvEt7EHA.2552@TK2MSFTNGP09.phx.gbl...
> > > >
> > > > "DC Gringo" <dcgringo@visiontechnology.net> wrote in message
> > > > news:eLyz6bq7EHA.2316@TK2MSFTNGP15.phx.gbl...
> > > > > I've got a lot boot process that hangs for it seems 5 minutes
while
> > > > running
> > > > > start-up scripts.  The only way to get it to log right in quickly
is
> > to
> > > > > disable the workstation service, which obviously causes other
> > problems.
> > > > >
> > > > > I'm running WinXP SP1 on a Win2k domain.
> > > > >
> > > > > I used bootvis.exe to log my boot process but it doesn't pinpoint
> what
> > > the
> > > > > exact hold up is.  Only that 1.5 min is in shell exec stage and 5
> > > minutes
> > > > > for Logon/services stage.
> > > > >
> > > > > How can I see what part of either the startup script or shell
exec,
> > > > > logon/services are holding me up?
> > > > >
> > > > > -- 
> > > > > _____
> > > > > DC G
> > > > >
> > > > >
> > > >
> > > > Slow login processes are usually the result of incorrect DNS
> > > > settings, causing the machine to look in the wrong place for
> > > > the domain name server before timing out.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

• Previous message: Richard G. Harper: "Re: Domain security policy and GPO"
• In reply to: DC Gringo: "Re: slow log in"
• Next in thread: DC Gringo: "Re: slow log in"
• Reply: DC Gringo: "Re: slow log in"
• Messages sorted by: [ date ] [ thread ]