home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!matt.ksu.ksu.edu!news
- From: mgriffin@matt.ksu.ksu.edu (Mark Griffin)
- Newsgroups: comp.sys.novell
- Subject: What's Causing System to be slow?
- Date: 12 Jan 1993 11:07:10 -0600
- Organization: Kansas State University
- Lines: 24
- Message-ID: <1iutruINNe7j@matt.ksu.ksu.edu>
- NNTP-Posting-Host: matt.ksu.ksu.edu
- Keywords: SCSI Netware 2.15
-
- We are running Novell Netware 2.15 on IBM PS2's. The server is a PS2 as are
- the clients. Not sure what the model numbers are. Anyway, this system has
- run fine for quite some time now until we recently added a 320M SCSI drive
- to the server. We did a re-gen of the network after adding the SCSI and
- have got the network running again. The clients can link the server
- successfully, and if we wish to we can even access the new drive. That is all
- of the good news, the bad news is that after a client has linked the server
- response time is tremendously slow. It does not matter whether you are
- accessing the original ESDI Drive or the new SCSI drive, response is slow.
- One peculiarity we have noticed is that if we link two clients to the server
- we can speed up response somewhat. What happens is, one client will seem to
- be hung on a command (sometimes for a minute or more), then just by entering
- a command that accesses the server from the other client, the first client
- that was hung will instantly free up and continue for awhile. Of course,
- shortly again, one client or the other will be hung again until a command is
- entered on the other client. Can anyone offer any clues as to what may be our
- problem. We have a great deal of experience with Lan Manager, but not much
- with Novell, so any help or suggestions would be greatly appreciated. Thanks.
-
- --
- . . . . . . . . . . . . . . . . . . . . .
- Mark Griffin, Sys Admin, Fort Hays State University |It is always better to
- Internet:mgriffin@matt.ksu.ksu.edu Bitnet:mgriffin@ksuvm |do, than be done to.
- . . . . . . . . . . . . . . . . . . . . .
-