HP found the cause...   Apparently, the UDP software still had a flag
set which indicated that the network was being shutdown.  Their
solution... any guesses???... reboot.  Rebooted at lunch, and the
problem has gone away.  (For now, at least.)

I wasn't showing any signs of an error, other than FTP hanging on the
open statement.

Thanks for the help,
David N. Lukenbill
--------------------------------------------
[log in to unmask]
Raytheon Missile Systems Company, Louisville


> -----Original Message-----
> From: HP3000-L 
> Sent: Wednesday, December 16, 1998 10:55 AM
> To: HP3000-L
> Cc: RCB
> Subject: Re: Networking Problem
> 
> 
>  In <H000019e031b4f21@MHS> [log in to unmask] writes:
> 
> >    I've run into a problem with my network.  (I'm posting 
> this because
> > the HP Response Center hasn't found a solution yet.)  Early this
> > morning, my backup job attempted to abort JSYSLOGD and JDAEMON.  The
> > jobs didn't abort.  (It looks as though the network was dropped from
> > under them before the abort took place.)  At the end of the 
> backup, the
> > network was re-started.  I'm now unable to make any outbound FTP
> > connections.  Any ideas?
> 
> I've seen similar problems on various MPE/iX releases when 
> some process
> using the network was still running when the network was brought down.
> 
> It seems that the network doesn't REALLY come all the way 
> back up after
> that, and as far as I remember, a clean network stop/restart 
> was the only
> way to get things back.
> 
> What errors are you getting when you try to connect out? Network not
> initualized (or similar)?
> 
>        -Chris (remove nospam) Bartram
>