> On 5 Jun 1998, Robert Hough wrote:
> > And here's the disconnect:
> >
> > S0: Sending Disconnect Request
> > S0: Received Clear Conf (B11 ID:55)
> > S2: Sending Disconnect Request
> > S2: Received Clear Conf (B12 ID:56)
> > S0: Session Terminated - Admin Reset
> > S2: Session Terminated - Admin Reset
> >
> >
> > This happens about 2-3 minutes after the connection is made. At first I
> > thought maybe it was just an idle time out, so I setup a 10mb download to
> > keep it busy. That didn't help. I then thought maybe it was a session
> > timeout, so I cranked that up, just to be safe. Still nothing. What sickens
> > me about this whole thing was, I called Lucent this morning, and as one of
> > the tech's were helping me out, the damned thing stayed connected for like
> > 25 minutes! After the call was over, things were back to the way it was. I
> > dont know if she did something during that time, but if so, can someone
> > tell me what it was, or should we hire a lady to look after sensitive PM's? :)
>
> This looks a lot like you have a script (running from cron probably) that
> looks at who is logged into your PMs and kicks people out that are logged
> in more than once (which a MP connection would appear as to many of those
> scripts). Are you running anything to prevent multiple logins? The
> reason I think this, is because "Admin Reset" usually means it was done
> "manually".
I haven't played to see what Port-Limit = 1 does.... would this cause the
same?
Also, are both B going to the same box? If not you may want the set
reported_ip on all boxes to say the same thing...
-- Aloha from Paradise,Sherwood
- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>