Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.

Cisco Router i Windows RAS problemi

[es] :: Enterprise Networking :: Cisco Router i Windows RAS problemi

[ Pregleda: 5886 | Odgovora: 6 ] > FB > Twit

Postavi temu Odgovori

Autor

Pretraga teme: Traži
Markiranje Štampanje RSS

djk494

Član broj: 494
Poruke: 320
195.252.81.*



+39 Profil

icon Cisco Router i Windows RAS problemi30.03.2005. u 16:29 - pre 231 meseci
Problem pri povezivanju Cisco routera na Windows RAS.

Konfiguracija cisco rutera:

interface BRI3/0
no ip address
encapsulation ppp
logging event nfas-status
dialer pool-member 1
isdn switch-type basic-net3
no cdp enable
!
interface Dialer200
description test
ip address negotiated
encapsulation ppp
dialer pool 1
dialer idle-timeout 60
dialer string xxxxxxxxxxx
dialer-group 1
no peer default ip address
ppp pap sent-username xXxXxXxXx password 0 xXxXxXxXx
!
ip route 172.16.200.0 255.255.255.0 Dialer200
!
dialer-list 1 protocol ip permit


debug ppp negotiation
debug ppp authentication
debug ppp error
terminal monitor

*Mar 30 07:15:31: %ISDN-6-LAYER2UP: Layer 2 for Interface BR3/0, TEI 88 changed to up
*Mar 30 17:15:32: %LINK-3-UPDOWN: Interface BRI3/0:1, changed state to up
*Mar 30 17:15:32: %DIALER-6-BIND: Interface BR3/0:1 bound to profile Di200
*Mar 30 17:15:34: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to down
*Mar 30 17:15:34: %ISDN-6-CONNECT: Interface BRI3/0:1 is now connected to 307xxxx 3c86.2052.4153
*Mar 30 17:15:34: %ISDN-6-DISCONNECT: Interface BRI3/0:1 disconnected from 307xxxx 3c86.2052.4153, call lasted 2 seconds
*Mar 30 17:15:35: %LINK-3-UPDOWN: Interface BRI3/0:1, changed state to down
*Mar 30 17:15:35: %DIALER-6-UNBIND: Interface BR3/0:1 unbound from profile Di200 *Mar 30 17:15:37: %LINK-3-UPDOWN: Interface BRI3/0:1, changed state to up
*Mar 30 17:15:37: %DIALER-6-BIND: Interface BR3/0:1 bound to profile Di200
*Mar 30 17:15:39: %ISDN-6-CONNECT: Interface BRI3/0:1 is now connected to 307xxxx 3c86.2052.4153
*Mar 30 17:15:39: %ISDN-6-DISCONNECT: Interface BRI3/0:1 disconnected from 307xxxx 3c86.2052.4153, call lasted 2 seconds
*Mar 30 17:15:39: %LINK-3-UPDOWN: Interface BRI3/0:1, changed state to down
*Mar 30 17:15:39: %DIALER-6-UNBIND: Interface BR3/0:1 unbound from profile Di200 *Mar 30 17:15:41: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR3/0, TEI 88 changed to down


Probao na Win 2000 Pro i Win 2003 Server i nece konekcija Cisco na Win sve ostale varjante Win na (Win, Cisco BRI, Cisco 042) i Cisco na (Cisco BRI, Cisco 042) rade...

P.S. Probao sa Intracom i Fritz modemima.

[Ovu poruku je menjao Djaki dana 01.04.2005. u 20:15 GMT+1]
 
Odgovor na temu

nenadgro

Član broj: 15054
Poruke: 30
*.cytanet.com.cy.



Profil

icon Re: Cisco Router i Windows RAS problemi31.03.2005. u 09:18 - pre 231 meseci
Upali:

debug isdn events
debug isdn q921
debug isdn q931

Pa posalji log...
 
Odgovor na temu

djk494

Član broj: 494
Poruke: 320
195.252.81.*



+39 Profil

icon Re: Cisco Router i Windows RAS problemi01.04.2005. u 14:54 - pre 231 meseci
Na C801 IOS 12.3 konekcija na win2003 server RAS setovan da prihvata PAP autentifikaciju.

debug isdn events
debug isdn q921
debug isdn q931

TeST#ping 172.16.200.1


