Koozali.org: home of the SME Server

Dial-up problems!!

Brandon Friedman

Dial-up problems!!
« on: September 27, 2000, 08:05:53 PM »
Hi there

We are having a problem with e-smith dial-up. We are using a 3Com faxmodem - it appears that e-smith is not resetting the modem properly - I have checked the /var/log/messages file. It tells me that the connection script failed????

Any ideas or suggestions?

Thanks
Brandon

Charlie Brady

RE: Dial-up problems!!
« Reply #1 on: September 27, 2000, 08:55:36 PM »
Brandon Friedman wrote:

> We are having a problem with e-smith dial-up. We are using a
> 3Com faxmodem - it appears that e-smith is not resetting the
> modem properly - I have checked the /var/log/messages file. It
> tells me that the connection script failed????

"connection script failed" just means that the connection script failed. What matters is at which point it fails - could be modem not responding, ISP number busy, ISP number ringing out etc. You should be able to work that out from the contents of /var/log/messages.

Charlie

Chris Booyens

RE: Dial-up problems!!
« Reply #2 on: September 28, 2000, 01:48:14 PM »
Hi Charlie,


Here is part of the log file.  The system connects and retrieve e-mail after a system reboot but then stops at a certain stage?


Sep 28 08:25:45 e-smith chat[10563]: ^M
Sep 28 08:25:45 e-smith chat[10563]: ATL0M0DT2833000^M^M
Sep 28 08:25:45 e-smith chat[10563]: ERROR
Sep 28 08:25:45 e-smith chat[10563]:  -- failed
Sep 28 08:25:45 e-smith chat[10563]: Failed (ERROR)
Sep 28 08:25:45 e-smith diald[363]: Connect script failed.
Sep 28 08:25:46 e-smith diald[363]: Delaying 10 seconds before clear to dial.
Sep 28 08:25:56 e-smith diald[363]: Calling site 196.2.45.14
Sep 28 08:25:57 e-smith chat[10565]: abort on (BUSY)
Sep 28 08:25:57 e-smith chat[10565]: abort on (ERROR)
Sep 28 08:25:57 e-smith chat[10565]: abort on (NO CARRIER)
Sep 28 08:25:57 e-smith chat[10565]: abort on (NO DIALTONE)
Sep 28 08:25:57 e-smith chat[10565]: abort on (Invalid Login)
Sep 28 08:25:57 e-smith chat[10565]: abort on (Login incorrect)
Sep 28 08:25:57 e-smith chat[10565]: send (ATZ^M)
Sep 28 08:25:57 e-smith chat[10565]: expect (OK)
Sep 28 08:25:57 e-smith chat[10565]: ATZ^M^M
Sep 28 08:25:57 e-smith chat[10565]: OK
Sep 28 08:25:57 e-smith chat[10565]:  -- got it
Sep 28 08:25:57 e-smith chat[10565]: send (ATL0M0DT2833000^M)
Sep 28 08:25:58 e-smith chat[10565]: expect (CONNECT)
Sep 28 08:25:58 e-smith chat[10565]: ^M
Sep 28 08:25:58 e-smith chat[10565]: ATL0M0DT2833000^M^M
Sep 28 08:25:58 e-smith chat[10565]: ERROR
Sep 28 08:25:58 e-smith chat[10565]:  -- failed
Sep 28 08:25:58 e-smith chat[10565]: Failed (ERROR)
Sep 28 08:25:58 e-smith diald[363]: Connect script failed.
Sep 28 08:25:59 e-smith diald[363]: Delaying 10 seconds before clear to dial.
Sep 28 08:26:09 e-smith diald[363]: Calling site 196.2.45.14
Sep 28 08:26:10 e-smith chat[10573]: abort on (BUSY)
Sep 28 08:26:10 e-smith chat[10573]: abort on (ERROR)
Sep 28 08:26:10 e-smith chat[10573]: abort on (NO CARRIER)
Sep 28 08:26:10 e-smith chat[10573]: abort on (NO DIALTONE)
Sep 28 08:26:10 e-smith chat[10573]: abort on (Invalid Login)
Sep 28 08:26:10 e-smith chat[10573]: abort on (Login incorrect)
Sep 28 08:26:10 e-smith chat[10573]: send (ATZ^M)
Sep 28 08:26:10 e-smith chat[10573]: expect (OK)
Sep 28 08:26:10 e-smith chat[10573]: ATZ^M^M
Sep 28 08:26:10 e-smith chat[10573]: OK
Sep 28 08:26:10 e-smith chat[10573]:  -- got it
Sep 28 08:26:10 e-smith chat[10573]: send (ATL0M0DT2833000^M)
Sep 28 08:26:10 e-smith chat[10573]: expect (CONNECT)
Sep 28 08:26:10 e-smith chat[10573]: ^M
Sep 28 08:26:10 e-smith chat[10573]: ATL0M0DT2833000^M^M
Sep 28 08:26:10 e-smith chat[10573]: ERROR
Sep 28 08:26:10 e-smith chat[10573]:  -- failed
Sep 28 08:26:10 e-smith chat[10573]: Failed (ERROR)
Sep 28 08:26:10 e-smith diald[363]: Connect script failed.
Sep 28 08:26:11 e-smith diald[363]: Delaying 10 seconds before clear to dial.
Sep 28 08:26:21 e-smith diald[363]: Calling site 196.2.45.14
Sep 28 08:26:22 e-smith chat[10575]: abort on (BUSY)
Sep 28 08:26:22 e-smith chat[10575]: abort on (ERROR)
Sep 28 08:26:22 e-smith chat[10575]: abort on (NO CARRIER)
Sep 28 08:26:22 e-smith chat[10575]: abort on (NO DIALTONE)
Sep 28 08:26:22 e-smith chat[10575]: abort on (Invalid Login)
Sep 28 08:26:22 e-smith chat[10575]: abort on (Login incorrect)
Sep 28 08:26:22 e-smith chat[10575]: send (ATZ^M)
Sep 28 08:26:22 e-smith chat[10575]: expect (OK)
Sep 28 08:26:22 e-smith chat[10575]: ATZ^M^M
Sep 28 08:26:22 e-smith chat[10575]: OK
Sep 28 08:26:22 e-smith chat[10575]:  -- got it
Sep 28 08:26:22 e-smith chat[10575]: send (ATL0M0DT2833000^M)
Sep 28 08:26:23 e-smith chat[10575]: expect (CONNECT)
Sep 28 08:26:23 e-smith chat[10575]: ^M
Sep 28 08:26:23 e-smith chat[10575]: ATL0M0DT2833000^M^M
Sep 28 08:26:23 e-smith chat[10575]: ERROR
Sep 28 08:26:23 e-smith chat[10575]:  -- failed
Sep 28 08:26:23 e-smith chat[10575]: Failed (ERROR)
Sep 28 08:26:23 e-smith diald[363]: Connect script failed.
Sep 28 08:26:24 e-smith diald[363]: Delaying 10 seconds before clear to dial.




Thanks

Chris

Harry Werkman

RE: Dial-up problems!!
« Reply #3 on: February 27, 2001, 09:46:17 AM »
The following message from /var/log/messages seems to indicate a MODEM init string error;
Sep 28 08:26:23 e-smith chat[10575]: ATL0M0DT2833000^M^M
Sep 28 08:26:23 e-smith chat[10575]: ERROR
Sep 28 08:26:23 e-smith chat[10575]: -- failed
Sep 28 08:26:23 e-smith chat[10575]: Failed (ERROR)

Try to place the L0M0 init into the previous init string (also ensure
that the init string is valid).

Regards,
Harry W.