Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

2620+8am dialin windows say "remote computer not responsed"

I have this problem when I config it. I don't know where is the mistake. Could you help me? That's very clament!!

Building configuration...

Current configuration:

!

version 12.0

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname router

!

enable secret 5 $1$W/vv$ec.iEER5BMUAxN.3EjMk2/

enable password 0 cisco

!

username aaa password 0 aaa

!

!

!

!

ip subnet-zero

no ip domain-lookup

!

!

!

interface FastEthernet0/0

ip address 172.16.10.100 255.255.255.0

no ip directed-broadcast

no ip mroute-cache

speed auto

full-duplex

!

interface Group-Async1

ip unnumbered FastEthernet0/0

no ip directed-broadcast

encapsulation ppp

ip tcp header-compression passive

no ip mroute-cache

async mode interactive

no fair-queue

peer default ip address pool setup_pool

no cdp enable

ppp authentication chap pap callin

group-range 33 40

!

router rip

version 2

network 172.16.10.0

!

ip local pool setup_pool 172.16.10.245 172.16.10.254

ip classless

no ip http server

!

line con 0

exec-timeout 0 0

password cisco

login

transport input none

line 33 40

autoselect during-login

autoselect ppp

login local

modem InOut

transport input all

transport output pad v120 telnet rlogin udptn

stopbits 1

flowcontrol hardware

line aux 0

exec-timeout 0 0

password cisco

login

modem InOut

modem autoconfigure discovery

transport input all

speed 38400

flowcontrol hardware

line vty 0 4

password cisco

login

!

no scheduler allocate

end

13 REPLIES
Cisco Employee

Re: 2620+8am dialin windows say "remote computer not responsed"

Config looks fine..We need to see the following debug from the router during call

debug modem

debug ppp authentication

debug ppp negotiation

term mon

Above debug will give us clear idea about whats going on there...Tejal

New Member

Re: 2620+8am dialin windows say "remote computer not responsed"

Oh, Thanx first. But tomorrow is Sat. and I have no chance to config the router, because I configed it remotely use aux. And I'll post debug result at Monday, hope can still get your help! Thank you!

New Member

Re: 2620+8am dialin windows say "remote computer not responsed"

Try to reduce the "speed" or not to configure the speed in the line interface, check the phone line(try to put a basic phone-to-phone call to know if the line is ready to used). Check the grounding. Oh ye please verify your debug command carefully.

New Member

Re: 2620+8am dialin windows say "remote computer not responsed"

I want to receive call use 8am module, and I set speed on my aux port. But I forgot to debug it. That's a terrible thing :) So I'll do it next Monday. Thanx.

New Member

Re: 2620+8am dialin windows say "remote computer not responsed"

Dear mate, I have get the debug infomation, I think the problem perhaps is the chap authentication process. And I want your help on edge. Thanx!!

router#

router#

router#

router#sh line

Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int

0 CTY - - - - - 0 0 0/0 -

Ready

A 33 TTY - inout - - - 0 0 0/0 -

Ready

I 34 TTY - inout - - - 0 0 0/0 -

Idle

I 35 TTY - inout - - - 0 0 0/0 -

Idle

I 36 TTY - inout - - - 0 0 0/0 -

Idle

I 37 TTY - inout - - - 0 0 0/0 -

Idle

I 38 TTY - inout - - - 0 0 0/0 -

Idle

I 39 TTY - inout - - - 0 0 0/0 -

Idle

I 40 TTY - inout - - - 0 0 0/0 -

Idle

* 65 AUX 115200/115200- inout - - - 0 0 84/564 -

Ready

66 VTY - - - - - 0 0 0/0 -

Idle

--More-- Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int

67 VTY - - - - - 0 0 0/0 -

Idle

68 VTY - - - - - 0 0 0/0 -

Idle

69 VTY - - - - - 0 0 0/0 -

Idle

70 VTY - - - - - 0 0 0/0 -

Idle

Line(s) not in async mode -or- with no hardware support:

1-32, 41-64

router#debut g modem

Modem control/process activation debugging is on

router#debug ppp authen

router#debug ppp authentication

PPP authentication debugging is on

router#debug ppp neg

router#debug ppp negotiation

PPP protocol negotiation debugging is on

router#term mon

router#

router#

00:28:56: Modem 1/0 Mcom: in modem state 'Dialing/Answering'

00:28:56: Modem 1/0 Mcom: in modem state 'Incoming ring'

00:28:59: Modem 1/0 Mcom: in modem state 'Waiting for Carrier'

00:29:05: Modem 1/0 Mcom: in modem state 'Connected'

