[SLUG] 'Login Script Failed': LCP frames problem.

["Adam Bogacki" <adam@xxxxxxxxxxx>]

Thanks guys,

(1) I spoke to a techie at Primus who told me that from his end the
disconnect reason appears as

"PPP - No LCP Frames received from remote peer."

He told me that the connection drops off after roughly one minute and
does not get to the point of verifying username and password.

(2) 'Properties of Primus' as defined by pppconfig are

No: 02 9423 0800
ISP Login        login:         Login prompt
User             afb3           ISP user name
ISP Prompt       password:      Password prompt
Password         *******        ISP password
Speed            115200         Port Speed
COM              /dev/ttyS0     modem COM port
Method           chat           Authentification Method

'Advanced Options' include

Modeminit        ATZ            Modem init string
ISP Connect      ' '
Pre-Login                       Pre-login chat
...............................................
Demand           enabled
Nameservers      dynamic
...............................................
Idle Timeout     300 (secs)    i.e. 5 minutes.

(3) I've reproduced the last part of my SYSLOG below.
It was done by hand onto paper then onto M$ Word: apologies for any
obvious errors. 

Note: I have named the system 'tux' ... 

tux kernel: ppp0: returning frame
tux chat [2322]: " ^ M
tux chat [2322]: NO CARRIER
tux chat [2322]: failed [NO CARRIER]
tux pppd [2196]: Connect script failed
tux kernel: ppp: set np 0 to 2
tux kernel: ppp_dev_xmit: dropping (npmode=2) on ppp0
tux last message repeated 5 times
tux kernel: ppp: set np 0 to 0
tux kernel: write frame, count=49
tux kernel: FF 03 00 21 45 00 00 2D
tux kernel: 02 29 00 00 40 11 2C 8C
tux kernel: C0 A8 01 01 80 08 0A 5A
tux kernel: 04 00 00 35 00 19 A5 94
tux kernel: 06 E6 00 00 00 01 00 00
tux kernel: 00 00 00 00 00    02 00
tux kernel: 01
tux kernel: ppp: set np to 3
tux pppd [2196]: Starting link
tux chat [2323]: abort on (BUSY)
tux chat [2323]: abort on (NO CARRIER)
tux chat [2323]: abort on (VOICE)
tux chat [2323]: abort on (NO DIALTONE)
tux chat [2323]: abort on (NO ANSWER)
tux chat [2323]: send (ATZ^M)
tux chat [2323]: expect (OK)
tux chat [2323]: ATZ^M^M
tux chat [2323]: OK
tux chat [2323]: -- got it
tux chat [2323]: send (ATDT0294230800^M)
tux chat [2323]: expect (CONNECT)
tux chat [2323]: ^M
tux kernel:ppp0: returning frame
tux last message repeated 6 times
tux chat [2323]: ATDT0294230800^M^M
tux chat [2323]: CONNECT
tux chat [2323]: -- got it
tux chat [2323]: send (^M)
tux chat [2323]: expect (login:)
tux chat [2323]: 115200^M
tux kernel:ppp0: returning frame
tux chat [2323]: !@#$%^&*()_+ 
		     
                 [6 lines of rubbish] 

(4) as noted before, this has not happened with previous Debian installs
and my XP drive connection to Primus has no problem - it sent this
message.

(5) How do I fix the LCP frames problem?

Adam Bogacki

P.O. Box 38, Earlwood, NSW 2206, Australia
afb3@xxxxxxxxxxxxx   [current ISP]
adam@xxxxxxxxxxx       [forwarding]