It is very unclear to me whether it is dying because of failed authentication, or because it fails to start ppp after successfully authenticating
I know this sounds trite, but could you please check that your username (zl3kr) and password are set properly. The dialog box in kppp will only reveal **** for the password, but if you do (as root) cat /etc/ppp/pap-secrets and cat /etc/ppp/chap-secrets you will find it in plain text, probably with 'quotes' around. remember these passwords and user names are case sensitive. Make sure that if you report back you do NOT send your password to the list, none of us want the burden of knowing your password, but please do check it. Twice. I am also puzzled by the lack of info in the logs. With debug turned on my ipcop box gives a whole lot of info like this: Aug 28 04:22:04 ipcoph pppd[3349]: sent [LCP ConfReq id=0x1 <magic 0x241a0426>] Aug 28 04:22:07 ipcoph pppd[3349]: sent [LCP ConfReq id=0x1 <magic 0x241a0426>] Aug 28 04:23:01 ipcoph pppd[3349]: sent [LCP ConfReq id=0x1 <magic 0x241a0426>] Aug 28 04:24:01 ipcoph pppd[3349]: sent [LCP ConfReq id=0x1 <magic 0x241a0426>] Aug 28 04:24:34 ipcoph pppd[3349]: LCP: timeout sending Config-Requests Whereas with Alan we only seem to get the final line. I think per the number one google hit on searching "LCP: timeout sending Config-Requests ihug" you should try to turn up "lcp-max-configure" - perhaps to double its current value, as well as lcp-max-failure So to summarise Alan: 1. check your username and password 2. increase the lcp-max-configure and lcp-max-failure settings to 20, or even 30 and try that. (according to man pppd the default is 10) On Mon, 28 Aug 2006 10:03:32 +1200 Alan wrote: > ok removed the + sign and just as it connected it said pppd Daemon died > suddenly. > I changed it then to chap+pap and tried again and got the same message. > When comparing with windows log on after the squeeling stops the connect > is very quick. > When in Linux there is a long delay between the end of the squeeling and > the connect command coming up...as soon as the connect command comes up > it is very quick to the "logging on to Network" coming up and the > starting pppd, then of course it just sits there and times out, so I > guess it must still be looking for something to come from pppd, that it > isnt getting, to set things in motion. > I would love to be able to get this thing to work, but hopefully I will > have an external modem early this week. > > Alan -- Nick Rout <[EMAIL PROTECTED]>