00:29:05: Modem 1/0 Mcom: CONNECT at 300/300(Tx/Rx), BEL103, Normal, None, Answer

00:29:05: TTY33: DSR came up

00:29:05: tty33: Modem: IDLE->(unknown)

00:29:05: TTY33: EXEC creation

00:29:05: TTY33: set timer type 10, 30 seconds

00:29:06: TTY33: Autoselect(2) sample FF

00:29:06: TTY33: Autoselect(2) sample FFFF

00:29:06: TTY33: Autoselect(2) sample FFFFFF

00:29:06: TTY33: Autoselect(2) sample FFFFFFFF

00:29:06: TTY33: Autoselect(2) sample FFFFFFFF

00:29:06: TTY33: Autoselect(2) sample FFFFFFFF

00:29:07: TTY33: Autoselect(2) sample FFFFFFFF

00:29:07: TTY33: Autoselect(2) sample FFFFFFFF

00:29:07: TTY33: Autoselect(2) sample FFFFFFFF

00:29:07: TTY33: Autoselect(2) sample FFFFFFFF

00:29:07: TTY33: Autoselect(2) sample FFFFFFFF

00:29:07: TTY33: Autoselect(2) sample FFFFFFFF

00:29:07: TTY33: Autoselect(2) sample FFFFFFFF

00:29:07: TTY33: Autoselect(2) sample FFFFFFFF

00:29:10: TTY33: Autoselect(2) sample FFFFFF7E

00:29:10: TTY33: Autoselect(2) sample FFFF7EFE

00:29:10: TTY33: Autoselect(2) sample FF7EFE7D

00:29:10: TTY33: Autoselect(2) sample 7EFE7D23

00:29:10: TTY33: set timer type 10, 30 seconds

00:29:10: TTY33: Autoselect(2) sample FE7D23FF

00:29:10: TTY33: Autoselect(2) sample 7D23FFDF

00:29:11: TTY33: Autoselect(2) sample 23FFDFDF

00:29:11: TTY33: Autoselect(2) sample FFDFDFDF

00:29:11: TTY33: Autoselect(2) sample DFDFDFFF

00:29:11: TTY33: Autoselect(2) sample DFDFFFFF

00:29:11: TTY33: Autoselect(2) sample DFFFFFFF

00:29:11: TTY33: Autoselect(2) sample FFFFFFFF

00:29:11: TTY33: Autoselect(2) sample FFFFFFDF

00:29:11: TTY33: Autoselect(2) sample FFFFDFFF

00:29:11: TTY33: Autoselect(2) sample FFDFFFFF

00:29:11: TTY33: Autoselect(2) sample DFFFFFFF

00:29:11: TTY33: Autoselect(2) sample FFFFFFFF

00:29:11: TTY33: Autoselect(2) sample FFFFFFFF

00:29:11: TTY33: Autoselect(2) sample FFFFFFFF

00:29:11: TTY33: Autoselect(2) sample FFFFFFFF

00:29:11: TTY33: Autoselect(2) sample FFFFFFDF

00:29:11: TTY33: Autoselect(2) sample FFFFDFFF

00:29:11: TTY33: Autoselect(2) sample FFDFFFDF

00:29:12: TTY33: Autoselect(2) sample DFFFDFBE

00:29:12: TTY33: Autoselect(2) sample FFDFBEFF

00:29:12: TTY33: Autoselect(2) sample DFBEFFFE

00:29:12: TTY33: Autoselect(2) sample BEFFFEFF

00:29:13: TTY33: Autoselect(2) sample FFFEFFFF

00:29:13: TTY33: Autoselect(2) sample FEFFFFFF

00:29:15: TTY33: Autoselect(2) sample FFFFFFFF

00:29:18: TTY33: Autoselect(2) sample FFFFFFFF

00:29:18: TTY33: Autoselect(2) sample FFFFFF7E

00:29:18: TTY33: Autoselect(2) sample FFFF7EFF

00:29:18: TTY33: Autoselect(2) sample FF7EFF7D

00:29:18: TTY33: Autoselect(2) sample 7EFF7D23

00:29:18: TTY33 Autoselect cmd: ppp negotiate

00:29:18: TTY33: EXEC creation

00:29:18: TTY33: create timer type 1, 600 seconds

00:29:18: TTY33: destroy timer type 1 (OK)

00:29:18: TTY33: destroy timer type 0

00:29:18: As33 IPCP: Install route to 172.16.10.252

00:29:20: %LINK-3-UPDOWN: Interface Async33, changed state to up

00:29:20: As33 PPP: Treating connection as a callin

00:29:20: As33 PPP: Phase is ESTABLISHING, Passive Open

