You can tell if this is the case by dialing in on one of the modems and
doing 'show netconns' and counting the number of .23 connections. You
can reset the network connections with a 'reset n<n>' where <n> is the
handle (hnd) number in the first column of the netconns display.
On Sat, 21 Dec 1996, Bruce Komito wrote:
>
> We've had this problem for two years and continue to have it. If you
> routinely telnet into your PM, plan on rebooting it every 3-4 weeks as a
> precaution. On the other hand, if you leave it alone, it will run for
> months.
>
> On Sat, 21 Dec 1996, Chris Shenton wrote:
>
> > I installed a PM2e-30 with ComOS-3.3.2 at a customer's site a few
> > months ago, and it operated fine for a couple months. It's got about
> > 20 modems on it.
> >
> > Now, after running for about 90 days, it's having serious problems:
> >
> > * it's refusing telnet connections so the admin can't talk to it
> > (UNIX telnet says "connection refused"; no daemon on that port)
> >
> > * they report that all the users are having problems dialing in --
> > only about one out of five times do they get a valid PPP login.
> >
I would ask you to double check you modem init strings. If you have
questions you can call tech support. Please have a copy of all manuals
for all different modems you have with you when you call.
> > These problems didn't happen earlier, so I am suspecting a memory
> > leak.
This could be. You might want to think about 3.3.3 or the 3.5b17. Given
the distance to the site (YIKES!) you should really have a good back plan
and semi-technical pair of hands at the remote site. (No, there isn't a
general problem, this is just he same general advice I give everyone.)
JGT
-- 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