Re: PM2 connecting to port 1642

John G. Thompson (jgt10@livingston.com)
Sat, 10 May 1997 15:02:56 -0700 (PDT)

Here you go guys...

At he command line do...

Command> set all service_login rlogin
Command> save all
Command> reset all

What is happening is that the async ports go out with a default config
that uses the portmaster service, which uses port 1642.

JGT
IP petro primate

On Sat, 10 May 1997, Dick St.Peters wrote:
>
> John W. Temples writes:
>
> > All of my Portmasters are pounding one of my UNIX servers with TCP
> > connection requests to port 1642. I searched the list archives, and see
>
> > Is there anything I can do to stop this?
>
> I've had similar things happen - something stuck in the PM that
> doesn't clear even with a power cycle. I use a packet filter to
> prevent the offending machine from bothering anything else.
>
> --
> Dick St.Peters, stpeters@NetHeaven.com
> Gatekeeper, NetHeaven, Ballston Spa, NY, 1-800-910-6671 (voice)
> Albany/Saratoga/Glens Falls/North Creek/Lake Placid/Blue Mountain Lake
> First Internet service based in the 518 area code
>

John G. Thompson Livingston Enterprises Inc. Phone: (800) 458-9966
JOAT(MON) 4464 Willow Road Fax: (510) 426-8951
support@livingston.com Pleasanton, CA 94588 http://www.livingston.com