Re: After week of uptime Logins Slow, Personal Share not mapping

Tech-Archive recommends: Speed Up your PC by fixing your registry



What I would do is to go into task manager shortly after a reboot, and note
how much RAM is being used by each process. You could simplify this by
limiting it to processes that are using over some threshold, say 1000 K.
Also check for anything that's using CPU resources other than briefly.

After say 6 days, go in to task manager again and see which processes have
significantly increased their RAM usage. Remember that it's normal for
store.exe to be using an ever-increasing amount of RAM, so that one will
definitely be much higher. For the others, though, they should be pretty
consistent with what they were shortly after the reboot. Again check CPU to
see if there's anything hogging CPU cycles.

I'd do both of these checks under the same circumstances as much as
possible - for example not during a backup.

If you haven't found anything by then, I'd wait and look at it when the
server becomes unresponsive.

A couple things I doubt are related but JIC - delete temp files from the
server, and make sure the drives have at least 25 or 30% free space.

"Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:639C38A1-DB7A-4494-8357-FFE9D27D6A97@xxxxxxxxxxxxxxxx
Have a SBS 2003 Std. Server w/SP1 running on Dell PowerEdge800 with
singles
NIC. This issue has been happening since this server was installed 6
mounts
ago. Using SonicWall TZ170 firewalls with Site to Site VPN. SBS running
Veritas Backup Exec version 10 and Trend Micro Client Server Messaging
Suite
2.0 for SBS. Clients are running XP Pro SP2 with latest patches, Server
is
patched as well.

The server and client work fine until server is up for about a week.
Clients
at remote site are login into the domain over the SonicWall VPN.
Performance
over the VPN is very good until server is up for a week. Then the remote
clients all of a sudden take 10 minutes to logon to the domain and the
personal shares set in the users accounts do not map. User's cannot
connect
to the Exchange server, access denied. Clients that are already logged in
are
ok unless they logout and log back in. Rebooting the server resolves the
problem and all is well until another week goes by. During this problem
the
Logon script appears to run and drives mapped with net use command map and
users can access them.

If server is rebooted every week the problem does not appear. Rebooting
the
server every week is an annoyance, my client is not liking this. This
seems
to a resource issue or memory leak. I have investigated both Veritas and
Trend Micro and applied patches for any issues that appeared to be
related.
There are no errors being logged and I cannot find any related issues in
Microsoft's Tech sites.

Some direction would be greatly appreciated.



.



Relevant Pages

  • Re: Creeping Oulook connectivity problems
    ... have you done any message tracing to see where they might be getting hung ... Clients are all XP Pro SP2, ... I hard coded the mail server IP into the hosts file. ... > reboot the machine only if we absolutely have to. ...
    (microsoft.public.exchange.admin)
  • Re: What are your servers specs?
    ... I have a friend who has clients running SBS on machines as old as a PIII ... min 2GB ECC RAM, PERC RAID Controllers, Hot Swap ... drives, DLT/SDLT Tape drives, Redundant Power Supplies, all SCSI devices. ... server ever was a Compaq SAN which you will NEVER use in this server space. ...
    (microsoft.public.windows.server.sbs)
  • [HPADM] SUMMARY -- nfs hang due to stad or lockd?
    ... It looks like the server will need a reboot at some point in time. ... the affected clients are compute servers. ... lab that cannot do a "ll" of a couple of mount points. ...
    (HP-UX-Admin)
  • Re: Questions about DHCP and DNS migration
    ... I can't think of a reason you'd have to reboot the clients. ... broadcast for the next and should contact the new dhcp server. ... For the DHCP, I did some reserach and used the command "hetsh dhcp server ...
    (microsoft.public.windows.server.active_directory)
  • Re: Hardwarempfehlung =?ISO-8859-15?Q?f=FCr?= Terminal-Server?
    ... Ich habe mal für 6 Clients einen Server gebaut. ... NX basiert mit 2GB Ram. ... trotzdem verlangt der KDE nicht wenig Ressourcen. ... Nun wollte ich den Server ein wenig ausbauen. ...
    (de.comp.os.unix.linux.hardware)