on Sun, Dec 31, 2000 at 04:16:15PM -0600, John Hasler ([EMAIL PROTECTED]) wrote:
> Karsten M. Self writes:
> > Almost *all* ISPs now provide instructions on how to connect via
> > GNU/Linux,...
>
> However, it is usually best not to follow those instructions as they are
> usually garbled. Just mi
Karsten M. Self writes:
> Almost *all* ISPs now provide instructions on how to connect via
> GNU/Linux,...
However, it is usually best not to follow those instructions as they are
usually garbled. Just mine them for information.
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wiscon
ne
> > > of them everything goes fine, with the
> > > other I get
> > >
> > > Dec 31 10:50:07 micron pppd[810]: Connect script failed
> > > Dec 31 10:50:08 micron pppd[810]: Exit.
> > >
> > > what could be wrong. I think that the scr
connect to them, but while with one of them everything goes fine, with the
> other I get
>
> Dec 31 10:50:07 micron pppd[810]: Connect script failed
> Dec 31 10:50:08 micron pppd[810]: Exit.
>
> what could be wrong. I think that the script is the same for both ISP.
Could be a lot
]: Connect script failed
Dec 31 10:50:08 micron pppd[810]: Exit.
what could be wrong. I think that the script is the same for both ISP.
Thanks is advance for the help!!!
Regards and happy new millenium!!
Marcelo
antos wrote:
jh0u >Happy New Year!
jh0u >
jh0u > I get a connect script failed when I try to use pon to connect to my
ISP.
jh0u >it used to work before. Here is the exact error message:
jh0u >
jh0u >debian:/etc# ln ?sf /dev/ttyS0 /dev/modem
jh0u >debian:/etc# pon x
jh0u >
Happy New Year!
I get a connect script failed when I try to use pon to connect to my ISP.
it used to work before. Here is the exact error message:
debian:/etc# ln sf /dev/ttyS0 /dev/modem
debian:/etc# pon x
debian:/etc# tail f /var/log/ppp.log
Jan 4 08:13:15 debian pppd[178]:Connect
On 16 Mar 1999q, John Hasler wrote:
> Anthony Campbell writes:
> > Thanks for the reply and helpful offer; yes it was garbled. I've now
> > discovered there should be a space after the colon (ogin: achc).
>
> How did it get garbled? pppconfig shouldn't do that.
> --
> John Hasler
Anthony Campbell writes:
> Thanks for the reply and helpful offer; yes it was garbled. I've now
> discovered there should be a space after the colon (ogin: achc).
How did it get garbled? pppconfig shouldn't do that.
--
John HaslerThis posting is in the public domain.
[EMAIL PROTE
On 15 Mar 1999q, John Hasler wrote:
> Anthony Campbell writes:
> > Mar 15 17:12:57 achc chat[1139]: expect (ogin:achc)
>^
>
> This looks like /etc/chatscripts/provider is garbled. Could you send me a
> copy of that file?
> --
> John Hasler
Anthony Campbell writes:
> Mar 15 17:12:57 achc chat[1139]: expect (ogin:achc)
^
This looks like /etc/chatscripts/provider is garbled. Could you send me a
copy of that file?
--
John HaslerThis posting is in the public domain.
[EM
chat[1139]: expect (ogin:achc)
Mar 15 17:12:57 achc chat[1139]: 31200/ARQ/V34/LAPM/V42BIS^M
Mar 15 17:13:00 achc chat[1139]: anchor-du-1.access.demon.net (2.1.0)^M
Mar 15 17:13:00 achc chat[1139]: ^M
Mar 15 17:13:00 achc chat[1139]: ^M
Mar 15 17:13:42 achc pppd[1137]: Connect script failed
Mar 1
12 matches
Mail list logo