Stopping and starting the network service fixed the problem.  I even had
command files to do it already set up.  I just do not do this sort of stuff
enough to remember it.

Thank all of you so much.

On Mon, May 2, 2022 11:48, Ralph Bagen wrote:
> Yes, James... was typing this response when I saw your e-mail reply.
>
> You could attempt a :NETCONTROL @;UPDATE=ALL  (or UPDATE=INTERNET).
>
> There is really no reason to reboot the HP3000.  Instead perhaps just stop
> and start the network?  Of course that will kick-off any / all NS-VT & Telnet
> users for a few minutes, so you may need to schedule that event.
>
> That is:
>
> 	:NETCONTROL STOP;NET=LAN1 (or your lanlink name)
> 	:NETCONTROL STOP;NET=LOOP
> 	:NSCONTROL STOP
>
> Then in reverse:
>
> 	:NETCONTROL START;NET=LAN1 (or your lanlink name)
> 	:NETCONTROL START;NET=LOOP
> 	:NSCONTROL START
>
> Hope that might solve your issue...
>


-- 
***          e-Mail is NOT a SECURE channel          ***
        Do NOT transmit sensitive data via e-Mail
   Unencrypted messages have no legal claim to privacy
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrne                mailto:[log in to unmask]
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *



* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *