this is in /etc/ppp/options # /etc/ppp/options # # Originally created by Jim Knoble <jmknoble@xxxxxxxxxxxxxxxxxxxxx> # Modified for Debian by alvar Bray <alvar@xxxxxxxxxxx> # Modified for PPP Server setup by Christoph Lameter <clameter@xxxxxxxxxx> # # To quickly see what options are active in this file, use this command: # egrep -v '#|^ *$' /etc/ppp/options # Specify which DNS Servers the incoming Win95 or WinNT Connection should use # Two Servers can be remotely configured # ms-dns 192.168.1.1 # ms-dns 192.168.1.2 # Specify which WINS Servers the incoming connection Win95 or WinNT should use # ms-wins 192.168.1.50 # ms-wins 192.168.1.51 # Run the executable or shell command specified after pppd has # terminated the link. This script could, for example, issue commands # to the modem to cause it to hang up if hardware modem control signals # were not available. #disconnect "chat -- \d+++\d\c OK ath0 OK" # async character map -- 32-bit hex; each bit is a character # that needs to be escaped for pppd to receive it. 0x00000001 # represents '\x01', and 0x80000000 represents '\x1f'. asyncmap 0 # Require the peer to authenticate itself before allowing network # packets to be sent or received. # Please do not disable this setting. It is expected to be standard in # future releases of pppd. Use the call option (see manpage) to disable # authentication for specific peers. #auth noauth # ... Unfortunately, fixing this properly in the peers file # (/etc/ppp/peers/ppp0, typically) is apparently incompatible with the # paradigm used by gnome-system-tools and system-tools-backend for # managing the peers files. So in Ubuntu Feisty we change the default. # Use hardware flow control (i.e. RTS/CTS) to control the flow of data # on the serial port. crtscts # Use software flow control (i.e. XON/XOFF) to control the flow of data # on the serial port. #xonxoff # Specifies that certain characters should be escaped on transmission # (regardless of whether the peer requests them to be escaped with its # async control character map). The characters to be escaped are # specified as a list of hex numbers separated by commas. Note that # almost any character can be specified for the escape option, unlike # the asyncmap option which only allows control characters to be # specified. The characters which may not be escaped are those with hex # values 0x20 - 0x3f or 0x5e. #escape 11,13,ff # Don't use the modem control lines. #local # Specifies that pppd should use a UUCP-style lock on the serial device # to ensure exclusive access to the device. lock # Don't show the passwords when logging the contents of PAP packets. # This is the default. hide-password # When logging the contents of PAP packets, this option causes pppd to # show the password string in the log message. #show-password # Use the modem control lines. On Ultrix, this option implies hardware # flow control, as for the crtscts option. (This option is not fully # implemented.) modem # Set the MRU [Maximum Receive Unit] value to <n> for negotiation. pppd # will ask the peer to send packets of no more than <n> bytes. The # minimum MRU value is 128. The default MRU value is 1500. A value of # 296 is recommended for slow links (40 bytes for TCP/IP header + 256 # bytes of data). #mru 542 # Set the interface netmask to <n>, a 32 bit netmask in "decimal dot" # notation (e.g. 255.255.255.0). #netmask 255.255.255.0 # Disables the default behaviour when no local IP address is specified, # which is to determine (if possible) the local IP address from the # hostname. With this option, the peer will have to supply the local IP # address during IPCP negotiation (unless it specified explicitly on the # command line or in an options file). #noipdefault # Enables the "passive" option in the LCP. With this option, pppd will # attempt to initiate a connection; if no reply is received from the # peer, pppd will then just wait passively for a valid LCP packet from # the peer (instead of exiting, as it does without this option). #passive # With this option, pppd will not transmit LCP packets to initiate a # connection until a valid LCP packet is received from the peer (as for # the "passive" option with old versions of pppd). #silent # Don't request or allow negotiation of any options for LCP and IPCP # (use default values). #-all # Disable Address/Control compression negotiation (use default, i.e. # address/control field disabled). #-ac # Disable asyncmap negotiation (use the default asyncmap, i.e. escape # all control characters). #-am # Don't fork to become a background process (otherwise pppd will do so # if a serial device is specified). #-detach # Disable IP address negotiation (with this option, the remote IP # address must be specified with an option on the command line or in # an options file). #-ip # Disable IPCP negotiation and IP communication. This option should # only be required if the peer is buggy and gets confused by requests # from pppd for IPCP negotiation. #noip # Disable magic number negotiation. With this option, pppd cannot # detect a looped-back line. #-mn # Disable MRU [Maximum Receive Unit] negotiation (use default, i.e. # 1500). #-mru # Disable protocol field compression negotiation (use default, i.e. # protocol field compression disabled). #-pc # Require the peer to authenticate itself using PAP. #+pap # Don't agree to authenticate using PAP. #-pap # Require the peer to authenticate itself using CHAP [Cryptographic # Handshake Authentication Protocol] authentication. #+chap # Don't agree to authenticate using CHAP. #-chap # Disable negotiation of Van Jacobson style IP header compression (use # default, i.e. no compression). #-vj # Increase debugging level (same as -d). If this option is given, pppd # will log the contents of all control packets sent or received in a # readable form. The packets are logged through syslog with facility # daemon and level debug. This information can be directed to a file by # setting up /etc/syslog.conf appropriately (see syslog.conf(5)). (If # pppd is compiled with extra debugging enabled, it will log messages # using facility local2 instead of daemon). debug # Append the domain name <d> to the local host name for authentication # purposes. For example, if gethostname() returns the name porsche, # but the fully qualified domain name is porsche.Quotron.COM, you would # use the domain option to set the domain name to Quotron.COM. #domain <d> # Enable debugging code in the kernel-level PPP driver. The argument n # is a number which is the sum of the following values: 1 to enable # general debug messages, 2 to request that the contents of received # packets be printed, and 4 to request that the contents of transmitted # packets be printed. #kdebug n # Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer # requests a smaller value via MRU negotiation, pppd will request that # the kernel networking code send data packets of no more than n bytes # through the PPP network interface. #mtu <n> # Set the name of the local system for authentication purposes to <n>. # This is a privileged option. With this option, pppd will use lines in the # secrets files which have <n> as the second field when looking for a # secret to use in authenticating the peer. In addition, unless overridden # with the user option, <n> will be used as the name to send to the peer # when authenticating the local system to the peer. (Note that pppd does # not append the domain name to <n>.) #name <n> # Enforce the use of the hostname as the name of the local system for # authentication purposes (overrides the name option). #usehostname # Set the assumed name of the remote system for authentication purposes # to <n>. #remotename <n> # Add an entry to this system's ARP [Address Resolution Protocol] # table with the IP address of the peer and the Ethernet address of this # system. proxyarp # Use the system password database for authenticating the peer using # PAP. Note: mgetty already provides this option. If this is specified # then dialin from users using a script under Linux to fire up ppp wont work. # login # If this option is given, pppd will send an LCP echo-request frame to the # peer every n seconds. Normally the peer should respond to the echo-request # by sending an echo-reply. This option can be used with the # lcp-echo-failure option to detect that the peer is no longer connected. lcp-echo-interval 30 # If this option is given, pppd will presume the peer to be dead if n # LCP echo-requests are sent without receiving a valid LCP echo-reply. # If this happens, pppd will terminate the connection. Use of this # option requires a non-zero value for the lcp-echo-interval parameter. # This option can be used to enable pppd to terminate after the physical # connection has been broken (e.g., the modem has hung up) in # situations where no hardware modem control lines are available. lcp-echo-failure 4 # Set the LCP restart interval (retransmission timeout) to <n> seconds # (default 3). #lcp-restart <n> # Set the maximum number of LCP terminate-request transmissions to <n> # (default 3). #lcp-max-terminate <n> # Set the maximum number of LCP configure-request transmissions to <n> # (default 10). #lcp-max-configure <n> # Set the maximum number of LCP configure-NAKs returned before starting # to send configure-Rejects instead to <n> (default 10). #lcp-max-failure <n> # Set the IPCP restart interval (retransmission timeout) to <n> # seconds (default 3). #ipcp-restart <n> # Set the maximum number of IPCP terminate-request transmissions to <n> # (default 3). #ipcp-max-terminate <n> # Set the maximum number of IPCP configure-request transmissions to <n> # (default 10). #ipcp-max-configure <n> # Set the maximum number of IPCP configure-NAKs returned before starting # to send configure-Rejects instead to <n> (default 10). #ipcp-max-failure <n> # Set the PAP restart interval (retransmission timeout) to <n> seconds # (default 3). #pap-restart <n> # Set the maximum number of PAP authenticate-request transmissions to # <n> (default 10). #pap-max-authreq <n> # Set the maximum time that pppd will wait for the peer to authenticate # itself with PAP to <n> seconds (0 means no limit). #pap-timeout <n> # Set the CHAP restart interval (retransmission timeout for # challenges) to <n> seconds (default 3). #chap-restart <n> # Set the maximum number of CHAP challenge transmissions to <n> # (default 10). #chap-max-challenge # If this option is given, pppd will rechallenge the peer every <n> # seconds. #chap-interval <n> # With this option, pppd will accept the peer's idea of our local IP # address, even if the local IP address was specified in an option. #ipcp-accept-local # With this option, pppd will accept the peer's idea of its (remote) IP # address, even if the remote IP address was specified in an option. #ipcp-accept-remote # Disable the IPXCP and IPX protocols. # To let pppd pass IPX packets comment this out --- you'll probably also # want to install ipxripd, and have the Internal IPX Network option enabled # in your kernel. /usr/doc/HOWTO/IPX-HOWTO.gz contains more info. noipx # Exit once a connection has been made and terminated. This is the default, # unless the `persist' or `demand' option has been specified. #nopersist # Do not exit after a connection is terminated; instead try to reopen # the connection. #persist # Terminate after n consecutive failed connection attempts. # A value of 0 means no limit. The default value is 10. #maxfail <n> # Initiate the link only on demand, i.e. when data traffic is present. # With this option, the remote IP address must be specified by the user on # the command line or in an options file. Pppd will initially configure # the interface and enable it for IP traffic without connecting to the peer. # When traffic is available, pppd will connect to the peer and perform # negotiation, authentication, etc. When this is completed, pppd will # commence passing data packets (i.e., IP packets) across the link. #demand # Specifies that pppd should disconnect if the link is idle for <n> seconds. # The link is idle when no data packets (i.e. IP packets) are being sent or # received. Note: it is not advisable to use this option with the persist # option without the demand option. If the active-filter option is given, # data packets which are rejected by the specified activity filter also # count as the link being idle. #idle <n> # Specifies how many seconds to wait before re-initiating the link after # it terminates. This option only has any effect if the persist or demand # option is used. The holdoff period is not applied if the link was # terminated because it was idle. #holdoff <n> # Wait for up n milliseconds after the connect script finishes for a valid # PPP packet from the peer. At the end of this time, or when a valid PPP # packet is received from the peer, pppd will commence negotiation by # sending its first LCP packet. The default value is 1000 (1 second). # This wait period only applies if the connect or pty option is used. #connect-delay <n> # Packet filtering: for more information, see pppd(8) # Any packets matching the filter expression will be interpreted as link # activity, and will cause a "demand" connection to be activated, and reset # the idle connection timer. (idle option) # The filter expression is akin to that of tcpdump(1) #active-filter <filter-expression> noauth # ---<End of File>--- and is still without conecting.. ----- Original Message ----- From: "Antonio Olivares" <olivares14031@xxxxxxxxx> To: "islanis" <islanis@xxxxxxxxxxxxxx> Cc: <Jacques.Goldberg@xxxxxxx>; <discuss@xxxxxxxxxxxxx>; "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx> Sent: Monday, February 15, 2010 12:57 AM Subject: Re: help motorola sm56 is not conecting Juan, Still the same thing? Did you make the changes suggested by Jacques? Feb 13 14:10:59 juan-desktop pppd[3523]: Remote message: Auth-Reject from Radius Server. Feb 13 14:10:59 juan-desktop pppd[3523]: Connection terminated. Feb 13 14:10:59 juan-desktop pppd[3523]: Exit. Feb 13 14:12:01 juan-desktop pppd[3671]: pppd 2.4.5 started by root, uid 0 Feb 13 14:12:01 juan-desktop pppd[3671]: Using interface ppp0 Feb 13 14:12:01 juan-desktop pppd[3671]: Connect: ppp0 <--> /dev/pts/0 Feb 13 14:12:05 juan-desktop pppd[3671]: Remote message: Auth-Reject from Radius Server. I don't know what to recommend, other than ask if you can record a session from windows and see what options are passed so that you can a connection there? I hope you have changed the number and tried to connect from 06110 to 016110 and also you might want to add to /etc/ppp/options the line noauth Like a section of scanModem outputs something like: Checking settings of: /etc/ppp/options asyncmap 0 noauth crtscts lock hide-password modem proxyarp lcp-echo-interval 30 lcp-echo-failure 4 noipx What is in your /etc/ppp/options? please send us $ sudo cat /etc/ppp/options and if not there add noauth $sudo gedit /etc/ppp/options noauth See if that has any effect. Let us know if this helped or not. Regards, Antonio On 2/13/10, islanis <islanis@xxxxxxxxxxxxxx> wrote: > this is what i did,,,,and the new file mydebug.txt,, nothing yet. > root@juan-desktop:/home/juan# wvdial > --> WvDial: Internet dialer version 1.60 > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > OK > --> Modem initialized. > --> Sending: ATDT060110 > --> Waiting for carrier. > ATDT060110 > CONNECT 52000 > --> Carrier detected. Waiting for prompt. > ************************************************ > * Product Name :Quidway A8010; * > * Product Provider:HuaWei; * > * Internet Server :######; * > ************************************************ > Welcome to INTERNET! > Please input username: > --> Looks like a login prompt. > --> Sending: islanis@xxxxxxxxxxxxxx > Please input password: > --> Looks like a password prompt. > --> Sending: (password) > ********************** > Can't contact authentication server. > Authentication failed! > Please input username: > --> Looks like a login prompt. > --> Sending: islanis@xxxxxxxxxxxxxx > islanis@xxxxxxxxxxxxxx > Please input password: > --> Looks like a password prompt. > --> Sending: (password) > ** > Auth-Reject from Radius Server. > Authentication failed! > Please input username: > --> Looks like a login prompt. > --> Sending: islanis@xxxxxxxxxxxxxx > --> Don't know what to do! Starting pppd and hoping for the best. > --> Starting pppd at Sat Feb 13 14:10:56 2010 > --> Pid of pppd: 3523 > --> pppd: ???[08]X??[08][08]??[08] > --> Using interface ppp0 > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> Authentication (PAP) started > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> Authentication (PAP) failed (Message: "Auth-Reject from Radius > Server." ) > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> Terminate Request (Message: "Failed to authenticate ourselves to > peer" ) > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> pppd: ???[08]X??[08][08]??[08] > --> Disconnecting at Sat Feb 13 14:11:00 2010 > --> Authentication error. > --> We failed to authenticate ourselves to the peer. > --> Maybe bad account or password? > --> Auto Reconnect will be attempted in 5 seconds > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > NO CARRIER > --> Sending: ATQ0 > ATQ0 > OK > --> Re-Sending: ATZ > ATZ > OK > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > OK > --> Modem initialized. > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > OK > --> Modem initialized. > --> Sending: ATDT060110 > --> Waiting for carrier. > ATDT060110 > ^CCaught signal 2: Attempting to exit gracefully... > --> Disconnecting at Sat Feb 13 14:11:14 2010 > root@juan-desktop:/home/juan# wvdial Infomed > --> WvDial: Internet dialer version 1.60 > --> Cannot get information for serial port. > --> 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: ATDT060110 > --> Waiting for carrier. > ATDT060110 > CONNECT 52000 > --> Carrier detected. Waiting for prompt. > ************************************************ > * Product Name :Quidway A8010; * > * Product Provider:HuaWei; * > * Internet Server :######; * > ************************************************ > Welcome to INTERNET! > Please input username: > --> Looks like a login prompt. > --> Sending: islanis@xxxxxxxxxxxxxx > Please input password: > --> Looks like a password prompt. > --> Sending: (password) > ********************** > Can't contact authentication server. > Authentication failed! > Please input username: > --> Looks like a login prompt. > --> Sending: islanis@xxxxxxxxxxxxxx > islanis@xxxxxxxxxxxxxx > Please input password: > --> Looks like a password prompt. > --> Sending: (password) > ** > Auth-Reject from Radius Server. > Authentication failed! > Please input username: > --> Looks like a login prompt. > --> Sending: islanis@xxxxxxxxxxxxxx > --> Don't know what to do! Starting pppd and hoping for the best. > --> Starting pppd at Sat Feb 13 14:12:01 2010 > --> Pid of pppd: 3671 > --> Using interface ppp0 > --> Authentication (PAP) started > --> Authentication (PAP) failed (Message: "Auth-Reject from Radius > Server." ) > --> Terminate Request (Message: "Failed to authenticate ourselves to > peer" ) > --> Disconnecting at Sat Feb 13 14:12:06 2010 > --> Authentication error. > --> We failed to authenticate ourselves to the peer. > --> Maybe bad account or password? > --> Auto Reconnect will be attempted in 5 seconds > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > NO CARRIER > --> Sending: ATQ0 > ATQ0 > OK > --> Re-Sending: ATZ > ATZ > OK > --> Cannot get information for serial port. > --> 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. > --> Cannot get information for serial port. > --> 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: ATDT060110 > --> Waiting for carrier. > ATDT060110 > ^CCaught signal 2: Attempting to exit gracefully... > --> Disconnecting at Sat Feb 13 14:12:19 2010 > root@juan-desktop:/home/juan# wvdial Infomed1 > --> WvDial: Internet dialer version 1.60 > --> Cannot get information for serial port. > --> 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: ATDT8314949 > --> Waiting for carrier. > ATDT8314949 > BUSY > --> The line is busy. Trying again. > --> Sending: ATDT8314949 > --> Waiting for carrier. > ATDT8314949 > BUSY > --> The line is busy. Trying again. > --> Sending: ATDT8314949 > --> Waiting for carrier. > ATDT8314949 > BUSY > --> The line is busy. Trying again. > --> Sending: ATDT8314949 > --> Waiting for carrier. > ATDT8314949 > BUSY > --> The line is busy. Trying again. > --> Sending: ATDT8314949 > --> Waiting for carrier. > ATDT8314949 > ^CCaught signal 2: Attempting to exit gracefully... > --> Disconnecting at Sat Feb 13 14:12:34 2010 > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > From: "Jacques Goldberg" <goldberg@xxxxxxxxxxxxxx> > To: "islanis" <islanis@xxxxxxxxxxxxxx> > Cc: "Antonio Olivares" <olivares14031@xxxxxxxxx>; "Jacques Goldberg" > <Jacques.Goldberg@xxxxxxx>; <discuss@xxxxxxxxxxxxx>; "Marvin Stodolsky" > <marvin.stodolsky@xxxxxxxxx> > Sent: Sunday, February 14, 2010 8:35 PM > Subject: Re: help motorola sm56 is not conecting > > >> Juan >> >> I repeat: you must NOT have Stupid Home active when you dial. >> >> In the report which you sent, IT IS ACTIVE. You can see it yourself by >> this: >> >> Carrier detected. Starting PPP immediately. >> >> There is no prompt for the username and the password. This is exactly >> what Stupid Mode = yes does : ii starts immediately without waiting >> for a prompt for username and password. >> >> Pleas ebe careful and systematic in your work. >> Antonio, please translate. >> Jacques >> Jacques >> >> islanis wrote: >> >>> this is the initial "wvdial" that i put >>> >>> root@juan-desktop:/etc/ppp# wvdial >>> --> WvDial: Internet dialer version 1.60 >>> --> Cannot get information for serial port. >>> --> Initializing modem. >>> --> Sending: ATZ >>> ATZ >>> OK >>> --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>> ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>> OK >>> --> Modem initialized. >>> --> Sending: ATDT060110 >>> --> Waiting for carrier. >>> ATDT060110 >>> CONNECT 52000 >>> --> Carrier detected. Starting PPP immediately. >>> --> Starting pppd at Sat Feb 13 07:31:02 2010 >>> --> Pid of pppd: 4372 >>> --> pppd: ?1X X1X [08]0X >>> --> Using interface ppp0 >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> Authentication (PAP) started >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> Authentication (PAP) failed (Message: "Auth-Reject from Radius >>> Server." ) >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> Terminate Request (Message: "Failed to authenticate ourselves to >>> peer" ) >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> Disconnecting at Sat Feb 13 07:31:05 2010 >>> --> Authentication error. >>> --> We failed to authenticate ourselves to the peer. >>> --> Maybe bad account or password? >>> --> Auto Reconnect will be attempted in 5 seconds >>> --> Cannot get information for serial port. >>> --> Initializing modem. >>> --> Sending: ATZ >>> NO CARRIER >>> --> Sending: ATQ0 >>> ATQ0 >>> OK >>> --> Re-Sending: ATZ >>> ATZ >>> OK >>> --> Cannot get information for serial port. >>> --> Initializing modem. >>> --> Sending: ATZ >>> ATZ >>> OK >>> --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>> ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>> OK >>> --> Modem initialized. >>> --> Cannot get information for serial port. >>> --> Initializing modem. >>> --> Sending: ATZ >>> ATZ >>> OK >>> --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>> ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>> OK >>> --> Modem initialized. >>> --> Sending: ATDT060110 >>> --> Waiting for carrier. >>> ATDT060110 >>> CONNECT 50667 >>> --> Carrier detected. Starting PPP immediately. >>> --> Starting pppd at Sat Feb 13 07:31:44 2010 >>> --> Pid of pppd: 4386 >>> --> pppd: ?1X X1X [08]0X >>> --> Using interface ppp0 >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> Authentication (PAP) started >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> Authentication (PAP) failed (Message: "Auth-Reject from Radius >>> Server." ) >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> Terminate Request (Message: "Failed to authenticate ourselves to >>> peer" ) >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> pppd: ?1X X1X [08]0X >>> --> Disconnecting at Sat Feb 13 07:31:47 2010 >>> --> Authentication error. >>> --> We failed to authenticate ourselves to the peer. >>> --> Maybe bad account or password? >>> --> Auto Reconnect will be attempted in 10 seconds >>> --> Cannot get information for serial port. >>> --> Initializing modem. >>> --> Sending: ATZ >>> NO CARRIER >>> --> Sending: ATQ0 >>> ATQ0 >>> OK >>> --> Re-Sending: ATZ >>> ATZ >>> OK >>> --> Cannot get information for serial port. >>> --> Initializing modem. >>> --> Sending: ATZ >>> ATZ >>> OK >>> --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>> ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>> OK >>> --> Modem initialized. >>> --> Cannot get information for serial port. >>> --> Initializing modem. >>> --> Sending: ATZ >>> ATZ >>> OK >>> --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>> ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>> OK >>> --> Modem initialized. >>> --> Sending: ATDT060110 >>> --> Waiting for carrier. >>> ATDT060110 >>> ^CCaught signal 2: Attempting to exit gracefully... >>> --> Disconnecting at Sat Feb 13 07:32:08 2010 >>> ////*********///////////***********//////////********////////**********///////////**********//////// >>> and this comes out in syslog when i activate the debug in >>> /etc/ppp/option >>> and i put wvdial Infomed >>> >>> >>> Feb 13 07:30:01 juan-desktop /USR/SBIN/CRON[3747]: (root) CMD (test -x >>> /etc/init.d/anacron && /usr/sbin/invoke-rc.d anacron start >/dev/null) >>> Feb 13 07:30:01 juan-desktop /USR/SBIN/CRON[3749]: (root) CMD ([ -x >>> /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null) >>> Feb 13 07:31:02 juan-desktop pppd[4372]: pppd 2.4.5 started by root, uid >>> 0 >>> Feb 13 07:31:02 juan-desktop pppd[4372]: using channel 1 >>> Feb 13 07:31:02 juan-desktop pppd[4372]: Using interface ppp0 >>> Feb 13 07:31:02 juan-desktop pppd[4372]: Connect: ppp0 <--> /dev/pts/0 >>> Feb 13 07:31:02 juan-desktop pppd[4372]: sent [LCP ConfReq id=0x1 >>> <asyncmap >>> 0x0> <magic 0x441c83a3> <pcomp> <accomp>] >>> Feb 13 07:31:03 juan-desktop pppd[4372]: rcvd [LCP ConfReq id=0xb5 <mru >>> 1500> <asyncmap 0xffffffff> <auth pap> <magic 0x1cb954f2> <mrru 1500> >>> <ssnhf> <endpoint [local]>] >>> Feb 13 07:31:03 juan-desktop pppd[4372]: sent [LCP ConfRej id=0xb5 <mrru >>> 1500> <ssnhf>] >>> Feb 13 07:31:03 juan-desktop pppd[4372]: rcvd [LCP ConfRej id=0x1 >>> <pcomp> >>> <accomp>] >>> Feb 13 07:31:03 juan-desktop pppd[4372]: sent [LCP ConfReq id=0x2 >>> <asyncmap >>> 0x0> <magic 0x441c83a3>] >>> Feb 13 07:31:03 juan-desktop pppd[4372]: rcvd [LCP ConfReq id=0xb6 <mru >>> 1500> <asyncmap 0xffffffff> <auth pap> <magic 0x1cb911d1> <endpoint >>> [local]>] >>> Feb 13 07:31:03 juan-desktop pppd[4372]: sent [LCP ConfAck id=0xb6 <mru >>> 1500> <asyncmap 0xffffffff> <auth pap> <magic 0x1cb911d1> <endpoint >>> [local]>] >>> Feb 13 07:31:03 juan-desktop pppd[4372]: rcvd [LCP ConfAck id=0x2 >>> <asyncmap >>> 0x0> <magic 0x441c83a3>] >>> Feb 13 07:31:03 juan-desktop pppd[4372]: sent [LCP EchoReq id=0x0 >>> magic=0x441c83a3] >>> Feb 13 07:31:03 juan-desktop pppd[4372]: sent [PAP AuthReq id=0x1 >>> user="islanis@xxxxxxxxxxxxxx" password=<hidden>] >>> Feb 13 07:31:04 juan-desktop pppd[4372]: rcvd [LCP EchoRep id=0x0 >>> magic=0x1cb911d1] >>> Feb 13 07:31:04 juan-desktop pppd[4372]: rcvd [PAP AuthNak id=0x1 >>> "Auth-Reject from Radius Server."] >>> Feb 13 07:31:04 juan-desktop pppd[4372]: Remote message: Auth-Reject >>> from >>> Radius Server. >>> Feb 13 07:31:04 juan-desktop pppd[4372]: PAP authentication failed >>> Feb 13 07:31:04 juan-desktop pppd[4372]: sent [LCP TermReq id=0x3 >>> "Failed >>> >>> to >>> authenticate ourselves to peer"] >>> Feb 13 07:31:05 juan-desktop pppd[4372]: rcvd [LCP TermAck id=0x3] >>> Feb 13 07:31:05 juan-desktop pppd[4372]: Connection terminated. >>> Feb 13 07:31:05 juan-desktop pppd[4372]: Exit. >>> Feb 13 07:31:44 juan-desktop pppd[4386]: pppd 2.4.5 started by root, uid >>> 0 >>> Feb 13 07:31:44 juan-desktop pppd[4386]: using channel 2 >>> Feb 13 07:31:44 juan-desktop pppd[4386]: Using interface ppp0 >>> Feb 13 07:31:44 juan-desktop pppd[4386]: Connect: ppp0 <--> /dev/pts/0 >>> Feb 13 07:31:44 juan-desktop pppd[4386]: sent [LCP ConfReq id=0x1 >>> <asyncmap >>> 0x0> <magic 0xd438a5f> <pcomp> <accomp>] >>> Feb 13 07:31:44 juan-desktop pppd[4386]: rcvd [LCP ConfReq id=0xfa <mru >>> 1500> <asyncmap 0xffffffff> <auth pap> <magic 0x1cb9f71e> <mrru 1500> >>> <ssnhf> <endpoint [local]>] >>> Feb 13 07:31:44 juan-desktop pppd[4386]: sent [LCP ConfRej id=0xfa <mrru >>> 1500> <ssnhf>] >>> Feb 13 07:31:44 juan-desktop pppd[4386]: rcvd [LCP ConfRej id=0x1 >>> <pcomp> >>> <accomp>] >>> Feb 13 07:31:44 juan-desktop pppd[4386]: sent [LCP ConfReq id=0x2 >>> <asyncmap >>> 0x0> <magic 0xd438a5f>] >>> Feb 13 07:31:45 juan-desktop pppd[4386]: rcvd [LCP ConfReq id=0xfb <mru >>> 1500> <asyncmap 0xffffffff> <auth pap> <magic 0x1cb9baed> <endpoint >>> [local]>] >>> Feb 13 07:31:45 juan-desktop pppd[4386]: sent [LCP ConfAck id=0xfb <mru >>> 1500> <asyncmap 0xffffffff> <auth pap> <magic 0x1cb9baed> <endpoint >>> [local]>] >>> Feb 13 07:31:45 juan-desktop pppd[4386]: rcvd [LCP ConfAck id=0x2 >>> <asyncmap >>> 0x0> <magic 0xd438a5f>] >>> Feb 13 07:31:45 juan-desktop pppd[4386]: sent [LCP EchoReq id=0x0 >>> magic=0xd438a5f] >>> Feb 13 07:31:45 juan-desktop pppd[4386]: sent [PAP AuthReq id=0x1 >>> user="islanis@xxxxxxxxxxxxxx" password=<hidden>] >>> Feb 13 07:31:45 juan-desktop pppd[4386]: rcvd [LCP EchoRep id=0x0 >>> magic=0x1cb9baed] >>> Feb 13 07:31:46 juan-desktop pppd[4386]: rcvd [PAP AuthNak id=0x1 >>> "Auth-Reject from Radius Server."] >>> Feb 13 07:31:46 juan-desktop pppd[4386]: Remote message: Auth-Reject >>> from >>> Radius Server. >>> Feb 13 07:31:46 juan-desktop pppd[4386]: PAP authentication failed >>> Feb 13 07:31:46 juan-desktop pppd[4386]: sent [LCP TermReq id=0x3 >>> "Failed >>> >>> to >>> authenticate ourselves to peer"] >>> Feb 13 07:31:47 juan-desktop pppd[4386]: rcvd [LCP TermAck id=0x3] >>> Feb 13 07:31:47 juan-desktop pppd[4386]: Connection terminated. >>> Feb 13 07:31:47 juan-desktop pppd[4386]: Exit. >>> Feb 13 07:33:34 juan-desktop ntfs-3g[3090]: ntfs_mst_post_read_fixup: >>> Argumento inválido >>> Feb 13 07:33:35 juan-desktop ntfs-3g[3090]: ntfs_mst_post_read_fixup: >>> Argumento inválido >>> >>> /////////////////////////////////////////////////////////////////////////////////////////// >>> and i try to connect again and i got this >>> >>> root@juan-desktop:/home/juan# wvdial Infomed >>> --> WvDial: Internet dialer version 1.60 >>> --> Cannot get information for serial port. >>> --> 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: ATDT060110 >>> --> Waiting for carrier. >>> ATDT060110 >>> CONNECT 52000 >>> --> Carrier detected. Starting PPP immediately. >>> --> Starting pppd at Sat Feb 13 07:57:02 2010 >>> --> Pid of pppd: 5236 >>> --> Using interface ppp0 >>> --> Authentication (PAP) started >>> --> Authentication (PAP) failed (Message: "Auth-Reject from Radius >>> Server." ) >>> --> Terminate Request (Message: "Failed to authenticate ourselves to >>> peer" ) >>> --> Disconnecting at Sat Feb 13 07:57:05 2010 >>> --> Authentication error. >>> --> We failed to authenticate ourselves to the peer. >>> --> Maybe bad account or password? >>> --> Auto Reconnect will be attempted in 5 seconds >>> --> Cannot get information for serial port. >>> --> Initializing modem. >>> --> Sending: ATZ >>> NO CARRIER >>> --> Sending: ATQ0 >>> ATQ0 >>> OK >>> --> Re-Sending: ATZ >>> ATZ >>> OK >>> --> Cannot get information for serial port. >>> --> 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. >>> --> Cannot get information for serial port. >>> --> 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: ATDT060110 >>> --> Waiting for carrier. >>> ATDT060110 >>> ^CCaught signal 2: Attempting to exit gracefully... >>> --> Disconnecting at Sat Feb 13 07:57:21 2010 >>> i am from havana city, more especific from boyeros >>> /////////////////////////////////////////////////////////////////////// >>> the content of chap-secrets from /etc/ppp/chap-secrets is this >>> >>> # Secrets for authentication using CHAP >>> # client server secret IP addresses >>> >>> islanis\@infomed\.sld\.cu * 12 >>> and the content of pap-secrets from /etc/ppp/pap-secrets it this >>> >>> * hostname "" * >>> >>> guest hostname "*" - >>> master hostname "*" - >>> root hostname "*" - >>> support hostname "*" - >>> stats hostname "*" - >>> >>> # * password >>> >>> >>> islanis\@infomed\.sld\.cu * 12 >>> >>> >>> ///////////////////////////////////////////////////////// >>> and de mydebug.txt comes in adjunt >>> >>> >>> >>> >>> >>> >>> ----- Original Message ----- >>> From: "Antonio Olivares" <olivares14031@xxxxxxxxx> >>> To: "Jacques Goldberg" <Jacques.Goldberg@xxxxxxx> >>> Cc: "islanis" <islanis@xxxxxxxxxxxxxx>; <discuss@xxxxxxxxxxxxx>; "Marvin >>> Stodolsky" <marvin.stodolsky@xxxxxxxxx> >>> Sent: Sunday, February 14, 2010 2:04 PM >>> Subject: Re: help motorola sm56 is not conecting >>> >>> >>> Jacques, >>> >>> I am copying item 13 here: >>> >>> failed to authenticate? verify that there is no matching entry in >>> /etc/ppp/chap-secrets. If you see your username and password in that >>> file, comment the line with a leading # and retry. Warning: wvdial >>> version 1.40 creates the line again, so use a more recent version. >>> Note: some ISP servers use a copyrighted encryption algorithm for chap >>> authentication, not supported by Linux pppd (at this time, at least). >>> >>> and translating to Spanish so that Juan can understand: >>> >>> Juan hemos fallado en autenticarnos al ISP(informed.sld.cu). >>> Necessitas ver el archivo /etc/ppp/chap-secrets. Si miras tu nombre >>> de usuario: islanis o islanis@xxxxxxxxxxxxxx y tu clave que usas >>> para conectarte. Trata de editar este archivo, como >>> $ sudo gedit /etc/ppp/chap-secrets >>> y ponerle un "#" antes del nombre de tu usuario y la clave y trata de >>> conectarte otra vez. Si tienes wvdial version 1.40, esta version >>> vuelve a poner el nombre del usuario y tu clave para autenticarte ante >>> tu ISP. Por ejemplo aqui esta el mio nomas para que mires como se ve: >>> >>> [root@localhost ~]# cat /etc/ppp/chap-secrets >>> # Secrets for authentication using CHAP >>> # client server secret IP addresses >>> mi-nombre-de-usuario 0 ********* >>> >>> >>> nomas que puse para username: mi-nombre-de-usuario y la clave puse >>> ********, tu tambien puedes hacer lo mismo. >>> >>> Jaques te recomienda que agreges la palabra "debug" al archivo >>> /etc/ppp/options, usa >>> $ sudo gedit /etc/ppp/options >>> >>> y poner la palabra debug en donde sea: >>> >>> add a line debug in /etc/ppp/options if not already there. >>> >>> en el archivo mio tengo "lock": >>> >>> [root@localhost ~]# cat /etc/ppp/options >>> lock >>> >>> Depues de hacer esto, Juan hay que hacer tres cosas mas, y se necesita >>> que sigas los consejos dados por Jacques para ver si se puede corregir >>> esta dificultad que tu tienes: >>> >>> English/Ingles >>> 1 open an additional window as root or su >>> 2 in this window enter tail -f /var/log/messages | tee mydebug.txt >>> 3 return to first window and start wvdial >>> >>> Spanish/Español >>> 1 abrir una ventana adicional como root o su , en caso de usted sudo >>> 2 en la ventana nueva/tab nueva poner lo siguiente >>> $ sudo tail -f /var/log/messages | tee mydebug.txt >>> 3 regrasar ala primer ventana/session y empezar wvdial >>> >>> Cuando wvdial termine y te de lo mismo que te ha dado, envianos el >>> archivo mydebug.txt para ver que esta sucediendo. >>> >>> =================== >>> >>> Antonio: perhaps some time can be saved by asking the ISP if they use >>> pap or chap secrets. >>> >>> Also it may be necessasry to check if the version of pppd used by >>> Juan is compiled for chap-secrets . I have not followed that since >>> long and I do not know if ms-chap is still copyrighted and then must >>> be worked around. >>> >>> Jacques: The ISP is not getting back to me, they have sent me back my >>> mails >>> :( >>> >>> Delivery to the following recipient failed permanently: >>> >>> problemas@xxxxxxxxxxxxxx >>> >>> Technical details of permanent failure: >>> Google tried to deliver your message, but it was rejected by the >>> recipient domain. We recommend contacting the other email provider for >>> further information about the cause of this error. The error that the >>> other server returned was: 550 550 Access denied (state 17). >>> >>> ----- Original message ----- >>> >>> MIME-Version: 1.0 >>> Received: by 10.216.88.202 with SMTP id >>> a52mr2163963wef.101.1266121826697; >>> Sat, 13 Feb 2010 20:30:26 -0800 (PST) >>> In-Reply-To: <eventum.1m5xkw7j.old6oh@xxxxxxxxxxxxxx> >>> References: <27F168F0D6EC4534859E3B1ED69F5F54@ale> >>> <eventum.1m5xkw7j.old6oh@xxxxxxxxxxxxxx> >>> Date: Sat, 13 Feb 2010 22:30:26 -0600 >>> Message-ID: >>> <75107331002132030o2c0473a7y8dc0df3769035037@xxxxxxxxxxxxxx> >>> Subject: Re: [#3099] Issue Created: Re: help motorola sm56 is not >>> conecting >>> From: Antonio Olivares <olivares14031@xxxxxxxxx> >>> To: "problemas@xxxxxxxxxxxxxx" <problemas@xxxxxxxxxxxxxx> >>> Cc: islanis <islanis@xxxxxxxxxxxxxx> >>> Content-Type: text/plain; charset=ISO-8859-1 >>> Content-Transfer-Encoding: quoted-printable >>> >>> ========================= >>> >>> >>> Juan, >>> >>> ya cambiaste el wvdial y te sigue dando lo mismo. Cambiaste el telefono >>> de >>> 061110 a 0160110? >>> >>> Note que la única diferencia al acceder por la plataforma ya sea por >>> el 0160110 desde cualquier provincia o por el 060110 desde Ciudad de >>> La Habana consiste en que debe poner su dirección de correo >>> electrónico de la forma siguiente: juanperez@xxxxxxxxxxxxxx >>> >>> tambien como Jaques te dijo, en un wvdial.conf tenias Informed, >>> Informed2, con dos diferentes versiones uno con >>> usuario islandis y otro con usuario islandis@xxxxxxxxxxxxxxx >>> >>> Usa el mismo que usas con Windows, y si todo sale bien lograras >>> conectarte con Ubuntu ala red. La clave tambien tiene que ser la >>> misma. Es dificil para nosotros saber si vives en provincia o Havana >>> para poder decirte con seguridad si debes usar el numero 06110 o el >>> otro numero 0161110 . >>> >>> Ojala que te puedas conectar, si no envianos el archivo mydebug.txt, y >>> luego Jacques/Marv/u otro usuario nos avisara como proceder. >>> >>> Attentamente/Regards, >>> >>> Antonio >>> >>> >>> >>> On 2/14/10, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: >>> >>>> Juan, at this place, first of all, clearly your modem technically works >>>> fine. >>>> >>>> No more problem with the driver. >>>> >>>> Debugging the authentication is not trivial. >>>> >>>> >>>> Antonio, please continue your kind help to Juan in Spanish. In the name >>>> of all of us, I thank you very much. >>>> >>>> >>>> The problem is discussed in item 13 of section TROUBLESHOOTING at >>>> http://linmodems.technion.ac.il/post-install.html >>>> >>>> The debugging goes as follows: >>>> >>>> >>>> Follow section FOR THE IMPATIENT in the same Web page, always as root >>>> (with sudo if Ubuntu, or after su ): >>>> >>>> Execute item 10 (inserting debug in file /etc/ppp/options : >>>> one line anywhere with the word debug >>>> >>>> Jump to executing steps 13, 14, 15 >>>> >>>> After seeing --> The PPP daemon has died. (exit code = 19) >>>> in the window where wvdial has worked, kill the tail command in >>>> the >>>> window where it is running, using CTRL-C >>>> >>>> Send us the file mydebug.txt >>>> >>>> With that file, using the SECOND link in item 13 of section >>>> TROUBLESHOOTING, the reason why authentication fails can be found. As >>>> item 13 suggests, it is very likely that the problem comes from >>>> incorrect pap-secrets & chap-secrets. >>>> >>>> >>>> Antonio: perhaps some time can be saved by asking the ISP if they use >>>> pap or chap secrets. >>>> >>>> Also it may be necessasry to check if the version of pppd used by Juan >>>> is compiled for chap-secrets . I have not followed that since long and >>>> I do not know if ms-chap is still copyrighted and then must be worked >>>> around. >>>> >>>> >>>> Good luck >>>> >>>> Jacques >>>> >>>> >>>> >>>> islanis wrote: >>>> >>>> >>>>> i made this antonio >>>>> >>>>> [Dialer defaults] >>>>> Init1 = ATZ >>>>> Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>>>> Modem Type = Analog >>>>> Baud = 460800 >>>>> Modem = /dev/ttySL0 >>>>> ISDN = 0 >>>>> Phone = 060110 >>>>> Password = 12 >>>>> Username = islanis@xxxxxxxxxxxxxx >>>>> Carrier Check = no >>>>> #Stupid Mode = yes >>>>> >>>>> and it return this: >>>>> >>>>> root@juan-desktop:/home/juan# wvdial >>>>> --> WvDial: Internet dialer version 1.60 >>>>> --> Cannot get information for serial port. >>>>> --> Initializing modem. >>>>> --> Sending: ATZ >>>>> ATZ >>>>> OK >>>>> --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>>>> ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>>>> OK >>>>> --> Modem initialized. >>>>> --> Sending: ATDT060110 >>>>> --> Waiting for carrier. >>>>> ATDT060110 >>>>> CONNECT 50667 >>>>> --> Carrier detected. Waiting for prompt. >>>>> ************************************************ >>>>> * Product Name :Quidway A8010; * >>>>> * Product Provider:HuaWei; * >>>>> * Internet Server :######; * >>>>> ************************************************ >>>>> Welcome to INTERNET! >>>>> Please input username: >>>>> --> Looks like a login prompt. >>>>> --> Sending: islanis@xxxxxxxxxxxxxx >>>>> Please input password: >>>>> --> Looks like a password prompt. >>>>> --> Sending: (password) >>>>> ********************** >>>>> Can't contact authentication server. >>>>> Authentication failed! >>>>> Please input username: >>>>> --> Looks like a login prompt. >>>>> --> Sending: islanis@xxxxxxxxxxxxxx >>>>> islanis@xxxxxxxxxxxxxx >>>>> Please input password: >>>>> --> Looks like a password prompt. >>>>> --> Sending: (password) >>>>> ** >>>>> Auth-Reject from Radius Server. >>>>> Authentication failed! >>>>> Please input username: >>>>> --> Looks like a login prompt. >>>>> --> Sending: islanis@xxxxxxxxxxxxxx >>>>> --> Don't know what to do! Starting pppd and hoping for the best. >>>>> --> Starting pppd at Fri Feb 12 21:06:45 2010 >>>>> --> Pid of pppd: 3187 >>>>> --> Using interface ppp0 >>>>> --> pppd: ?!2[08]?!2[08]X 2[08] >>>>> --> pppd: ?!2[08]?!2[08]X 2[08] >>>>> --> pppd: ?!2[08]?!2[08]X 2[08] >>>>> --> pppd: ?!2[08]?!2[08]X 2[08] >>>>> --> pppd: ?!2[08]?!2[08]X 2[08] >>>>> --> Disconnecting at Fri Feb 12 21:06:49 2010 >>>>> --> The PPP daemon has died: Authentication error. >>>>> --> We failed to authenticate ourselves to the peer. >>>>> --> Maybe bad account or password? (exit code = 19) >>>>> --> man pppd explains pppd error codes in more detail. >>>>> --> I guess that's it for now, exiting >>>>> --> The PPP daemon has died. (exit code = 19) >>>>> >>>>> and with Stupid Mode = yes >>>>> i got this: >>>>> root@juan-desktop:/home/juan# wvdial >>>>> --> WvDial: Internet dialer version 1.60 >>>>> --> Cannot get information for serial port. >>>>> --> Initializing modem. >>>>> --> Sending: ATZ >>>>> ATZ >>>>> OK >>>>> --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>>>> ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>>>> OK >>>>> --> Modem initialized. >>>>> --> Sending: ATDT060110 >>>>> --> Waiting for carrier. >>>>> ATDT060110 >>>>> CONNECT 52000 >>>>> --> Carrier detected. Starting PPP immediately. >>>>> --> Starting pppd at Fri Feb 12 21:09:22 2010 >>>>> --> Pid of pppd: 3203 >>>>> --> Using interface ppp0 >>>>> --> pppd: ?1?[08]X1?[08][08]0?[08] >>>>> --> pppd: ?1?[08]X1?[08][08]0?[08] >>>>> --> pppd: ?1?[08]X1?[08][08]0?[08] >>>>> --> pppd: ?1?[08]X1?[08][08]0?[08] >>>>> --> pppd: ?1?[08]X1?[08][08]0?[08] >>>>> --> Disconnecting at Fri Feb 12 21:09:28 2010 >>>>> --> The PPP daemon has died: Authentication error. >>>>> --> We failed to authenticate ourselves to the peer. >>>>> --> Maybe bad account or password? (exit code = 19) >>>>> --> man pppd explains pppd error codes in more detail. >>>>> --> I guess that's it for now, exiting >>>>> --> The PPP daemon has died. (exit code = 19) >>>>> >>>>> what else..pls >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ----- Original Message ----- >>>>> From: "Antonio Olivares" <olivares14031@xxxxxxxxx> >>>>> To: "islanis" <islanis@xxxxxxxxxxxxxx> >>>>> Cc: <discuss@xxxxxxxxxxxxx>; "Marvin Stodolsky" >>>>> <marvin.stodolsky@xxxxxxxxx>; <problemas@xxxxxxxxxxxxxx> >>>>> Sent: Sunday, February 14, 2010 5:41 AM >>>>> Subject: Re: help motorola sm56 is not conecting >>>>> >>>>> >>>>> Juan, Marv, Jacques, et. all, >>>>> >>>>> I have made contact with the ISP which Juan uses to see how this >>>>> problem can be resolved. Upon looking at the requirements, I have >>>>> made some recommendations to Juan (modifying his wvdial.conf file) and >>>>> see if he can connect with them or not? I wrote the instructions in >>>>> Spanish so Juan should not have difficulties. I hope this helps in >>>>> some way. >>>>> >>>>> Me he communicado via electronica con informed.sld para ver si te algo >>>>> se puede modificar para que puedas lograr una coneccion con Linux. Yo >>>>> hara los siguientes cambios. Cambiara el archivo /etc/wvdial.conf >>>>> >>>>> de lo que nos enviaste >>>>> >>>>> [Dialer Infomed] >>>>> Init1 = ATZ >>>>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>>> Modem Type = Analog >>>>> Baud = 460800 >>>>> New PPPD = yes >>>>> Modem = /dev/ttySL0 >>>>> ISDN = 0 >>>>> Phone = 060110 >>>>> Password = 12 >>>>> Username = islanis@xxxxxxxxxxxxxx >>>>> #Stupid Mode = yes >>>>> Password Prompt = 12 >>>>> Carrier Check = no >>>>> >>>>> [Dialer Infomed1] >>>>> Init1 = ATZ >>>>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>>> Modem Type = Analog >>>>> Baud = 460800 >>>>> New PPPD = yes >>>>> Modem = /dev/ttySL0 >>>>> ISDN = 0 >>>>> Phone = 8314949 >>>>> Password = 12 >>>>> Username = islanis >>>>> #Stupid Mode = yes >>>>> Password Prompt = 12 >>>>> Carrier Check = no >>>>> >>>>> >>>>> >>>>> a >>>>> >>>>> [Dialer defaults] >>>>> Init1 = ATZ >>>>> Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>>>> Modem Type = Analog >>>>> Baud = 460800 >>>>> Modem = /dev/ttySL0 >>>>> ISDN = 0 >>>>> Phone = 060110 >>>>> Password = 12 >>>>> Username = islanis@xxxxxxxxxxxxxx >>>>> Carrier Check = no >>>>> #Stupid Mode = yes >>>>> >>>>> pero antes de hacer los cambios haz lo siguiente. >>>>> $ sudo cp /etc/wvdial.conf /etc/wvdial.old >>>>> y haces las modificaciones y tratas de connectarte. Si no funciona, >>>>> cambias el numero de >>>>> >>>>> 060110 >>>>> >>>>> a >>>>> >>>>> 060110 >>>>> >>>>> porque el nombre de usuario(username) esta correcto. Esto es lo que >>>>> exije informed.sld.cu: >>>>> >>>>> Excepciones del proxy: *.sld.cu >>>>> Note que la única diferencia al acceder por la plataforma ya sea >>>>> por >>>>> el 0160110 desde cualquier provincia o por el 060110 desde Ciudad de >>>>> La Habana consiste en que debe poner su dirección de correo >>>>> electrónico de la forma siguiente: juanperez@xxxxxxxxxxxxxx >>>>> >>>>> Trata de hacer estos cambios y dejanos saber si funciona o no? >>>>> >>>>> De no funcionar trata de eliminar el "#" de Stupid Mode = yes y tratar >>>>> asi y haber si te puedes connectar? >>>>> >>>>> >>>>> Attentamente/Regards, >>>>> >>>>> Antonio >>>>> >>>>> >>>>> >>>>> >>>>> On 2/12/10, islanis <islanis@xxxxxxxxxxxxxx> wrote: >>>>> >>>>> >>>>>> i cant conect yet please help >>>>>> ----- Original Message ----- >>>>>> From: "Antonio Olivares" <olivares14031@xxxxxxxxx> >>>>>> To: <discuss@xxxxxxxxxxxxx> >>>>>> Cc: "islanis" <islanis@xxxxxxxxxxxxxx>; "Marvin Stodolsky" >>>>>> <marvin.stodolsky@xxxxxxxxx>; <problemas@xxxxxxxxxxxxxx> >>>>>> Sent: Saturday, February 13, 2010 8:03 PM >>>>>> Subject: Re: help motorola sm56 is not conecting >>>>>> >>>>>> >>>>>> Jacques, Juan, Marv & et all >>>>>> >>>>>> I can help translate a bit if it is needed as I have added a cc: to >>>>>> problemas@xxxxxxxxxxxxxxx which is the ISP. >>>>>> >>>>>> I am asking politely to the ISP informed.sld.cu for help/requirements >>>>>> to try and help out Juan get his connection working using Linux. I >>>>>> am >>>>>> asking for basic requirements like password, username and phone no. >>>>>> Upon getting some information, I will relay back to Juan & list and >>>>>> see how we can help diagnoze his difficulties. >>>>>> >>>>>> Estimados amigos del a red informed.sld.cu. El usuario Juan se puede >>>>>> connectar con Windows, pero tiene dificultades para conectarse con >>>>>> Linux. Si hay requiremientos para poder tener asesso ala red, que >>>>>> tiene que tener? >>>>>> >>>>>> Por ejemplo: >>>>>> >>>>>> >>>>>> Username = islanis@xxxxxxxxxxxxxx >>>>>> Password = 12 >>>>>> Phone = 060110 >>>>>> >>>>>> o el nombre del usuario >>>>>> Username = islanis >>>>>> ? >>>>>> >>>>>> la clave(password) debe ser igual que la que tiene en windows? >>>>>> Password = 12 >>>>>> Phone = 060110 >>>>>> >>>>>> y el telefono que este igual tambien que en windows. >>>>>> >>>>>> Nomas queremos saber que es lo que se exije para poder ayuadar a Juan >>>>>> poder conectarse al internet con Linux. No es ninguna queja formal >>>>>> ni >>>>>> mucho menos. >>>>>> >>>>>> Gracias por ayudar. >>>>>> >>>>>> Attentamente, >>>>>> >>>>>> Antonio Olivares >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 2/13/10, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: >>>>>> >>>>>> >>>>>>> In your file wvdial.conf there are two sections named Infomed and >>>>>>> Infomed1 >>>>>>> >>>>>>> In Infomed the username is islanis@xxxxxxxxxxxxxx coupled to the >>>>>>> phone >>>>>>> number 060110 >>>>>>> >>>>>>> This is the section which you used in your attempt to connect. >>>>>>> >>>>>>> Then you have a section Infomed1 where the username is islanis , not >>>>>>> the >>>>>>> same (only islanis, not your complete email address). >>>>>>> >>>>>>> Are you sure that the one which you use (islanis@xxxxxxxxxxxxxx) is >>>>>>> the >>>>>>> correct one which Infomed has given to you? >>>>>>> >>>>>>> Also the password which you use, 12 , is a bit strange: usually >>>>>>> the >>>>>>> ISP (your ISP is Infomed) give a more sophisticated password not so >>>>>>> simple, >>>>>>> >>>>>>> Furthermore the password promt is strange: who told you to have a >>>>>>> Password Prompt line like that ? Infomed? >>>>>>> >>>>>>> The command Password Prompt is for use in the very infrequent cases >>>>>>> when, when asking for your password, the ISP does not ask something >>>>>>> like password? or password: or the same with login in place of >>>>>>> password or longer lines of text including one of the words login, >>>>>>> logon, or password. Of course, if Infomed uses a Spanish word it >>>>>>> might >>>>>>> be a reason to use Password Prompt. I have looked into >>>>>>> http://www.infomed.sld.cu hoping to find the answer myself but I do >>>>>>> not >>>>>>> understand Spanish and I did not see anything which could be related >>>>>>> to >>>>>>> the use of a modem. >>>>>>> >>>>>>> >>>>>>> >>>>>>> The most probable cuase of your failure is still that you do not >>>>>>> need >>>>>>> the line Password Prompt (which perrhaps changes nothing to the >>>>>>> failure) >>>>>>> and either the Username or the Password or both as reported in >>>>>>> section >>>>>>> Infomed of your file are incorrect. If you are not 100% sure, ask >>>>>>> Infomed >>>>>>> ! >>>>>>> >>>>>>> >>>>>>> Jacques >>>>>>> >>>>>>> >>>>>>> islanis wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> these are my wvdial.conf >>>>>>>> >>>>>>>> [Dialer Infomed] >>>>>>>> Init1 = ATZ >>>>>>>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>>>>>> Modem Type = Analog >>>>>>>> Baud = 460800 >>>>>>>> New PPPD = yes >>>>>>>> Modem = /dev/ttySL0 >>>>>>>> ISDN = 0 >>>>>>>> Phone = 060110 >>>>>>>> Password = 12 >>>>>>>> Username = islanis@xxxxxxxxxxxxxx >>>>>>>> #Stupid Mode = yes >>>>>>>> Password Prompt = 12 >>>>>>>> Carrier Check = no >>>>>>>> >>>>>>>> [Dialer Infomed1] >>>>>>>> Init1 = ATZ >>>>>>>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>>>>>> Modem Type = Analog >>>>>>>> Baud = 460800 >>>>>>>> New PPPD = yes >>>>>>>> Modem = /dev/ttySL0 >>>>>>>> ISDN = 0 >>>>>>>> Phone = 8314949 >>>>>>>> Password = 12 >>>>>>>> Username = islanis >>>>>>>> #Stupid Mode = yes >>>>>>>> Password Prompt = 12 >>>>>>>> Carrier Check = no >>>>>>>> >>>>>>>> and this is what i got with one and woth the other and nothing >>>>>>>> >>>>>>>> with the first >>>>>>>> >>>>>>>> root@juan-desktop:/home/juan# wvdial infomed >>>>>>>> --> WvDial: Internet dialer version 1.60 >>>>>>>> --> Cannot get information for serial port. >>>>>>>> --> 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: ATDT060110 >>>>>>>> --> Waiting for carrier. >>>>>>>> ATDT060110 >>>>>>>> CONNECT 52000 >>>>>>>> --> Carrier detected. Waiting for prompt. >>>>>>>> ************************************************ >>>>>>>> * Product Name :Quidway A8010; * >>>>>>>> * Product Provider:HuaWei; * >>>>>>>> * Internet Server :######; * >>>>>>>> ************************************************ >>>>>>>> Welcome to INTERNET! >>>>>>>> Please input username: >>>>>>>> --> Looks like a login prompt. >>>>>>>> --> Sending: islanis@xxxxxxxxxxxxxx >>>>>>>> Please input password: >>>>>>>> --> Looks like a password prompt. >>>>>>>> --> Sending: (password) >>>>>>>> ********************** >>>>>>>> Can't contact authentication server. >>>>>>>> Authentication failed! >>>>>>>> Please input username: >>>>>>>> --> Looks like a login prompt. >>>>>>>> --> Sending: islanis@xxxxxxxxxxxxxx >>>>>>>> islanis@xxxxxxxxxxxxxx >>>>>>>> Please input password: >>>>>>>> --> Looks like a password prompt. >>>>>>>> --> Sending: (password) >>>>>>>> ** >>>>>>>> Auth-Reject from Radius Server. >>>>>>>> Authentication failed! >>>>>>>> Please input username: >>>>>>>> --> Looks like a login prompt. >>>>>>>> --> Sending: islanis@xxxxxxxxxxxxxx >>>>>>>> --> Don't know what to do! Starting pppd and hoping for the best. >>>>>>>> --> Starting pppd at Thu Feb 11 18:35:26 2010 >>>>>>>> --> Pid of pppd: 3250 >>>>>>>> --> Using interface ppp0 >>>>>>>> --> pppd: ??) ?) ?) >>>>>>>> --> pppd: ??) ?) ?) >>>>>>>> --> pppd: ??) ?) ?) >>>>>>>> --> pppd: ??) ?) ?) >>>>>>>> --> pppd: ??) ?) ?) >>>>>>>> --> Disconnecting at Thu Feb 11 18:35:28 2010 >>>>>>>> --> The PPP daemon has died: Authentication error. >>>>>>>> --> We failed to authenticate ourselves to the peer. >>>>>>>> --> Maybe bad account or password? (exit code = 19) >>>>>>>> --> man pppd explains pppd error codes in more detail. >>>>>>>> --> I guess that's it for now, exiting >>>>>>>> --> The PPP daemon has died. (exit code = 19) >>>>>>>> >>>>>>>> and with the second >>>>>>>> >>>>>>>> >>>>>>>> root@juan-desktop:/home/juan# wvdial infomed1 >>>>>>>> --> WvDial: Internet dialer version 1.60 >>>>>>>> --> Cannot get information for serial port. >>>>>>>> --> 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: ATDT8314949 >>>>>>>> --> Waiting for carrier. >>>>>>>> ATDT8314949 >>>>>>>> BUSY >>>>>>>> --> The line is busy. Trying again. >>>>>>>> --> Sending: ATDT8314949 >>>>>>>> --> Waiting for carrier. >>>>>>>> ATDT8314949 >>>>>>>> BUSY >>>>>>>> --> The line is busy. Trying again. >>>>>>>> --> Sending: ATDT8314949 >>>>>>>> --> Waiting for carrier. >>>>>>>> ATDT8314949 >>>>>>>> BUSY >>>>>>>> --> The line is busy. Trying again. >>>>>>>> --> Sending: ATDT8314949 >>>>>>>> --> Waiting for carrier. >>>>>>>> ATDT8314949 >>>>>>>> ^CCaught signal 2: Attempting to exit gracefully... >>>>>>>> --> Disconnecting at Thu Feb 11 18:37:24 2010 >>>>>>>> >>>>>>>> and nothing,,,, >>>>>>>> helpppp, what else >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ----- Original Message ----- >>>>>>>> From: "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx> >>>>>>>> To: "islanis" <islanis@xxxxxxxxxxxxxx> >>>>>>>> Cc: <discuss@xxxxxxxxxxxxx> >>>>>>>> Sent: Saturday, February 13, 2010 1:33 AM >>>>>>>> Subject: Re: help motorola sm56 is not conecting >>>>>>>> >>>>>>>> >>>>>>>> Juan >>>>>>>> >>>>>>>> Good progress. The problem is now one of logon protocol >>>>>>>> RE: --> Carrier detected. Starting PPP immediately. >>>>>>>> Please make sure that >>>>>>>> Stupid Mode = on >>>>>>>> is not active. It can be inactivated by preceding it with a #, as >>>>>>>> in: >>>>>>>> # Stupid Mode = on >>>>>>>> >>>>>>>> Starting PPP immediately. >>>>>>>> indicates that logon and password on not being sent, so >>>>>>>> --> The PPP daemon has died: Authentication error. >>>>>>>> --> We failed to authenticate ourselves to the peer. >>>>>>>> >>>>>>>> MarvS >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Feb 10, 2010 at 11:20 PM, islanis <islanis@xxxxxxxxxxxxxx> >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> hey marv look at this i a changed my ISP number to another number >>>>>>>>> but >>>>>>>>> the >>>>>>>>> same ISP and i got this >>>>>>>>> >>>>>>>>> >>>>>>>>> almost but nothing >>>>>>>>> >>>>>>>>> >>>>>>>>> root@juan-desktop:/home/juan# wvdial >>>>>>>>> --> WvDial: Internet dialer version 1.60 >>>>>>>>> --> Cannot get information for serial port. >>>>>>>>> --> 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: ATDT060110 >>>>>>>>> --> Waiting for carrier. >>>>>>>>> ATDT060110 >>>>>>>>> CONNECT 50667 >>>>>>>>> --> Carrier detected. Starting PPP immediately. >>>>>>>>> --> Starting pppd at Wed Feb 10 20:06:18 2010 >>>>>>>>> --> Pid of pppd: 3425 >>>>>>>>> --> Using interface ppp0 >>>>>>>>> --> pppd: ??C[08]@?C[08][18]?C[08] >>>>>>>>> --> pppd: ??C[08]@?C[08][18]?C[08] >>>>>>>>> --> pppd: ??C[08]@?C[08][18]?C[08] >>>>>>>>> --> pppd: ??C[08]@?C[08][18]?C[08] >>>>>>>>> --> pppd: ??C[08]@?C[08][18]?C[08] >>>>>>>>> --> Disconnecting at Wed Feb 10 20:06:21 2010 >>>>>>>>> --> The PPP daemon has died: Authentication error. >>>>>>>>> --> We failed to authenticate ourselves to the peer. >>>>>>>>> --> Maybe bad account or password? (exit code = 19) >>>>>>>>> --> man pppd explains pppd error codes in more detail. >>>>>>>>> --> I guess that's it for now, exiting >>>>>>>>> --> The PPP daemon has died. (exit code = 19) >>>>>>>>> >>>>>>>>> ----- Original Message ----- >>>>>>>>> From: "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx> >>>>>>>>> To: "Juan Alejandro Martinez Linares" <islanis@xxxxxxxxxxxxxx> >>>>>>>>> Cc: <discuss@xxxxxxxxxxxxx> >>>>>>>>> Sent: Thursday, February 11, 2010 2:35 PM >>>>>>>>> Subject: Re: help motorola sm56 is not conecting >>>>>>>>> >>>>>>>>> >>>>>>>>> Many (but not all) modem users are having this problem of the >>>>>>>>> specification >>>>>>>>> Carrier Check = no >>>>>>>>> seems to be ignored. >>>>>>>>> >>>>>>>>> Today I should be able to get home through some 20 miles of >>>>>>>>> Washington >>>>>>>>> area snow drifts, after 3 days stuck at a convention center, which >>>>>>>>> is >>>>>>>>> usually only a 30 minute drive away. >>>>>>>>> >>>>>>>>> At home I will compile a variant of wvdial, >>>>>>>>> with default changed to >>>>>>>>> Carrier Check = no >>>>>>>>> Then those of you having problem can test it. >>>>>>>>> >>>>>>>>> MarvS >>>>>>>>> >>>>>>>>> On Thu, Feb 11, 2010 at 8:26 AM, Juan Alejandro Martinez Linares >>>>>>>>> <islanis@xxxxxxxxxxxxxx> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> one thing ,,i have omited one thing,, it dial only the 4 first >>>>>>>>>> numbers >>>>>>>>>> of >>>>>>>>>> the telephone >>>>>>>>>> number of my provider,, i heard it always the only 4 numbers ,, >>>>>>>>>> IE >>>>>>>>>> 8314 >>>>>>>>>> of >>>>>>>>>> 8314949, >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Mensaje citado por Antonio Olivares <olivares14031@xxxxxxxxx>: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Juan, >>>>>>>>>>> >>>>>>>>>>> If you have a telephone, can you verify that the line is not >>>>>>>>>>> busy? >>>>>>>>>>> It >>>>>>>>>>> might be ISP problem here? >>>>>>>>>>> >>>>>>>>>>> Si levantas el telefono, suena ocupado? Si no es probablemente >>>>>>>>>>> un >>>>>>>>>>> problema con la red y tu provedor de Internet? >>>>>>>>>>> >>>>>>>>>>> Regards/Saludos, >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Antonio >>>>>>>>>>> >>>>>>>>>>> On 2/10/10, Juan Alejandro Martinez Linares >>>>>>>>>>> <islanis@xxxxxxxxxxxxxx> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> i did this >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >>>>>>>>>>>> Stupid Mode = on >>>>>>>>>>>> Auto DNS = off >>>>>>>>>>>> to >>>>>>>>>>>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +MS=34 >>>>>>>>>>>> # Stupid Mode = on >>>>>>>>>>>> Idle Seconds = 12 >>>>>>>>>>>> Auto DNS = on >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> and it sais this >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> root@juan-desktop:/home/juan# wvdial infomed3 >>>>>>>>>>>> --> WvDial: Internet dialer version 1.60 >>>>>>>>>>>> --> Cannot get information for serial port. >>>>>>>>>>>> --> Initializing modem. >>>>>>>>>>>> --> Sending: ATZ >>>>>>>>>>>> ATZ >>>>>>>>>>>> OK >>>>>>>>>>>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +MS=34 >>>>>>>>>>>> ATQ0 V1 E1 S0=0 &C1 &D2 +MS=34 >>>>>>>>>>>> OK >>>>>>>>>>>> --> Modem initialized. >>>>>>>>>>>> --> Idle Seconds = 12, disabling automatic reconnect. >>>>>>>>>>>> --> Sending: ATDT8314949 >>>>>>>>>>>> --> Waiting for carrier. >>>>>>>>>>>> ATDT8314949 >>>>>>>>>>>> BUSY >>>>>>>>>>>> --> The line is busy. Trying again. >>>>>>>>>>>> --> Sending: ATDT8314949 >>>>>>>>>>>> --> Waiting for carrier. >>>>>>>>>>>> ATDT8314949 >>>>>>>>>>>> BUSY >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> what else >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------ >>>>>>>>>>>> Infomed - Red de Salud de Cuba >>>>>>>>>>>> http://www.sld.cu/ >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>>>>> Este mensaje le ha llegado mediante el servicio de correo >>>>>>>>>>>> electronico >>>>>>>>>>>> que >>>>>>>>>>>> ofrece Infomed para respaldar el cumplimiento de las misiones >>>>>>>>>>>> del >>>>>>>>>>>> Sistema >>>>>>>>>>>> Nacional de Salud. La persona que envia este correo asume el >>>>>>>>>>>> compromiso >>>>>>>>>>>> de >>>>>>>>>>>> usar el servicio a tales fines y cumplir con las regulaciones >>>>>>>>>>>> establecidas >>>>>>>>>>>> >>>>>>>>>>>> Infomed: http://www.sld.cu/ >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> ------------------------------ >>>>>>>>>> Infomed - Red de Salud de Cuba >>>>>>>>>> http://www.sld.cu/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> Este mensaje le ha llegado mediante el servicio de correo >>>>>>>>>> electronico >>>>>>>>>> que >>>>>>>>>> ofrece Infomed para respaldar el cumplimiento de las misiones del >>>>>>>>>> Sistema >>>>>>>>>> Nacional de Salud. La persona que envia este correo asume el >>>>>>>>>> compromiso >>>>>>>>>> de >>>>>>>>>> usar el servicio a tales fines y cumplir con las regulaciones >>>>>>>>>> establecidas >>>>>>>>>> >>>>>>>>>> Infomed: http://www.sld.cu/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> __________ Informacin de ESET Smart Security, versin de la base de >>>>>>>>> firmas >>>>>>>>> >>>>>>>>> de >>>>>>>>> virus 4804 (20100125) __________ >>>>>>>>> >>>>>>>>> ESET Smart Security ha comprobado este mensaje. >>>>>>>>> >>>>>>>>> http://www.eset.com >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> __________ Información de ESET Smart Security, versión de la base >>>>>>>>> de >>>>>>>>> firmas de virus 4804 (20100125) __________ >>>>>>>>> >>>>>>>>> ESET Smart Security ha comprobado este mensaje. >>>>>>>>> >>>>>>>>> http://www.eset.com >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> Este mensaje le ha llegado mediante el servicio de correo >>>>>>>>> electronico >>>>>>>>> que >>>>>>>>> >>>>>>>>> ofrece Infomed para respaldar el cumplimiento de las misiones del >>>>>>>>> Sistema >>>>>>>>> >>>>>>>>> Nacional de Salud. La persona que envia este correo asume el >>>>>>>>> compromiso >>>>>>>>> de >>>>>>>>> usar el servicio a tales fines y cumplir con las regulaciones >>>>>>>>> establecidas >>>>>>>>> >>>>>>>>> Infomed: http://www.sld.cu/ >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> __________ Informacin de ESET Smart Security, versin de la base de >>>>>>>> firmas >>>>>>>> de >>>>>>>> virus 4804 (20100125) __________ >>>>>>>> >>>>>>>> ESET Smart Security ha comprobado este mensaje. >>>>>>>> >>>>>>>> http://www.eset.com >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> __________ Información de ESET Smart Security, versión de la base >>>>>>>> de >>>>>>>> firmas de virus 4804 (20100125) __________ >>>>>>>> >>>>>>>> ESET Smart Security ha comprobado este mensaje. >>>>>>>> >>>>>>>> http://www.eset.com >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Este mensaje le ha llegado mediante el servicio de correo >>>>>>>> electronico >>>>>>>> que >>>>>>>> ofrece Infomed para respaldar el cumplimiento de las misiones del >>>>>>>> Sistema >>>>>>>> Nacional de Salud. La persona que envia este correo asume el >>>>>>>> compromiso >>>>>>>> de >>>>>>>> usar el servicio a tales fines y cumplir con las regulaciones >>>>>>>> establecidas >>>>>>>> >>>>>>>> Infomed: http://www.sld.cu/ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>> __________ Información de ESET Smart Security, versión de la base de >>>>>> firmas >>>>>> de virus 4804 (20100125) __________ >>>>>> >>>>>> ESET Smart Security ha comprobado este mensaje. >>>>>> >>>>>> http://www.eset.com >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> __________ Información de ESET Smart Security, versión de la base de >>>>>> firmas >>>>>> de virus 4804 (20100125) __________ >>>>>> >>>>>> ESET Smart Security ha comprobado este mensaje. >>>>>> >>>>>> http://www.eset.com >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Este mensaje le ha llegado mediante el servicio de correo electronico >>>>>> que >>>>>> ofrece Infomed para respaldar el cumplimiento de las misiones del >>>>>> Sistema >>>>>> Nacional de Salud. La persona que envia este correo asume el >>>>>> compromiso >>>>>> de >>>>>> usar el servicio a tales fines y cumplir con las regulaciones >>>>>> establecidas >>>>>> >>>>>> Infomed: http://www.sld.cu/ >>>>>> >>>>>> >>>>>> >>>>> __________ Información de ESET Smart Security, versión de la base de >>>>> firmas >>>>> de virus 4804 (20100125) __________ >>>>> >>>>> ESET Smart Security ha comprobado este mensaje. >>>>> >>>>> http://www.eset.com >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> __________ Información de ESET Smart Security, versión de la base de >>>>> firmas de virus 4804 (20100125) __________ >>>>> >>>>> ESET Smart Security ha comprobado este mensaje. >>>>> >>>>> http://www.eset.com >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Este mensaje le ha llegado mediante el servicio de correo electronico >>>>> que >>>>> ofrece Infomed para respaldar el cumplimiento de las misiones del >>>>> Sistema >>>>> Nacional de Salud. La persona que envia este correo asume el >>>>> compromiso >>>>> de >>>>> usar el servicio a tales fines y cumplir con las regulaciones >>>>> establecidas >>>>> >>>>> Infomed: http://www.sld.cu/ >>>>> >>>>> >>>> >>> >>> __________ Información de ESET Smart Security, versión de la base de >>> firmas >>> de virus 4804 (20100125) __________ >>> >>> ESET Smart Security ha comprobado este mensaje. >>> >>> http://www.eset.com >>> >>> >>> >>> >>> >>> >>> >> >> >> __________ Información de ESET Smart Security, versión de la base de >> firmas de virus 4804 (20100125) __________ >> >> ESET Smart Security ha comprobado este mensaje. >> >> http://www.eset.com >> >> >> > > > > > > > > -- > > Este mensaje le ha llegado mediante el servicio de correo electronico que > ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema > Nacional de Salud. La persona que envia este correo asume el compromiso de > usar el servicio a tales fines y cumplir con las regulaciones establecidas > > Infomed: http://www.sld.cu/ > __________ Información de ESET Smart Security, versión de la base de firmas de virus 4804 (20100125) __________ ESET Smart Security ha comprobado este mensaje. http://www.eset.com -- Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema Nacional de Salud. La persona que envia este correo asume el compromiso de usar el servicio a tales fines y cumplir con las regulaciones establecidas Infomed: http://www.sld.cu/
