I've had similar problems with dropping connections.
I've been up for 3 days straight so I'm not sure if my solution will work
for your situation, but here's the info anyway.

                        If you're on Mpe/iX 5.5 you can run nettool.net.sys.

                        RUN NETTOOL.NET.SYS;INFO='NAMEADDR;ROUTING;GATEUP
router ip;QUIT'    or
                        RUN NETTOOL.NET.SYS and navigate through the
utility.

                        I didn't have this problem until I upgraded to 5.5,
so I never tried using the NETCONTROL UPDATE to fix the problem.

                        Hope this helps.. :-)

                        Dane Bodamer
                        Systems Manager
                        MicroWarehouse Inc.

                        P.s.  This is the first time I replied to the list,
so if I replied wrong please let me know.  Thanx :-)

                                -----Original Message-----
                                From:   Joseph Rosenblatt
[SMTP:[log in to unmask]]
                                Sent:   Tuesday, August 04, 1998 11:21 AM
                                To:     [log in to unmask]
                                Subject:        Question

                                James Trout asked:
                                >I have a question.. we had a problem last
week where the network kept
                                >dropping on the HP and stopped protocols
showed up on the console... we
                                >couln't figure out why... and it quit on
wednesday ...

                                I'm not sure this is the same thing but I
occasionally have problems
                                with my remote sites loosing there
connection to the HP. I have found
                                that this is occurs when a router or hub
goes down for any reason, i.e.
                                if the connection is bad from either the
network side or the HP side.

                                The HP LAN will look for the device 200
times (this means send 200
                                packets not 200 attempted logons.) After
that it stops trying and says
                                that the NODE is not found. At this point
you need to "recycle" the
                                network. This is done by:

                                :NETCONTROL UPDATE;NET=lan name (Usually
LAN1)
                                :NETCONTROL UPDATE;NET=LOOP

                                If your problem is the same as mine this
should correct it. Worse case
                                scenario you may have to down the network
and restart it. This of course
                                logs all users off so it should be used as a
last resort.