From: jkain@bronze.ucs.indiana.edu (Jeff Kain)
Subject: Unsolvable problem
Summary: We can't solve a baffling network problem
Keywords: help problem Mac Hardware network printing File Sharing
Organization: Indiana University
Date: Sat, 25 Jul 92 19:55:22 GMT

Hello...

I'd like to share a problem we are unable to explain. It has baffled
us, and we are out of ideas on how to fix it. Any ideas you have would
be greatly appreciated!

DIARY:

June 20, 1992
-------------
Pediatrician's office with Macintosh network. Two Mac IIcx computers
and one Mac SE running System 6.0.8, all with 2MB RAM, all sharing an
AppleTalk ImageWriter printer. One IIcx is the 'file server' and a
workstation for a database program, connected via TOPS. No problems,
everything is working fine.

June 21, 1992
-------------
We, the experts, walk into the office to do several things:
  1. Upgrade each IIcx to 5MB RAM and the SE to 4 MB
  2. Remove TOPS on all Macs and install System 7.0.1 on the CXs
(6.0.8 still on the SE)
  3. Upgrade the medical database program to the latest version

We opened each machine, vacuumed the insides, installed the memory on
each machine, then removed TOPS and installed System 7 and the new
program. Did a quick check to make sure the memory was working, loaded
the new program and did quick tests, and left.

June 22, 1992
-------------
The office calls with many problems.
  1. The AppleTalk Imagewriter, which used to print very fast (always
in draft mode) is now taking two to four minutes to print a single
page from the CXs only. The SE prints fine.
  2. The database program on the non-server IIcx, which opens by
loading a set of data dictionaries into RAM across the network, is now doing so
approximately five times slower than before, and five times slower
than the SE which is also doing the same network loading.
  3. The connection to the printer is periodically lost from the
non-server CX.

Here's what we tried to solve these problems, over the last month:

1. Replace all phoneNet connectors.  Didn't help.
2. Tried booting the CX from a 6.0.8 floppy and running database.
Didn't help. Net still slow.
3. Exchanged the CX and the SE CPUs only, using the identical network
cabling, power cords, keyboard, mouse, etc.. The SE ran normally. Put
the CX in its place, the CX went back to the same problems.
4. Brought the CX to our office and tested on our network. No
problems, performed flawlessly. Brought to Apple Authorized Service,
where they did several hours of diagnostics. No problems found, that
will be $70 please...
5. Directly connected the SE to the file server (sat them side-by-side
and used a new piece of phone wire to connect them, bypassing the
existing wiring in the ceiling). SE ran fast.  Put the CX in its
place, still slow.
6. Copied the database program from the SE to the CX and replaced
existing copy. Didn't help.

The office is furious and frustrated. We are out of ideas! Our next
step is to rewire the whole office and reformat each hard disk, but we
don't think that these are the problems.

Some long-shots we considered:
- All the CPUs are sharing the same Kensington UPS. The overload light
does not light on the UPS, and doesn't otherwise indicate there is too
much load or that it is not supplying enough power to all machines.

- Maybe we have two separate problems... a defective printer and
something else causing the CX to load data slowly.

- Something (an X-ray machine, lab equipment, ...) is causing just the
one CX to have problems.

Any ideas?  Any comments will be gratefully accepted!  Please e-mail
to jkain@bronze.ucs.indiana.edu or WabashMed@aol.com

Thanks!
              Jeff Kain



-- 
jkain@bronze.ucs.indiana.edu
F7 d+ m++ b- r-- s++ e- h c

Newsgroups: comp.sys.mac.hardware