Re: Why is winlogon taking too much memory?

Thanks for your help. I ran a virus scan and it turned up nothing.

I was able to lower the winlogon service process memory! I did it by simply
logging into the console locally. Weird! I have a duplicate windows 2003
SP1 web server (network load balanced with the other) that was suffering
with the same problem and logging in directly from the console cleared out
the winlogon process on that as well. I even kept a terminal service
session active on the 2nd server to see what effect that would cause.

So the question now is what happened and why did logging into the local
console fix it?

Perhaps there is some sort of terminal session memory leak problem with
Windows 2003.

Any ideas?

"Todd J Heron" <todd_heron_no_spam@xxxxxxxxxxx> wrote in message
news:OP0ne3WrFHA.3060@xxxxxxxxxxxxxxxxxxxxxxx
> Could be a virus, or a hacking program, maybe.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> --------------------------------------------------------------------------
--
> This posting is provided "as is" with no warranties and confers no rights
>
> "Steve M" <steve@xxxxxxxxxxxxxx> wrote in message
> news:%23buX$sWrFHA.1788@xxxxxxxxxxxxxxxxxxxxxxx
> I only have the remote control (2 connection) terminal services running on
> the web servers from remote administration. Typically only I would
terminal
> service into the boxes. I failed to report that my services.exe process
is
> also eating up over 400 MB as well. I used sysinternal's process explorer
> to see what's going on but it did not reveal much.
>
> Any ideas?
>
>
> "Todd J Heron" <todd_heron_no_spam@xxxxxxxxxxx> wrote in message
> news:ubCT7BOrFHA.3788@xxxxxxxxxxxxxxxxxxxxxxx
> > You should have only one winlogon.exe process running unless you are
using
> > Terminal Services. In which case you'll get an additional winlogon.exe
> > process for each terminal session. So, who's connected in remotely?
> >
> > --
> > Todd J Heron, MCSE
> > Windows Server 2003/2000/NT; CCA
>
> --------------------------------------------------------------------------
> --
> > This posting is provided "as is" with no warranties and confers no
rights
> >
> > "Steve M" <steve@xxxxxxxxxxxxxx> wrote in message
> > news:%23vxAYpMrFHA.3604@xxxxxxxxxxxxxxxxxxxxxxx
> > I have this problem too with 2 of my Dell PowerEdge Windows 2003 SP1
> > machines. I'm running ASP.NET web services on them and winlogon.exe is
> > eating up over 400 MB. I disabled my virus protection, patrol
monitoring
> > agents, etc. in hope to free up this service's memory but it didn't
help.
> I
> > have noticed a lot of open connections to my SQL server though. Could
> this
> > cause the problem?
> >
> > Any ideas?
> >
> >
> > "Homam" <Homam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:043799C6-0E2B-4096-AB16-837272DC61FB@xxxxxxxxxxxxxxxx
> > > I have a few Windows 2003 machines running ASP.NET Web Services, and I
> > > noticed that on all the machines there are two winlogon.exe processes.
> One
> > is
> > > consuming around 2 megs, and the other one is consuming a whopping 255
> > megs.
> > >
> > > I'm not using standard anonymous HTTP connection, no windows
> > authentication
> > > of any kind is required by the Web Services.
> > >
> > > The second winlogon process on all the machines is consuming about the
> > same
> > > amount of memory (255MB).
> > >
> > > Has anyone encountered something like this?
> > >
> > > How do I find out what the second winlogon process is doing?
> > >
> > > Thanks
> > >
> >
> >
>
>


.

Relevant Pages