Re: server is using 100% cpu

"that looped or something" ??

This is not normal. I would still want to know what is the underlying
cause. The fact that you "killed" the process at the end of the workstation
logon sounds like a band aid. But the wound may still be festering and
might kill your server in the end. Even then, if it is a non threatening
process, it is still not normal. And I like normal, as opposed to abnormal.
In pets, friends, relationships, networks, and anywhere else I can find it.
There is already too much craziness in the world.

On the workstation, msconfig will allow you to stop most startup services.
I would stop them all, then start them one at a time. In the login script,
I would rem out any calls to programs, and if have services/programs that
are started in any other way I would look closely at that.

Regards:

Anna Clark
-----
Please do post the conclusion or solution
to your issue so that others may benefit.


"Marnix" <Marnix@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:461DBB2B-DC06-4295-92A9-04896D7EA8D7@xxxxxxxxxxxxxxxx
Dear Cris,

You might be a MPV but you are also WRONG. I gave a good couple of hints
that RAM or PIII had nothing to do with it. But you choose to ignore them.
It
WAS a cmd process at clients login that looped or something. Use taskkill
at
the end of the logon script and all the network traffic stopped. Result
the
server went back to using 10% cpu. All users are happy again and so am I.

With kind regards,

Marnix


"Cris Hanna" wrote:

Marnix
We've given you a direct indication as to the problem
Your SBS server is vastly underpowered!!!

As far as your one user with all that traffic...are you running Windows
Defender and a good antivirus on that workstation because most likely it
has
a virus or spyware

--
CRIS HANNA [SBS-MVP]
---------------------------------
Please only respond in the newsgroup. Do Not Contact Directly.
MVPs do not work for Microsoft.
---------------------------------------
Sent via Windows Mail on Vista Ultimate connected to SBS R2
"Marnix" <Marnix@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A768ECFF-6029-45BE-AB20-778352CA920C@xxxxxxxxxxxxxxxx
Sorry misunderstanding I mend in my first posting I forgot to say
that:
Task
manager is telling me that system is eating cpu.
My system uses about 490 to 550 intern so it has to swap all day. But
it
has
done so from day one. I will increase it as soon as I can just to make
sure
that that is not the problem.

Winroute: because it is a good firewall that my client can manage. It
has
a
good gui and is easy to use. It does allow bandwidth limitations and
per
user
rights. As far as I know it uses very little recourses especially when
no
one
is using the internet.

Have You seen my posting about the network traffic?


"Steve" wrote:

You didn't answer my question about why you're using Kerio and what
kind
of
performance impact it may have. Certainly 512 MB RAM is too little
and
needs
to be increased. Most of us recommend 2 GB for SBS 2003 SE and more
if
you
have PE and are running SQL. Also I didn't see a response to Anna's
question
about task manager and what it shows for the process that is
consuming
so
much CPU? You did state in another post "I forgot to tell this in the
mail
it is system that is eating CPU" but how are you determining that and
exactly what about mail is eating the CPU?

"Marnix" <Marnix@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:63BC2168-EDD5-44B6-B3C3-647D12621993@xxxxxxxxxxxxxxxx
Thanks for all your help guys. I've read 3 comments about the ram
in my
system. This server has been up for a year. the CPU problem is only
been
around for two to three months. So I have the feeling that it has
little
to
do with that but I could be wrong. As I told earlier the problem is
only
three months old. So I was more thinking along the lines of a
Microsoft
update of the clients or the server. What do you guys thing about
reinstalling SP1 and seeing what happens?


"Marnix" wrote:

I have a Proliant ML 350 PIII 1.13 GHz and 512 MB of RAM. I run a
standard
SBS 2003 on it. The only other software that is running on that
system
is
Kerio Winroute Firewall. The network has 10 clients.

The system was working perfectly until about three months ago. I,
for
as
far
as I can remember, havened changed anything on that system. It is
running
at
100% CPU. I think it has something to do with continuous
communication
with
the clients. This communication uses 10% of one of the network
cards.
It
seems to have all two do with Microsoft-DS. This all happens so
far
under
water that I have no clue how two fix this.







.

Relevant Pages

  • RE: Dropped Client Connections
    ... I understand that the SBS clients will lose ... Do all clients lose network connection at same time? ... Do you have single or double NICs on SBS? ... Modify the registry to disable Receive Side Scaling ...
    (microsoft.public.windows.server.sbs)
  • RE: Can not see vpn clients in SBS domain network view
    ... send console message to the remote clients. ... When the remote clients connect SBS network via VPN, ... So you can not find the remote computers. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Server & a WiFi Hotspot (some DHCP for good measure too)
    ... ISA2k4 is currently not supported on SBS ... To review - you have LAN clients that you want to have ... card for your server. ... > network with 5 client computers. ...
    (microsoft.public.windows.server.sbs)
  • Re: server is using 100% cpu
    ... to call Microsoft SBS Support so as not to be disappointed with the best ... You always have the option to use other resources including call Microsoft ... WAS a cmd process at clients login that looped or something. ... server went back to using 10% cpu. ...
    (microsoft.public.windows.server.sbs)
  • Re: server is using 100% cpu
    ... and without physically looking at your server we do the best we can to provide you information which may or may not resolve the issue. ... You always have the option to use other resources including call Microsoft SBS Support and getting a support engineer dedicated to assisting you in resolving your issue. ... WAS a cmd process at clients login that looped or something. ... > manager is telling me that system is eating cpu. ...
    (microsoft.public.windows.server.sbs)