Re: Creating a PPP connection -V4R5 -- MIDRANGE-L

Mike,

It's not getting through even the first parts of the PPP negotiation. I
would have expected a lot more in this log. If the connection failed you
would see some reset records in the log. Was there more to the log?

Also, if the line is failing you should find an error message in the system
history log. Try using the DSPLOG command after the session is complete. If
you find any diagnostic messages about a failed line put the cursor on the
message and look at the second level text. This can sometimes be helpful
with these types of problems.

Patrick

----- Original Message -----
From: "Mike Silvers" <msilvers@HBS-INC.COM>
To: "Midrange Systems Technical Discussion" <midrange-l@MIDRANGE.COM>
Sent: Friday, January 24, 2003 7:36 AM
Subject: Re: Creating a PPP connection -V4R5


> I tried the logging option.  Here are the results:
>
> 09:27:37.560 === Modem for PPP line PPP : USRobotics 56K V.90 Sportster.
> 09:27:37.581 === Attempting modem reset.
> 09:27:37.606 ==> AT&F1S0=0
> 09:27:37.660 === Reading modem response.
> 09:27:38.313 <== OK
> 09:27:38.419 === Attempting modem initialization.
> 09:27:38.420 ==> AT&D2&C1X4V1Q0S7=70&M4&H1&B1&K1&S1
> 09:27:38.427 === Reading modem response.
> 09:27:39.084 <== OK
> 09:27:39.098 === Attempting modem dial/answer.
> 09:27:39.099 ==> ATS0=2
> 09:27:39.767 <== OK
> 09:27:39.791 === Waiting for incoming call.
> 09:28:03.794 === Reading modem response.
> 09:28:04.308 <== RING
> 09:28:09.055 === Reading modem response.
> 09:28:09.570 <== RING
> 09:28:22.713 === Reading modem response.
> 09:28:23.228 <== CONNECT 28800/ARQ/V34/LAPM/V42BIS
> 09:28:23.433 === Incoming call received.
> 09:28:23.648 === Establishing point-to-point connection for profile PPP.
> 09:28:55.439 === NOTE: LCP sent MAX(10) Configure-Request
> 09:28:58.621 === Att
>
> Any ideas?
>
> Thanks
>
> Mike
>
>
> ----- Original Message -----
> From: "Patrick Townsend" <patownsend@patownsend.com>
> To: "Midrange Systems Technical Discussion" <midrange-l@midrange.com>
> Sent: Thursday, January 23, 2003 10:40 PM
> Subject: Re: Creating a PPP connection -V4R5
>
>
> > Mike,
> >
> > In OpsNav you can set on logging for the PPP connection. In the same
> dialog
> > where you start the PPP connection select the option for logging. You
will
> > then get a printed report with a lot of detail on the PPP negotiation
> > phases. You might find something helpful in there.
> >
> > Patrick
> >
> >
> > ----- Original Message -----
> > From: "Mike Silvers" <msilvers@HBS-INC.COM>
> > To: "Midrange-L list" <midrange-l@MIDRANGE.COM>
> > Sent: Thursday, January 23, 2003 8:26 AM
> > Subject: Creating a PPP connection -V4R5
> >
> >
> > > All,
> > >
> > > I am trying to create a PPP connection using a US Robotics 5686e async
> > > modem.  I have a validation list setup for the valid users, and I have
> > CHAP
> > > password validation.  I have an answer modem setup.  When I start the
> PPP
> > > connection, the line varies on and it waits for a connection.  When I
> dial
> > > in, the modem picks up and there is some communication between my PC
and
> > the
> > > modem.  The PPP line status changes from waiting to answering.  Then
the
> > > connection drops.  The PPP connection goes back to the waiting state.
> The
> > > error I get is that the port has not connected (thanks to win2000 for
> > their
> > > descriptive errors).  The client side then drops.
> > >
> > > I am thinking that it might be in the modem initialization string --
but
> I
> > > don't know where to go with it.....
> > >
> > > Any ideas?
> > >
> > > Mike
> > >
> > >
> > > =======================================
> > > Mike Silvers
> > > Senior Programmer/Analyst
> > > IBM Certified Expert
> > > Hainey Business Systems
> > > Main Office:  (717) 718-9601 ext 237
> > > Branch Office:  (410) 397-8739
> > > http://www.hbs-inc.com
> > > =======================================
> > >
> > >
> > > _______________________________________________
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > > To post a message email: MIDRANGE-L@midrange.com
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> > > or email: MIDRANGE-L-request@midrange.com
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> > >
> > >
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>