Apr 1 13:30:15.199: ISDN BR0 EVENT: isdn_sw_cstate: State = 0, Old State = 6.
Apr 1 13:31:14.727: ISDN BR0 EVENT: UserIdle: callid 0x8016 received ISDN_CALL (0x0)
Apr 1 13:31:14.763: ISDN BR0 EVENT: handle_l2d_srq_mail: Activating Layer 1
Apr 1 13:31:14.767: ISDN BR0 EVENT: isdn_sw_cstate: State = 4, Old State = 4
Apr 1 13:31:14.963: ISDN BR0 EVENT: service_queue_from_physical_layer: Recvd L1 prim 1 state is 0
Apr 1 13:31:14.967: ISDN BR0 EVENT: isdn_sw_cstate: State = 4, Old State = 4
Apr 1 13:31:14.971: ISDN BR0 Q921: User TX -> IDREQ ri=727 ai=127
Apr 1 13:31:15.003: ISDN BR0 Q921: User RX <- IDASSN ri=727 ai=75
Apr 1 13:31:15.019: ISDN BR0 Q921: User TX -> SABMEp sapi=0 tei=75.
Apr 1 13:31:15.055: ISDN BR0 Q921: User TX -> INFO sapi=0 tei=75, ns=0 nr=0
Apr 1 13:31:15.071: ISDN BR0 Q931: SETUP pd = 8 callref = 0x16
Bearer Capability i = 0x8890
Standard = CCITT
Transer Capability = Unrestricted Digital
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x83
Called Party Number i = 0x80, '307xxxx'
Plan:Unknown, Type:Unknown
Apr 1 13:31:15.211: ISDN BR0 Q921: User RX <- RR sapi=0 tei=75 nr=1
Apr 1 13:31:15.287: ISDN BR0 Q921: User RX <- INFO sapi=0 tei=75, ns=0 nr=1
Apr 1 13:31:15.291: ISDN BR0 Q931: SETUP_ACK pd = 8 callref = 0x96
Channel ID i = 0x89
Apr 1 13:31:15.299: ISDN BR0 Q921: User TX -> RR sapi=0 tei=75 nr=1
Apr 1 13:31:15.307: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x8016 calltype 1 HOST_INFORMATION
Apr 1 13:31:15.487: ISDN BR0 Q921: User RX <- INFO sapi=0 tei=75, ns=1 nr=1
Apr 1 13:31:15.487: ISDN BR0 Q931: CALL_PROC pd = 8 callref = 0x96
Apr 1 13:31:15.495: ISDN BR0 Q921: User TX -> RR sapi=0 tei=75 nr=2
Apr 1 13:31:15.507: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x8016 calltype 1 HOST_PROCEEDING
Apr 1 13:31:15.811: ISDN BR0 Q921: User RX <- INFO sapi=0 tei=75, ns=2 nr=1
Apr 1 13:31:15.811: ISDN BR0 Q931: ALERTING pd = 8 callref = 0x96.
Apr 1 13:31:15.819: ISDN BR0 Q921: User TX -> RR sapi=0 tei=75 nr=3
Apr 1 13:31:15.827: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x8016 calltype 1 HOST_ALERTING
Apr 1 13:31:16.235: ISDN BR0 Q921: User RX <- INFO sapi=0 tei=75, ns=3 nr=1
Apr 1 13:31:16.239: ISDN BR0 Q931: CONNECT pd = 8 callref = 0x96
Date/Time i = 0x0504010D1E00
Apr 1 13:31:16.247: ISDN BR0 Q921: User TX -> RR sapi=0 tei=75 nr=4
Apr 1 13:31:16.255: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x8016 calltype 1 HOST_CONNECT
Apr 1 13:31:16.275: ISDN BR0 Q921: User TX -> INFO sapi=0 tei=75, ns=1 nr=4
Apr 1 13:31:16.275: ISDN BR0 Q931: CONNECT_ACK pd = 8 callref = 0x16
Apr 1 13:31:16.387: ISDN BR0 Q921: User RX <- RR sapi=0 tei=75 nr=2
Apr 1 13:31:16.931: ISDN BR0 Q921: User RX <- INFO sapi=0 tei=75, ns=4 nr=2
Apr 1 13:31:16.935: ISDN BR0 Q931: DISCONNECT pd = 8 callref = 0x96
Cause i = 0x8090 - Normal call clearing
Progress Ind i = 0x8288 - In-band info or appropriate now available
Apr 1 13:31:16.939: ISDN BR0 Q921: User TX -> RR sapi=0 tei=75 nr=5
Apr 1 13:31:16.947: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x8016 calltype 1 HOST_DISCONNECT
Apr 1 13:31:16.971: ISDN BR0 Q921: User TX -> INFO sapi=0 tei=75, ns=2 nr=5
Apr 1 13:31:16.975: ISDN BR0 Q931: RELEASE pd = 8 callref = 0x16
Cause i = 0x8090 - Normal call clearing
Apr 1 13:31:17.087: ISDN BR0 Q921: User RX <- RR sapi=0 tei=75 nr=3
Apr 1 13:31:17.119: ISDN BR0 Q921: User RX <- INFO sapi=0 tei=75, ns=5 nr=3
Apr 1 13:31:17.119: ISDN BR0 Q931: RELEASE_COMP pd = 8 callref = 0x96
Apr 1 13:31:17.127: ISDN BR0 Q921: User TX -> RR sapi=0 tei=75 nr=6
Apr 1 13:31:17.135: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x8016 calltype 1 HOST_DISCONNECT_ACK.
Success rate is 0 
Apr 1 13:31:18.079: ISDN BR0 Q921: User RX <- IDCKRQ ri=0 ai=127
Apr 1 13:31:18.091: ISDN BR0 Q921: User TX -> IDCKRP ri=12360 ai=75
Apr 1 13:31:18.615: ISDN BR0 EVENT: UserIdle: callid 0x8017 received ISDN_CALL (0x0)
Apr 1 13:31:18.627: ISDN BR0 Q921: User TX -> INFO sapi=0 tei=75, ns=3 nr=6
Apr 1 13:31:18.631: ISDN BR0 Q931: SETUP pd = 8 callref = 0x17
Bearer Capability i = 0x8890
Standard = CCITT
Transer Capability = Unrestricted Digital
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x83
Called Party Number i = 0x80, '307xxxx'
Plan:Unknown, Type:Unknown
Apr 1 13:31:18.667: ISDN BR0 Q921: User RX <- RR sapi=0 tei=75 nr=4
Apr 1 13:31:18.835: ISDN BR0 Q921: User RX <- INFO sapi=0 tei=75, ns=6 nr=4
Apr 1 13:31:18.835: ISDN BR0 Q931: SETUP_ACK pd = 8 callref = 0x97




