Re: Nick, Australia kernel 2.6.31 -- connect 460800

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

this type of problem is unlikely related to the init. string used nor the driver. If you believe this is a init. string related problem, you can always try with simply 'AT &F' to use factory defaults.

You could try to connect using 'minicom' or any low-level telecommunication software to determine if the dialing program is sending the right user/pass. If it still doesn't work doing it the manual way, you should probably contact your ISP to see what information they expect from you to connect to their services. I've seen a ISP that do require a complete email address as user name, you could try that.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
support@xxxxxxxxxxxx


Nick wrote:
Marv

Have you had any suggestions from Jonathan - or any idea what I could
try next?

Nick

Nick Wahl wrote:
I am still stuck, Jonathan, and I was wondering if it is possible that
a password, which works in Windows, wouldn't work in Linux.

If that can't be the problem, I'd be grateful for any advice on what I
can try to make this work.

Regards,
Nick

Marvin Stodolsky wrote:
Nick

The sample you sent below seems to be effective so far as the Init
strings are concerned.
However there remains the Authorization problem.

Jonathan,
   This is a hsfmodem installation.  Any suggestions?

MarvS

On Wed, Jan 6, 2010 at 1:02 AM, Nick <nwahl@xxxxxxxxxxxxxx> wrote:
Marv, I am really glad we are not trying to fly a plane here!

I tried the Init2 and Init3 you recommended and, I think, all possible
combination of these with ;, SPACEs (bad init string) and username.
All, except SPACEs ended with 'Authorization failed' (see one example
below).

Before I try to fiddle with AT+VCID, I would prefer to see what you
suggest I do.

Nick

nw@nw:~$ wvdial
--> WvDial: Internet dialer version 1.60
--> Initializing modem.
--> Sending: ATZ
OK
--> Sending: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2
AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2
OK
--> Sending: ATS7=60S30=0L2M1+ES=3,0,2;+DS=3;+DS44=3;+IFC=2,2;X4
OK
--> Modem initialized.
--> Sending: ATDT0198331333
--> Waiting for carrier.
+MCR: V90
+MRR: 45333
+ER: LAPM
+DR: V42B
CONNECT 44000
User Access Verification
 Username: username: login:
--> Carrier detected.  Waiting for prompt.
 Username: username: login:
--> Looks like a login prompt.
--> Sending: nwahl
nwahl
 Password: password:
--> Looks like a password prompt.
--> Sending: (password)
% Authorization failed.
--> Connected, but carrier signal lost!  Retrying...
^CCaught signal 2:  Attempting to exit gracefully...
--> Disconnecting at Wed Jan  6 11:44:13 2010
nw@nw:~$

Jacques Goldberg wrote:
Marv, Nick:

AT+VCID is a relatively new AT command which has to do with
identification of the caller ID by the modem.

It did not exist when I was using call back so that I cannot say if it
is necessary at all, and where it ought to be placed.

I suggest studying the document

http://vocpsystem.com/callerid_setup.php?mode=function


Jacques


Marvin Stodolsky wrote:

Nick

Try using in wvdial.conf
Init2 = AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2
Init3 = ATS7=60S30=0L2M1+ES=3,0,2;+DS=3;+DS44=3;+IFC=2,2;X4

I'm not sure how the ; translate in Linux, you may have to use SPACEs
instead.

Jacques,
   Does this look like part of a CALL BACK protocol

01-03-2010 20:08:58.920 - Waiting for a call.
01-03-2010 20:08:58.930 - Send: at+vcid=1<cr>

MarvS

On Sun, Jan 3, 2010 at 6:03 AM, Nick <nwahl@xxxxxxxxxxxxxx> wrote:

Thanks for not putting this in the too hard basket, Marv! - Nick