00:29:20: Modem 1/0 Mcom: PPP escape map: Tx map = FFFFFFFF, Rx map = 0

00:29:20: As33 LCP: State is Listen

00:29:22: As33 LCP: TIMEout: State Listen

00:29:22: Modem 1/0 Mcom: PPP escape map: Tx map = FFFFFFFF, Rx map = 0

00:29:22: As33 LCP: O CONFREQ [Listen] id 77 len 25

00:29:22: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:22: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:22: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:22: As33 LCP: PFC (0x0702)

00:29:22: As33 LCP: ACFC (0x0802)

00:29:24: As33 LCP: TIMEout: State REQsent

00:29:24: As33 LCP: O CONFREQ [REQsent] id 78 len 25

00:29:24: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:24: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:24: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:24: As33 LCP: PFC (0x0702)

00:29:24: As33 LCP: ACFC (0x0802)

00:29:26: As33 LCP: TIMEout: State REQsent

00:29:26: As33 LCP: O CONFREQ [REQsent] id 79 len 25

00:29:26: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:26: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:26: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:26: As33 LCP: PFC (0x0702)

00:29:26: As33 LCP: ACFC (0x0802)

00:29:28: As33 LCP: TIMEout: State REQsent

00:29:28: As33 LCP: O CONFREQ [REQsent] id 80 len 25

00:29:28: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:28: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:28: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:28: As33 LCP: PFC (0x0702)

00:29:28: As33 LCP: ACFC (0x0802)

00:29:30: As33 LCP: TIMEout: State REQsent

00:29:30: As33 LCP: O CONFREQ [REQsent] id 81 len 25

00:29:30: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:30: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:30: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:30: As33 LCP: PFC (0x0702)

00:29:30: As33 LCP: ACFC (0x0802)

00:29:32: As33 LCP: TIMEout: State REQsent

00:29:32: As33 LCP: O CONFREQ [REQsent] id 82 len 25

00:29:32: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:32: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:32: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:32: As33 LCP: PFC (0x0702)

00:29:32: As33 LCP: ACFC (0x0802)

00:29:34: As33 LCP: TIMEout: State REQsent

00:29:34: As33 LCP: O CONFREQ [REQsent] id 83 len 25

00:29:34: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:34: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:34: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:34: As33 LCP: PFC (0x0702)

00:29:34: As33 LCP: ACFC (0x0802)

00:29:36: As33 LCP: TIMEout: State REQsent

00:29:36: As33 LCP: O CONFREQ [REQsent] id 84 len 25

00:29:36: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:36: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:36: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:36: As33 LCP: PFC (0x0702)

00:29:36: As33 LCP: ACFC (0x0802)

00:29:38: As33 LCP: TIMEout: State REQsent

00:29:38: As33 LCP: O CONFREQ [REQsent] id 85 len 25

00:29:38: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:38: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:38: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:38: As33 LCP: PFC (0x0702)

00:29:38: As33 LCP: ACFC (0x0802)

00:29:40: As33 LCP: TIMEout: State REQsent

00:29:40: As33 LCP: O CONFREQ [REQsent] id 86 len 25

00:29:40: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:40: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:40: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:40: As33 LCP: PFC (0x0702)

00:29:40: As33 LCP: ACFC (0x0802)

00:29:42: As33 LCP: TIMEout: State REQsent

00:29:42: As33 LCP: O CONFREQ [REQsent] id 87 len 25

00:29:42: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:29:42: As33 LCP: AuthProto CHAP (0x0305C22305)

00:29:42: As33 LCP: MagicNumber 0x083C9860 (0x0506083C9860)

00:29:42: As33 LCP: PFC (0x0702)

00:29:42: As33 LCP: ACFC (0x0802)

00:29:44: As33 LCP: TIMEout: State REQsent

00:29:44: TTY33: Async Int reset: Dropping DTR

00:29:44: As33 LCP: State is Listen

00:29:44: Modem 1/0 Mcom: in modem state 'Disconnecting'

00:29:44: Modem 1/0 Mcom: DISCONNECT, duration = 00:00:40, reason (0x9) DTR Drop

00:29:45: TTY33: DSR was dropped

00:29:45: tty33: Modem: READY->(unknown)

00:29:45: Modem 1/0 Mcom: in modem state 'Idle'

00:29:46: TTY33: dropping DTR, hanging up

00:29:46: tty33: Modem: HANGUP->(unknown)

00:29:46: %LINK-5-CHANGED: Interface Async33, changed state to reset

00:29:46: As33 LCP: State is Closed

00:29:46: As33 PPP: Phase is DOWN