debug ppp authentication
debug ppp negotiation


TeST#ping 172.16.200.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.200.1, timeout is 2 seconds:

Apr 1 14:40:06.130: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
Apr 1 14:40:06.142: BR0:1 PPP: Using dialer call direction
Apr 1 14:40:06.142: BR0:1 PPP: Treating connection as a callout
Apr 1 14:40:06.146: BR0:1 PPP: Phase is ESTABLISHING, Active Open
Apr 1 14:40:06.146: BR0:1 PPP: Authorization required
Apr 1 14:40:06.150: BR0:1 LCP: O CONFREQ [Closed] id 239 len 14
Apr 1 14:40:06.150: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:06.150: BR0:1 LCP: MagicNumber 0x0F9F2094 (0x05060F9F2094)
Apr 1 14:40:06.462: BR0:1 LCP: I CONFREQ [REQsent] id 0 len 14
Apr 1 14:40:06.466: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:06.466: BR0:1 LCP: MagicNumber 0x20BF228A (0x050620BF228A).
Apr 1 14:40:06.486: BR0:1 PAP: O AUTH-REQ id 27 len 24 from "username"
Apr 1 14:40:06.806: BR0:1 PAP: I AUTH-ACK id 27 len 5
Apr 1 14:40:06.810: BR0:1 LCP: I CONFREQ [Open] id 2 len 14
Apr 1 14:40:06.814: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:06.814: BR0:1 LCP: MagicNumber 0x251F63BA (0x0506251F63BA)
Apr 1 14:40:06.818: BR0:1 PPP: Phase is TERMINATING
Apr 1 14:40:06.818: BR0:1 PPP: Authorization required
Apr 1 14:40:06.818: BR0:1 PPP: Phase is ESTABLISHING
Apr 1 14:40:06.822: BR0:1 LCP: O CONFREQ [Open] id 240 len 14
Apr 1 14:40:06.822: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:06.826: BR0:1 LCP: MagicNumber 0x0F9F2335 (0x05060F9F2335)
Apr 1 14:40:06.826: BR0:1 LCP: O CONFACK [Open] id 2 len 14
Apr 1 14:40:06.830: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:06.830: BR0:1 LCP: MagicNumber 0x251F63BA (0x0506251F63BA)
Apr 1 14:40:07.146: BR0:1 LCP: I CONFREJ [ACKsent] id 240 len 8
Apr 1 14:40:07.150: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:07.150: BR0:1 LCP: O CONFREQ [ACKsent] id 241 len 14
Apr 1 14:40:07.150: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:07.154: BR0:1 LCP: MagicNumber 0x0F9F2335 (0x05060F9F2335)
Apr 1 14:40:07.170: BR0:1 LCP: I CONFREJ [ACKsent] id 241 len 8
Apr 1 14:40:07.170: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:07.170: BR0:1 LCP: O CONFREQ [ACKsent] id 242 len 14
Apr 1 14:40:07.174: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:07.174: BR0:1 LCP: MagicNumber 0x0F9F2335 (0x05060F9F2335)
Apr 1 14:40:07.278: BR0:1 LCP: I CONFREJ [ACKsent] id 242 len 8
Apr 1 14:40:07.278: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:07.282: BR0:1 LCP: O CONFREQ [ACKsent] id 243 len 14
Apr 1 14:40:07.282: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:07.282: BR0:1 LCP: MagicNumber 0x0F9F2335 (0x05060F9F2335)
Apr 1 14:40:07.298: BR0:1 LCP: I CONFREJ [ACKsent] id 243 len 8.
Apr 1 14:40:07.298: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:07.302: BR0:1 LCP: O CONFREQ [ACKsent] id 244 len 14
Apr 1 14:40:07.302: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:07.302: BR0:1 LCP: MagicNumber 0x0F9F2335 (0x05060F9F2335)
Apr 1 14:40:07.614: BR0:1 LCP: I CONFREJ [ACKsent] id 244 len 8
Apr 1 14:40:07.614: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:07.618: BR0:1 LCP: O CONFREQ [ACKsent] id 245 len 14
Apr 1 14:40:07.618: BR0:1 LCP: AuthProto PAP (0x0304C023)
Apr 1 14:40:07.618: BR0:1 LCP: MagicNumber 0x0F9F2335 (0x05060F9F2335)
Apr 1 14:40:07.634: BR0:1 LCP: I TERMREQ [ACKsent] id 3 len 16 (0x251F63BA003CCD74000002DC)
Apr 1 14:40:07.638: BR0:1 LCP: O TERMACK [ACKsent] id 3 len 4
Apr 1 14:40:07.638: BR0:1 PPP: Authorization required
Apr 1 14:40:09.654: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up.

