[ale] still cant connect to bellsouth

Gary Maltzen maltzen at mm.com
Fri Jun 25 11:16:04 EDT 1999


If you read more carefully, you'll see that he got neither a "name:" nor a
"ogin:" prompt, but hung up immediately after getting the trailing
("115200^m") part of the CONNECT response.

I assume you are correct about that he should expect a "name:" prompt; I'm
in USWestLand.

-----Original Message-----
 From: Philip Rodgers <prodgers at switchco.com>


your first expect is wrong Bellsouth looks for a Username: not a Login:
so you need to change the script to expect name: and then ssword:

Gary Maltzen wrote:

> It looks like you aren't absorbing the connect speed or are sending the
> first ^m too soon. What does your connect script look like? I would expect
> something like this...
>
> abort BUSY
> abort 'NO CARRIER'
> '' ATZ
> OK atdt7703008900
> TIMEOUT 45 CONNECT\d ''
> TIMEOUT 10 ogin:--ogin: username
> TIMEOUT 5  sword: password
>
> -----Original Message-----
> From: Martin Nichols <mnichol at bellsouth.net>
>
>     Hi, Iam having absolutley no luck in connecting to bellsouth my
> modem dials it sounds like it wants to connect then quits. here is the
> message i am getting from my log maybe this will give someone a clue.
>
> pppd started for ppp0 on /dev/ttys1 at 115200
> atdt7703008900^m^m
> connect
> --got it
> send(^m)
> expect(ogin:)
> 115200^m
> connect script failed
> alarm
> failed
> exit
>
> Does this help anyone? Using Redhat 6.0
>
> ThankYou, Marty






More information about the Ale mailing list