Re: modem weirdness was: minor error in ppp chatscript
Hi, On Mon, 7 Aug 2000 [EMAIL PROTECTED] wrote: Hrmmm. I must have been more asleep than I thought.. :/ It happens to all of us :-) I am dialing out to my secondary ISP. When modem is connected to the i386 box, I connect to the ISP, press 'enter' and get a login prompt. When modem is connected to the IPX, I connect to the ISP, press 'enter' and fail to get a login prompt. In both cases I am dialing out with the modem command ATDTphone # On the i386 I am using a Belkin serial modem cable. On the IPX I am using a (I THINK Interex) Mac modem cable. well, first of all, IANAn expert in serial ports, but this certainly looks like it has something to do with the problem. Once I heard that if you're using a Mac serial cable, you have to tell the modem you're doing so, 'cause the Mac serial cables don't have all the pins and so you have to tell the modem to expect (or keep) some signals to be always on (or off) or to expect the flow control signals in other pins or some other such... (as you can see, I have no idea what I'm talking about here :-) Unfortunately I couldn't find this informations (or anything resembling it) on a cursory look thru the Serial- and Modem-HOWTOs, but I remember reading about it in a US Robotics modem manual. Try your modem manual for Macintosh instructions. (a few hours later...) Here, found this on the 3com website: USR Sportster manual for x2: ftp://consumerftp.3com.com/3Com%20US%20Robotics%20Modem%20%28Sportster%29/macx2.pdf * make sure dip switch 1 is down and that you put D0 in the init string (ATF1D0 is sugested). * make sure the TR (DTR) light on the modem is on (that is what the dip switch 1 is for, to ignore the DTR and asume it is on). I don't know if it helps, but at least you got a nice pdf manual for x2 for the Mac :-) There are tons of other info on 3com's website (http://www.3com.com/) maybe they have some info on Sparcs. The only one I found was for SS2 and sugested (among other things) lowering the DTE baud to at most 19200, so I didn't think it would apply. Regards, Leo. On Mon, 7 Aug 2000, Leonardo Rochael Almeida wrote: Hi, It is not clear what your problem is. Where are you connecting? (i.e.: what is on the other side of the phone line?) Are you trying to dial into your IPX or out of it? Whose minicom seems locked? the one on the IPX dialing out or the one on the machine you are trying to dial into your IPX? In order to dial into your IPX you have to have a getty of sorts listening on the serial port. Debian's /etc/inittab usually has an example of how to do that, but it is usually commented out. As for the alarm problem, I have no clue. Regards, Leo On Sat, 5 Aug 2000 [EMAIL PROTECTED] wrote: I'm having a different but certainly related problem now. I can talk to the modem fine from within minicom, but my terminal session appears to lock after the modem negotiates connection to the remote and returns the CONNECT string. After connecting I press enter and nothing at all happens until I'm disconnected a minute or so later. However, I connect the modem to my intel box and dial in, I press enter and am greeted with a login prompt. I don't understand what's happening here. Could the cable be bad in some subtle way, or do I need some special init string? I'm just lost right now. On Fri, 4 Aug 2000 [EMAIL PROTECTED] wrote: I'm curious why I would be getting a timeout and alarm at this point of chat. The modem is an external USR Sportster X2 flashed to v.90 code, and the cable is a mac serial crossover cable. I can talk to the modem through minicom and do not see any problems there. The port settings is 38400N81 with hardware flow control. The computer is a Sparc IPX running Potato. Aug 4 22:02:16 runescribe chat[27627]: abort on (BUSY) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO CARRIER) Aug 4 22:02:16 runescribe chat[27627]: abort on (VOICE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO DIALTONE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO DIAL TONE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO ANSWER) Aug 4 22:02:16 runescribe chat[27627]: send (ATZ^M) Aug 4 22:02:16 runescribe chat[27627]: expect (OK) Aug 4 22:03:01 runescribe chat[27627]: alarm Aug 4 22:03:01 runescribe chat[27627]: send (AT^M) Aug 4 22:03:01 runescribe chat[27627]: expect (OK) Aug 4 22:03:01 runescribe chat[27627]: AT^M^M Aug 4 22:03:01 runescribe chat[27627]: OK Aug 4 22:03:01 runescribe chat[27627]: -- got it Aug 4 22:03:01 runescribe chat[27627]: send (ATX4DT4286535^M) Aug 4 22:03:01 runescribe chat[27627]: expect (CONNECT) Aug 4 22:03:01 runescribe chat[27627]: ^M Aug 4 22:03:03 runescribe chat[27627]: ATX4DT4286535^M^M Aug 4 22:03:03 runescribe chat[27627]:
Re: modem weirdness was: minor error in ppp chatscript
Hi, It is not clear what your problem is. Where are you connecting? (i.e.: what is on the other side of the phone line?) Are you trying to dial into your IPX or out of it? Whose minicom seems locked? the one on the IPX dialing out or the one on the machine you are trying to dial into your IPX? In order to dial into your IPX you have to have a getty of sorts listening on the serial port. Debian's /etc/inittab usually has an example of how to do that, but it is usually commented out. As for the alarm problem, I have no clue. Regards, Leo On Sat, 5 Aug 2000 [EMAIL PROTECTED] wrote: I'm having a different but certainly related problem now. I can talk to the modem fine from within minicom, but my terminal session appears to lock after the modem negotiates connection to the remote and returns the CONNECT string. After connecting I press enter and nothing at all happens until I'm disconnected a minute or so later. However, I connect the modem to my intel box and dial in, I press enter and am greeted with a login prompt. I don't understand what's happening here. Could the cable be bad in some subtle way, or do I need some special init string? I'm just lost right now. On Fri, 4 Aug 2000 [EMAIL PROTECTED] wrote: I'm curious why I would be getting a timeout and alarm at this point of chat. The modem is an external USR Sportster X2 flashed to v.90 code, and the cable is a mac serial crossover cable. I can talk to the modem through minicom and do not see any problems there. The port settings is 38400N81 with hardware flow control. The computer is a Sparc IPX running Potato. Aug 4 22:02:16 runescribe chat[27627]: abort on (BUSY) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO CARRIER) Aug 4 22:02:16 runescribe chat[27627]: abort on (VOICE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO DIALTONE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO DIAL TONE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO ANSWER) Aug 4 22:02:16 runescribe chat[27627]: send (ATZ^M) Aug 4 22:02:16 runescribe chat[27627]: expect (OK) Aug 4 22:03:01 runescribe chat[27627]: alarm Aug 4 22:03:01 runescribe chat[27627]: send (AT^M) Aug 4 22:03:01 runescribe chat[27627]: expect (OK) Aug 4 22:03:01 runescribe chat[27627]: AT^M^M Aug 4 22:03:01 runescribe chat[27627]: OK Aug 4 22:03:01 runescribe chat[27627]: -- got it Aug 4 22:03:01 runescribe chat[27627]: send (ATX4DT4286535^M) Aug 4 22:03:01 runescribe chat[27627]: expect (CONNECT) Aug 4 22:03:01 runescribe chat[27627]: ^M Aug 4 22:03:03 runescribe chat[27627]: ATX4DT4286535^M^M Aug 4 22:03:03 runescribe chat[27627]: NO DIAL TONE Aug 4 22:03:03 runescribe chat[27627]: -- failed Aug 4 22:03:03 runescribe chat[27627]: Failed (NO DIAL TONE) Aug 4 22:03:03 runescribe pppd[27620]: Connect script failed
Re: modem weirdness was: minor error in ppp chatscript
Hrmmm. I must have been more asleep than I thought.. :/ I am dialing out to my secondary ISP. When modem is connected to the i386 box, I connect to the ISP, press 'enter' and get a login prompt. When modem is connected to the IPX, I connect to the ISP, press 'enter' and fail to get a login prompt. In both cases I am dialing out with the modem command ATDTphone # On the i386 I am using a Belkin serial modem cable. On the IPX I am using a (I THINK Interex) Mac modem cable. On Mon, 7 Aug 2000, Leonardo Rochael Almeida wrote: Hi, It is not clear what your problem is. Where are you connecting? (i.e.: what is on the other side of the phone line?) Are you trying to dial into your IPX or out of it? Whose minicom seems locked? the one on the IPX dialing out or the one on the machine you are trying to dial into your IPX? In order to dial into your IPX you have to have a getty of sorts listening on the serial port. Debian's /etc/inittab usually has an example of how to do that, but it is usually commented out. As for the alarm problem, I have no clue. Regards, Leo On Sat, 5 Aug 2000 [EMAIL PROTECTED] wrote: I'm having a different but certainly related problem now. I can talk to the modem fine from within minicom, but my terminal session appears to lock after the modem negotiates connection to the remote and returns the CONNECT string. After connecting I press enter and nothing at all happens until I'm disconnected a minute or so later. However, I connect the modem to my intel box and dial in, I press enter and am greeted with a login prompt. I don't understand what's happening here. Could the cable be bad in some subtle way, or do I need some special init string? I'm just lost right now. On Fri, 4 Aug 2000 [EMAIL PROTECTED] wrote: I'm curious why I would be getting a timeout and alarm at this point of chat. The modem is an external USR Sportster X2 flashed to v.90 code, and the cable is a mac serial crossover cable. I can talk to the modem through minicom and do not see any problems there. The port settings is 38400N81 with hardware flow control. The computer is a Sparc IPX running Potato. Aug 4 22:02:16 runescribe chat[27627]: abort on (BUSY) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO CARRIER) Aug 4 22:02:16 runescribe chat[27627]: abort on (VOICE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO DIALTONE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO DIAL TONE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO ANSWER) Aug 4 22:02:16 runescribe chat[27627]: send (ATZ^M) Aug 4 22:02:16 runescribe chat[27627]: expect (OK) Aug 4 22:03:01 runescribe chat[27627]: alarm Aug 4 22:03:01 runescribe chat[27627]: send (AT^M) Aug 4 22:03:01 runescribe chat[27627]: expect (OK) Aug 4 22:03:01 runescribe chat[27627]: AT^M^M Aug 4 22:03:01 runescribe chat[27627]: OK Aug 4 22:03:01 runescribe chat[27627]: -- got it Aug 4 22:03:01 runescribe chat[27627]: send (ATX4DT4286535^M) Aug 4 22:03:01 runescribe chat[27627]: expect (CONNECT) Aug 4 22:03:01 runescribe chat[27627]: ^M Aug 4 22:03:03 runescribe chat[27627]: ATX4DT4286535^M^M Aug 4 22:03:03 runescribe chat[27627]: NO DIAL TONE Aug 4 22:03:03 runescribe chat[27627]: -- failed Aug 4 22:03:03 runescribe chat[27627]: Failed (NO DIAL TONE) Aug 4 22:03:03 runescribe pppd[27620]: Connect script failed
modem weirdness was: minor error in ppp chatscript
I'm having a different but certainly related problem now. I can talk to the modem fine from within minicom, but my terminal session appears to lock after the modem negotiates connection to the remote and returns the CONNECT string. After connecting I press enter and nothing at all happens until I'm disconnected a minute or so later. However, I connect the modem to my intel box and dial in, I press enter and am greeted with a login prompt. I don't understand what's happening here. Could the cable be bad in some subtle way, or do I need some special init string? I'm just lost right now. On Fri, 4 Aug 2000 [EMAIL PROTECTED] wrote: I'm curious why I would be getting a timeout and alarm at this point of chat. The modem is an external USR Sportster X2 flashed to v.90 code, and the cable is a mac serial crossover cable. I can talk to the modem through minicom and do not see any problems there. The port settings is 38400N81 with hardware flow control. The computer is a Sparc IPX running Potato. Aug 4 22:02:16 runescribe chat[27627]: abort on (BUSY) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO CARRIER) Aug 4 22:02:16 runescribe chat[27627]: abort on (VOICE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO DIALTONE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO DIAL TONE) Aug 4 22:02:16 runescribe chat[27627]: abort on (NO ANSWER) Aug 4 22:02:16 runescribe chat[27627]: send (ATZ^M) Aug 4 22:02:16 runescribe chat[27627]: expect (OK) Aug 4 22:03:01 runescribe chat[27627]: alarm Aug 4 22:03:01 runescribe chat[27627]: send (AT^M) Aug 4 22:03:01 runescribe chat[27627]: expect (OK) Aug 4 22:03:01 runescribe chat[27627]: AT^M^M Aug 4 22:03:01 runescribe chat[27627]: OK Aug 4 22:03:01 runescribe chat[27627]: -- got it Aug 4 22:03:01 runescribe chat[27627]: send (ATX4DT4286535^M) Aug 4 22:03:01 runescribe chat[27627]: expect (CONNECT) Aug 4 22:03:01 runescribe chat[27627]: ^M Aug 4 22:03:03 runescribe chat[27627]: ATX4DT4286535^M^M Aug 4 22:03:03 runescribe chat[27627]: NO DIAL TONE Aug 4 22:03:03 runescribe chat[27627]: -- failed Aug 4 22:03:03 runescribe chat[27627]: Failed (NO DIAL TONE) Aug 4 22:03:03 runescribe pppd[27620]: Connect script failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