Success rate is 0 perceî



prethodni ciklus ide tri puta i na kraju ide

Apr 1 14:40:18.474: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 79 changed to down
Apr 1 14:40:41.358: %PQUICC-1-LOSTCARR: Unit 0, lost carrier. Transceiver problem?


 
Odgovor na temu

MarijanKo
Marijan Kovacevic
USSteel Serbia
Beograd

Član broj: 41490
Poruke: 165
*.bg.wifi.vline.verat.net.



Profil

icon Re: Cisco Router i Windows RAS problemi03.04.2005. u 23:32 - pre 231 meseci
vidi vraga slican problem.. :)
I ja ne mogu da povezem ADSl ruter na windowsov RAS.. jednostavno paketi nece da izadju sa LAN-a samo sto mi moj problem lici tako mali kad vidim ovoliko velike log fajlove kod tebe.

Promeni ruter :)
Ili promeni OS :)
 
Odgovor na temu

nenadgro

Član broj: 15054
Poruke: 30
*.cytanet.com.cy.



Profil

icon Re: Cisco Router i Windows RAS problemi04.04.2005. u 09:51 - pre 231 meseci
Hm da... Nije bilo potrebe za isdn debug-om, deluje da ISDN prodje kako treba ali PPP odbija da radi.

Nemam sad u blizini neki Win RAS da probam, ali mozes li ti da vidis nesto u logu na Win serveru?
 
Odgovor na temu

djk494

Član broj: 494
Poruke: 320
195.252.81.*



+39 Profil

icon Re: Cisco Router i Windows RAS problemi04.04.2005. u 13:20 - pre 231 meseci
Ma ne znam vise pobrisao sam sve druge auth protokole sa windowsa ostavio sam samo pap, u windows logu se ne pojavljuje nista.
Mislim da je u pitanju neki od parametara koji treba da se definise na Cisco-u jer ga ne dobija od windows RAS-a, ostaje ne vezi koliko mu je NCP timeout...
 
Odgovor na temu

luke6

Član broj: 337493
Poruke: 2
123.24.56.*



Profil

icon Re: Cisco Router i Windows RAS problemi06.11.2017. u 08:01 - pre 77 meseci
Ez segíthet megoldani a router problémáját: 192.168.0.1
 
Odgovor na temu

[es] :: Enterprise Networking :: Cisco Router i Windows RAS problemi

[ Pregleda: 5886 | Odgovora: 6 ] > FB > Twit

Postavi temu Odgovori

Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.