00:29:47: TTY33: cleanup pending. Delaying DTR

00:29:48: TTY33: cleanup pending. Delaying DTR

00:29:49: TTY33: cleanup pending. Delaying DTR

00:29:49: TTY33: destroy timer type 0

00:29:49: TTY33: destroy timer type 1

00:29:49: TTY33: destroy timer type 3

00:29:49: TTY33: destroy timer type 4

00:29:49: TTY33: destroy timer type 2

00:29:49: Async33: allowing modem_process to continue hangup

00:29:49: As33 IPCP: Remove route to 172.16.10.252

00:29:50: TTY33: restoring DTR

00:29:51: %LINK-3-UPDOWN: Interface Async33, changed state to down

00:29:51: As33 LCP: State is Closed

Cisco Employee

Re: 2620+8am dialin windows say "remote computer not responsed"

Somhow router is not getting the LCP reply from the other side device..Here is the suggestion

use "Async mode dedicated" under the interface group-async 1 instead of "interactive" and see if that make any difference..Thanks..Tejal

New Member

Re: 2620+8am dialin windows say "remote computer not responsed"

other side is PC, use "dialup network".

New Member

Re: 2620+8am dialin windows say "remote computer not responsed"

I have change it to "dedicated" ,but it is still can't work. remote PC's error code is 619. and the follow is the debug info. I don't know how to do ........

00:11:23: Modem 1/0 Mcom: in modem state 'Dialing/Answering'

00:11:23: Modem 1/0 Mcom: in modem state 'Incoming ring'

00:11:26: Modem 1/0 Mcom: in modem state 'Waiting for Carrier'

00:12:05: Modem 1/0 Mcom: in modem state 'Connected'

00:12:05: Modem 1/0 Mcom: CONNECT at 300/300(Tx/Rx), BEL103, Normal, None, Answer

00:12:05: TTY33: DSR came up

00:12:05: TTY33: destroy timer type 1

00:12:05: TTY33: destroy timer type 0

00:12:05: tty33: Modem: IDLE->(unknown)

00:12:07: %LINK-3-UPDOWN: Interface Async33, changed state to up

00:12:07: As33 PPP: Treating connection as a callin

00:12:07: As33 PPP: Phase is ESTABLISHING, Passive Open

00:12:07: Modem 1/0 Mcom: PPP escape map: Tx map = FFFFFFFF, Rx map = 0

00:12:07: As33 LCP: State is Listen

00:12:09: As33 LCP: TIMEout: State Listen

00:12:09: Modem 1/0 Mcom: PPP escape map: Tx map = FFFFFFFF, Rx map = 0

00:12:09: As33 LCP: O CONFREQ [Listen] id 23 len 25

00:12:09: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:09: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:09: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:09: As33 LCP: PFC (0x0702)

00:12:09: As33 LCP: ACFC (0x0802)

00:12:11: As33 LCP: TIMEout: State REQsent

00:12:11: As33 LCP: O CONFREQ [REQsent] id 24 len 25

00:12:11: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:11: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:11: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:11: As33 LCP: PFC (0x0702)

00:12:11: As33 LCP: ACFC (0x0802)

00:12:13: As33 LCP: TIMEout: State REQsent

00:12:13: As33 LCP: O CONFREQ [REQsent] id 25 len 25

00:12:13: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:13: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:13: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:13: As33 LCP: PFC (0x0702)

00:12:13: As33 LCP: ACFC (0x0802)

00:12:15: As33 LCP: TIMEout: State REQsent

00:12:15: As33 LCP: O CONFREQ [REQsent] id 26 len 25

00:12:15: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:15: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:15: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:15: As33 LCP: PFC (0x0702)

00:12:15: As33 LCP: ACFC (0x0802)

00:12:17: As33 LCP: TIMEout: State REQsent

00:12:17: As33 LCP: O CONFREQ [REQsent] id 27 len 25

00:12:17: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:17: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:17: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:17: As33 LCP: PFC (0x0702)

00:12:17: As33 LCP: ACFC (0x0802)

00:12:19: As33 LCP: TIMEout: State REQsent

00:12:19: As33 LCP: O CONFREQ [REQsent] id 28 len 25

00:12:19: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:19: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:19: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:19: As33 LCP: PFC (0x0702)

00:12:19: As33 LCP: ACFC (0x0802)

00:12:21: As33 LCP: TIMEout: State REQsent

00:12:21: As33 LCP: O CONFREQ [REQsent] id 29 len 25

00:12:21: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:21: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:21: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:21: As33 LCP: PFC (0x0702)

