[comp.dcom.lans] LANTASTIC network snoozes

ralphs@seattleu.edu (Ralph Sims) (03/16/91)

Periodically, our two-node server-to-server LANTASTIC network seems
to want to go to sleep.  An error (resembling an MS-DOS error message)
of 'network device no longer exist, ABORT, RETRY FAIL' is shown when
running a directory on a remote machine.  So far the problem exists
in both directions.

The configuration is:

COMPAQ DESKPRO 386/16, older BIOS, 4 megs of RAM, COMPAQ DOS 3.31 with
4DOS 3.02a command processor (removing it doesn't help), LANTASTIC AE-2
card w/20' of 'cheapernet' cable, 120meg MicroScience IDE drive.

Noname 386/25, AMI BIOS, 4 megs or RAM, COMPAQ DOS 3.31, etc., with a
SEAGATE ST4096 80meg ST-506 drive.

The LANTASTIC configration is basically out-of-the-box, with a debug
patch applied on the COMPAQ to handle the pre-historic BIOS (no5C).

A 'retry' wakes things up, and running LANCHECK indicates no collisions,
but a single 'Retransmission' and 'Resource Exhaust' error.

In talking with ARTISOFT, it was recommended to get rid of COMPAQ DOS
('We don't know what they're doing with their erorcodes') and setting
the IOBASE=320 via W4 jumpers.  Dumping the DOS isn't really feasible,
and we've re-configured the jumpers, but the problem still exists.

Before I spend another couple of hours on the line with ARTISOFT, does
anyone have any thoughts on this?  The system exists in an emergency
dispatch center with a considerable amount of RF generated by a MERLIN
II phone system, MOTOROLA CentraCOM console, various monitor receivers,
fluorescent lights, etc., but no radio transmitters in the area (except
for 5-watt VHF portables and 40-watt mobiles operating 75' away).  The
building is wood-frame construction.  The problem doesn't seem to be tied
to radio traffic, time-of-day, or anytthing recognizable.

By the bye, the error message from the DOS prompt cannot be located in
any of the files, executable or system, on the drive.  I'd be inclined
to believe it's a BIOS errormessage.  If so, would it be from the COMPAQ
or the AMI BIOS (hints on a debug routine to scan the BIOS areas would
be helpful)?

--
                    halcyon!ralphs@seattleu.edu
  The 23:00 News and Mail Service - +1 206 292 9048 - Seattle, WA USA
                 +++ A Waffle Iron, Model 1.64 +++