RE: Server disconnecting users

This is long post indeed....

Anyway, although you've provided a lot of information I am missing the
psychical network layout, are there maybe any routers which are running out
of memory and causing the network to fail?

"Wolfman099" wrote:

I have an HP Proliant DL380 G4 server running Windows Server 2003
Standard. The machine has a zeon 3.2 ghz processor with 1ghz ram.
This server is a domain controller and its role is a DNS Server, File
Server, and Print Server. I also have another DC that acts as a DNS
(AD Intergrated) and DHCP Server. This server has identical specs. I
will call the first server(file/print server) Server 1 and the other
Server 2. I have both servers setup with HP's Network "Team" which
utilize both gigabit network connections. Server 1 has a Raid 5 setup
with 4 300gb 10000 rpm drives.

A little about our environment... We have about 250 users. Server 1
holds a Personal folder for all users. We map drives to this personal
folder and also map their My Docs folder to the same share. We also
have a public share and a share for each department. Everyone pretty
much has 3 drives mapped to Server1.

Lately, we have been having a lot of disconnect problems with the
server. The server kind of locks everyone up. For example, today we
had a problem and if I double clicked on My Computer, My system would
freeze for 2-3 minutes. If I accessed anything on the network share,
my system would freeze. It was happening to pretty much everyone. I
was able to remote into the server. I checked the performance of the
server, the system had 400mb of memory left, was only using between
1-20% processor and the network utilization was at 3-6% and had a peak
of 8%. I checked the system log as well, nothing out of the ordinary.
No Errors at all.

This is becoming more and more common. I am really unsure of what the
problem is. I am hoping that with the help of this forum, I can try
and narrow down the problem by monitoring the traffic and logs. It is
blowing my mind, because the specs on Server 1 are pretty good and the
logs look fine. I really don't know what to look for.

More info on what seems to cause this problem...... There are a few
things that I can do that will more than likely cause this problem. We
have a Ghost Server. I have been doing some Unicast images to
different machines. These machines are on their own subnet, but the
ghost image files are on Server1. When I image a PC on this Ghost LAN,
people start losing connection to their mapped drives and others get
locked up.

The other day I was simply copying a 3gb image file from the Ghost
server to Server1. It was a single large file, but it started locking
people up.

We have office 2003 installed with XP workstations. Each user has an
archive file on Server1. Some of these files can be quite large. A
few times, the files become corrupt. Outlook will try to repair the
file on the network and the entire time it is working on repairing, it
locks everyone else up. Why would one file lock everyone else up. We
have had 3 occurrences of this and we are 100% sure it was the .PST
file that was causing the problem. As soon as we copied the PST file
local and reparied it, the problem was resolved. How can this single
(1gb) file cause such a problem on our ENTIRE network!? I had this
problem today as well with another user. Atleast this time I knew to
copy it local first so that the problem didn't continue.

At one point during the week I was doing a search for MP3's on the Raid
5 drive on Server1. Everytime I do this, it starts locking up users.
In the past, I would search for mp3's, wav, wma and movie files all at
once. This last time, I only had one search window open looking for
mp3's and I had to cancel it. It had taken over an hour and still
wasn't complete and was causing people to lose their network drives.

I was monitoring some traffic today and it seems like we have a ton of
very large print jobs going to server1. I think that all the traffic
(although the logs don't show it as a problem) may be causing an issue.
I'm debating on moving the print server over to server 2.

Wow, this is a long post! I hope someone actually reads it all :-).
Can anyone help me figure out what I should look for the next time that
we have one of our lockups or people start losing connection to their
network drives? Everything I check seems to be fine. Do you think that
moving the print server to a new machine would help?

I GREATLY appreciate any help that you can provide to me as a new
admin.


.

Relevant Pages

  • Re: Terminal Server Performance
    ... when we are having problems and it seems the network is fine during the ... I will have to analyze the data when the server starts going slow again. ... "Jeff Pitsch" wrote: ... the hard drives to see if commands are lining up during peak ...
    (microsoft.public.windows.terminal_services)
  • Re: Vista drive mapping to 2008 Server
    ... It sounds like something in the network infrastructure may not be working with some of these features. ... Try each setting both on the server alone, a client alone, then both. ... After doing this map a drive by any method then see if it loses the ... > No logon script used in this instance and it maps drives not used by> any ...
    (microsoft.public.windows.vista.networking_sharing)
  • RE: net use
    ... The network connection could not be found. ... mapped drives to properly register in T.S.. ... AD/Exchange Server) are fine. ... When you run the logon script manually, you receive "system error 85" error ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server Performance
    ... it appears that the bottleneck is with the ... I will have to analyze the data when the server starts going slow again. ... percentage in the network utilization?... ... the hard drives to see if commands are lining up during peak ...
    (microsoft.public.windows.terminal_services)
  • Re: Fully parallel Scheme-based language w/ evaluator
    ... Windows Server 2003 and networks in simple - and irreverent - terms. ... If networking really is a big deal, ... Concepts and Terminology in Part I, and The Design and Deployment of Network ...
    (comp.lang.misc)
Loading