00:12:21: As33 LCP: ACFC (0x0802)

00:12:23: As33 LCP: TIMEout: State REQsent

00:12:23: As33 LCP: O CONFREQ [REQsent] id 30 len 25

00:12:23: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:23: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:23: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:23: As33 LCP: PFC (0x0702)

00:12:23: As33 LCP: ACFC (0x0802)

00:12:25: As33 LCP: TIMEout: State REQsent

00:12:25: As33 LCP: O CONFREQ [REQsent] id 31 len 25

00:12:25: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:25: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:25: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:25: As33 LCP: PFC (0x0702)

00:12:25: As33 LCP: ACFC (0x0802)

00:12:27: As33 LCP: TIMEout: State REQsent

00:12:27: As33 LCP: O CONFREQ [REQsent] id 32 len 25

00:12:27: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:27: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:27: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:27: As33 LCP: PFC (0x0702)

00:12:27: As33 LCP: ACFC (0x0802)

00:12:29: As33 LCP: TIMEout: State REQsent

00:12:29: As33 LCP: O CONFREQ [REQsent] id 33 len 25

00:12:29: As33 LCP: ACCM 0x000A0000 (0x0206000A0000)

00:12:29: As33 LCP: AuthProto CHAP (0x0305C22305)

00:12:29: As33 LCP: MagicNumber 0x082CD466 (0x0506082CD466)

00:12:29: As33 LCP: PFC (0x0702)

00:12:29: As33 LCP: ACFC (0x0802)

00:12:31: As33 LCP: TIMEout: State REQsent

00:12:31: TTY33: Async Int reset: Dropping DTR

00:12:31: As33 LCP: State is Listen

00:12:31: Modem 1/0 Mcom: in modem state 'Disconnecting'

00:12:31: Modem 1/0 Mcom: DISCONNECT, duration = 00:00:26, reason (0x9) DTR Drop

00:12:32: Modem 1/0 Mcom: in modem state 'Idle'

00:12:32: TTY33: DSR was dropped

00:12:32: tty33: Modem: READY->(unknown)

00:12:33: %LINK-5-CHANGED: Interface Async33, changed state to reset

00:12:33: As33 LCP: State is Closed

00:12:33: As33 PPP: Phase is DOWN

00:12:33: TTY33: dropping DTR, hanging up

00:12:33: tty33: Modem: HANGUP->(unknown)

00:12:34: TTY33: cleanup pending. Delaying DTR

00:12:35: TTY33: cleanup pending. Delaying DTR

00:12:36: TTY33: destroy timer type 0

00:12:36: TTY33: destroy timer type 1

00:12:36: TTY33: destroy timer type 3

00:12:36: TTY33: destroy timer type 4

00:12:36: TTY33: destroy timer type 2

00:12:36: Async33: allowing modem_process to continue hangup

00:12:37: TTY33: restoring DTR

00:12:38: %LINK-3-UPDOWN: Interface Async33, changed state to down

00:12:38: As33 LCP: State is Closed

New Member

Re: 2620+8am dialin windows say "remote computer not responsed"

I don't know if it is pressed for "modem autoconfigure discovery" in the line 33 to 40

New Member

Re: 2620+8am dialin windows say "remote computer not responsed"

And I havn't grounding the device. Someone told me 8am is a grounding sensitivity module. Who could tell me if it is a important factor?

Silver

Re: 2620+8am dialin windows say "remote computer not responsed"

The previous two debugs indicate the call connected only at BEL103 (300 baud)....try forcing to v.34:

configure terminal

modemcap edit V34_ONLY misc &F%L0

line 33 40

modem autoconfigure type V34_ONLY

Also can you try moving the PSTN line to another modem port, say 34 or changing the line itself.

Yes, the chassis needs to be grounded .....please refer to Field Notice to this effect:

http://www-tac/Support_Library/field_alerts/fn8771.html

Thanks, Mak.

New Member

Re: 2620+8am dialin windows say "remote computer not responsed"

Can I type "modem autoconfigure discovery" instead "modem autoconfigure type V34_ONLY"? And if I can use it , should I still type "modemcap edit V34_ONLY misc &F%L0"???

Silver

Re: 2620+8am dialin windows say "remote computer not responsed"

You can with the "modem autoconfig discovery" , without the "modem autoconfigure type V34_ONLY" (IOS trying to detect the external modem connected)....if that does not work, try locking to v.34.

Also as per the previous messages:

1)Try changing the modem port.

2)Try changing the POTS line.

3)The chassis needs to be properly grounded.

Thanks, Mak.

149
Views
0
Helpful
13
Replies
CreatePlease login to create content