HP3000-L Archives

October 2020, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Landin <[log in to unmask]>
Reply To:
Mark Landin <[log in to unmask]>
Date:
Sat, 10 Oct 2020 21:13:30 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (90 lines)
Sounds like your routing table is getting polluted with bad RIP updates.
Doubt it’s coming from the printers themselves. Not sure how you’d track
that down. Maybe if you put a PC running Wireshark on the same LAN you
could find the source of the bogus updates.

On Sat, Oct 10, 2020 at 13:37 Craig Lalley <
[log in to unmask]> wrote:

> Yes, I have seen this before.  I suppose you will probably want to know
> how I resolved it.I don't remember...  but.
> Network Redirects come to mind.   Are they getting network redirects at
> the console?  Do they have the correct gateway in NMMGR?   Have you looked
> at the buffers?  NETTOOL.NET --> RESOURCE --> DISPLAY?
> Of course what does LINKCONTROL @,A show?
>
> Finally look at the Name Resolution.
>
> I know that probably doesn't help.  It's all I can think of right now.
>
> -Craig
>
>
>     On Saturday, October 10, 2020, 11:25:33 AM PDT, Gilles Schipper <
> [log in to unmask]> wrote:
>
>  External Email
>
> Has anyone seen the following situation:
>
> All of sudden, 2 HP3000's (running MPE/iX 6.5) are unable to accept VT
> sessions from terminals on same network.
>
> (Network administrators unable to point to any network configuration or
> equipment issues that could explain the problem.
>
> Further investigation show that one or two ip's associated with PRINTERS
> (usually 1, but sometimes 2) have appeared in the "GATELIST" command
> within NETTOOLS.NET.SYS (along with the ip address of the router).
>
> It seems that inability for network terminals to log on to either system
> is ALWAYS due to this bizarre situation that I've never seen before.
>
> Currently, the solution is to run a job every 5 minutes or so that
> issues a NETCONTROL NET=LAN; UPDATE=ALL, which results in ONLY the
> correct router ip address in the GATELIST, and after which everything is
> okay.
>
> Has anyone seen this before?
>
> And how to fix the problem permanently without requiring the running of
> the UPDATE job?
>
> TIA,
>
> Gilles
>
> --
> -----------------------------------------------------
> Gilles Schipper
> GSA Inc.
> HP System Administration Specialists
> PO Box 77566 RPO Sheppard Plaza
> Toronto ON M3H 6A7 Canada
> Tel: 416.702.7900
> email:  [log in to unmask]
> -----------------------------------------------------
>
>
> --
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> This message is not from a UTC.EDU address. Caution should be used in
> clicking links and downloading attachments from unknown senders or
> unexpected email.
>
> * 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 *
>
-- 
"He's old enough to know what's right and young enough not to choose it.
He's strong enough to win the world and weak enough to lose it." - Neal
Peart

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

ATOM RSS1 RSS2