01-03-2010 20:08:58.670 - File: C:\Windows\system32\tapisrv.dll,
Version 6.0.6002
01-03-2010 20:08:58.670 - File: C:\Windows\system32\unimdm.tsp,
Version 6.0.6002
01-03-2010 20:08:58.670 - File: C:\Windows\system32\unimdmat.dll,
Version 6.0.6000
01-03-2010 20:08:58.670 - File: C:\Windows\system32\uniplat.dll,
Version 6.0.6000
01-03-2010 20:08:58.670 - File: C:\Windows\system32\drivers\modem.sys,
Version 6.0.6001
01-03-2010 20:08:58.670 - File: C:\Windows\system32\modemui.dll,
Version 6.0.6002
01-03-2010 20:08:58.685 - File: C:\Windows\system32\mdminst.dll,
Version 6.0.6001
01-03-2010 20:08:58.685 - Modem type: HDAUDIO Soft Data Fax Modem with
SmartCP
01-03-2010 20:08:58.685 - Modem inf path: oem8.inf
01-03-2010 20:08:58.685 - Modem inf section: ModemX
01-03-2010 20:08:58.685 - Matching hardware ID:
hdaudio\func_02&ven_14f1&dev_5045&subsys_103c30d9
01-03-2010 20:08:58.857 - 115200,8,N,1, ctsfl=1, rtsctl=2
01-03-2010 20:08:58.857 - Initializing modem.
01-03-2010 20:08:58.858 - DSR is low while initializing the modem.
Verify modem is turned on.
01-03-2010 20:08:58.895 - Send: AT<cr>
01-03-2010 20:08:58.896 - Recv: AT<cr>
01-03-2010 20:08:58.896 - Command Echo
01-03-2010 20:08:58.896 - Recv: <cr><lf>OK<cr><lf>
01-03-2010 20:08:58.896 - Interpreted response: OK
01-03-2010 20:08:58.906 - Send:
AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
01-03-2010 20:08:58.909 - Recv:
AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
01-03-2010 20:08:58.909 - Command Echo
01-03-2010 20:08:58.909 - Recv: <cr><lf>OK<cr><lf>
01-03-2010 20:08:58.909 - Interpreted response: OK
01-03-2010 20:08:58.919 - Send:
ATS7=60S30=0L2M1+ES=3,0,2;+DS=3;+DS44=3;+IFC=2,2;X4<cr>
01-03-2010 20:08:58.920 - Recv: <cr><lf>OK<cr><lf>
01-03-2010 20:08:58.920 - Interpreted response: OK
01-03-2010 20:08:58.920 - Waiting for a call.
01-03-2010 20:08:58.930 - Send: at+vcid=1<cr>
01-03-2010 20:08:58.978 - Recv: <cr><lf>OK<cr><lf>
01-03-2010 20:08:58.978 - Interpreted response: OK
01-03-2010 20:08:58.979 - Send: ATS0=0<cr>
01-03-2010 20:08:58.980 - Recv: <cr><lf>OK<cr><lf>
01-03-2010 20:08:58.980 - Interpreted response: OK
01-03-2010 20:08:58.980 - 115200,8,N,1, ctsfl=1, rtsctl=2
01-03-2010 20:08:58.980 - Initializing modem.
01-03-2010 20:08:58.980 - DSR is low while initializing the modem.
Verify modem is turned on.
01-03-2010 20:08:58.990 - Send: AT<cr>
01-03-2010 20:08:58.993 - Recv: <cr><lf>OK<cr><lf>
01-03-2010 20:08:58.993 - Interpreted response: OK
01-03-2010 20:08:59.003 - Send:
AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
01-03-2010 20:08:59.005 - Recv: <cr><lf>OK<cr><lf>
01-03-2010 20:08:59.005 - Interpreted response: OK
01-03-2010 20:08:59.015 - Send:
ATS7=60S30=0L2M1+ES=3,0,2;+DS=3;+DS44=3;+IFC=2,2;X4<cr>
01-03-2010 20:08:59.016 - Recv: <cr><lf>OK<cr><lf>
01-03-2010 20:08:59.016 - Interpreted response: OK
01-03-2010 20:08:59.016 - Dialing.
01-03-2010 20:08:59.026 - Send: ATDT##########<cr>
01-03-2010 20:09:26.029 - Recv: <cr><lf>+MCR: V90<cr><lf>
01-03-2010 20:09:26.029 - Interpreted response: Informative
01-03-2010 20:09:26.029 - Recv: <cr><lf>+MRR: 40000<cr><lf>
01-03-2010 20:09:26.029 - Interpreted response: Informative
01-03-2010 20:09:26.837 - Recv: <cr><lf>+ER: LAPM<cr><lf>
01-03-2010 20:09:26.837 - Interpreted response: Informative
01-03-2010 20:09:26.837 - Recv: <cr><lf>+DR: V42B<cr><lf>
01-03-2010 20:09:26.837 - Interpreted response: Informative
01-03-2010 20:09:26.837 - Recv: <cr><lf>CONNECT 40000<cr><lf>
01-03-2010 20:09:26.837 - Interpreted response: Connect
01-03-2010 20:09:26.837 - Connection established at 40000bps.
01-03-2010 20:09:26.837 - Error-control on.
01-03-2010 20:09:26.837 - Data compression on.
01-03-2010 20:09:56.836 - Read: Total: 14326, Per/Sec: 490, Written:
Total: 35164, Per/Sec: 1208

Marvin Stodolsky wrote:

Nick,

The problem doesn't seem to be the options then.
Could you make a Port.log of one of your dialups under Microsoft?
The option to do so will be somewhere within the Modem setup choices.

MarvS

On Fri, Jan 1, 2010 at 9:36 AM, Nick Wahl <nwahl@xxxxxxxxxxxxxx> wrote:

Am I glad you know more about this than I, Marv. I get exactly the
same output. - Nick

nw@nw:~$ (egrep -v '#|^ *$' /etc/ppp/options)
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
nw@nw:~$

Marvin Stodolsky wrote:

Nick

$ man pppd
relates for error 2
       2      An error was detected in processing the options given,
such as two mutually exclusive options being used.

Please run:
$(egrep -v '#|^ *$' /etc/ppp/options)
and send me the output the List the output.
on my System the output is below

MarvS

asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx




On Mon, Dec 28, 2009 at 9:11 PM, Nick <nwahl@xxxxxxxxxxxxxx> wrote:

Thanks, Marv. I thought the 'under Linux' was the answer, but it
wasn't (see dialout attempt below). - Nick

nw@nw:~$ sudo wvdial
--> WvDial: Internet dialer version 1.60
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT0198331333
--> Waiting for carrier.
ATDT0198331333
CONNECT 57600
User Access Verification
 Username: username: login:
--> Carrier detected.  Waiting for prompt.
 Username: username: login:
--> Looks like a login prompt.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--> Sending: pacific.net.au/nwahl
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
pacific.net.au/nwahl
 Password: password:
--> Looks like a password prompt.
--> Sending: (password)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
% Authorization failed.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--> Connected, but carrier signal lost!  Retrying...
^CCaught signal 2:  Attempting to exit gracefully...
--> Disconnecting at Tue Dec 29 11:35:55 2009
nw@nw:~$

Marvin Stodolsky wrote:

Nick,

If your IP uses CHAP authentification your may need instead of
LoginName under Linux
   pacific.net.au/LoginName

MarvS

[snip]







[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux