PPTP PPP Trace verstehen

Forum zum Thema allgemeinen Fragen zu VPN

Moderator: Lancom-Systems Moderatoren

Antworten
Benutzeravatar
joeMJ
Beiträge: 359
Registriert: 18 Feb 2005, 21:03
Wohnort: Krefeld/NRW
Kontaktdaten:

PPTP PPP Trace verstehen

Beitrag von joeMJ »

Moin,

auch wenn ich PPTP nicht als VPN sehe, wurde per Order von oben entschieden, eine S2S Anbindung bereitzustellen. Ich kann nix machen. Der LC scheint meiner Meinung zu sein und die Verbindung schlägt fehl. Ich bekomme die Info, mit Windows PPTP würde es gehen.

Ich habe in //Kommunikation/Protokolle in PPTP und PPP Liste konfiguriert und einen passenden Eintrag in der IPv4Routingtabelle erstellt. Der LC hängt an einem Standard CoCo. Schaue ich jetzt in's Trace, kommt keine Verbindung zustande. Kann mir jemand mit dem Trace helfen?

Zunächst sagt Peer folgendes:

Peer requests authentication protocol CHAP with DES encryption (MS-CHAPv2), no protocol available

OK, mache ich also MS-CHAPv2.

Dann trace ich nochmal, verstehe aber LCP nicht, dass der zumachen möchte. Warum?

Also:

Code: Alles auswählen

[PPP] 2014/01/29 16:42:22,101  Devicetime: 2014/01/29 16:42:23,327

Received IPCP frame from peer PPTPSERVER (channel 0)
Evaluate configure-reject with ID 00 and size 10
Peer rejects secondary DNS address , discard local option
Configure-Nak/Rej-Received event for IPCP
Initializing IPCP restart timer to 3000 milliseconds
Generating IPCP configure-request for peer PPTPSERVER
Inserting IP address 0.0.0.0
Inserting primary DNS address 0.0.0.0
Sending IPCP configure-request with ID 02 and length 16 to peer PPTPSERVER (channel 0)
Starting IPCP restart timer with 3000 milliseconds

[PPP] 2014/01/29 16:42:22,243  Devicetime: 2014/01/29 16:42:23,366

Received IPCP frame from peer PPTPSERVER (channel 0)
Evaluate configure-request with ID 73 and size 10
Peer requests IP address 192.168.182.252, accepted
Positive Configure-Request-Received event for IPCP
Sending IPCP configure-ack with ID 73 and length 10 to peer PPTPSERVER (channel 0)

[PPP] 2014/01/29 16:42:22,243  Devicetime: 2014/01/29 16:42:23,383

Received LCP frame from peer PPTPSERVER (channel 0)
Terminate-Request-Received event for LCP

[PPP] 2014/01/29 16:42:22,243  Devicetime: 2014/01/29 16:42:23,384
This-Layer-Down action for LCP
Lower-Layer-Down event for IPV6CP
Stopping IPV6CP restart timer
Lower-Layer-Down event for BACP
Stopping BACP restart timer
Lower-Layer-Down event for CCP
Stopping CCP restart timer
Lower-Layer-Down event for IPCP
Stopping IPCP restart timer
Lower-Layer-Down event for IPXCP
Stopping IPXCP restart timer
Resetting LCP restart timer with 3000 milliseconds
Change phase to TERMINATE for PPTPSERVER
Sending LCP terminate-request with ID 04 and length 4 to peer PPTPSERVER (channel 0)
Starting LCP restart timer with 3000 milliseconds
Sending LCP terminate-ack with ID 4d and length 4 to peer PPTPSERVER (channel 0)

[PPP] 2014/01/29 16:42:22,243  Devicetime: 2014/01/29 16:42:23,386
Change phase to DEAD for PPTPSERVER
Stopping LCP restart timer
Stopping IPCP restart timer
Stopping CCP restart timer
Stopping BACP restart timer
Stopping IPV6CP restart timer

[PPP] 2014/01/29 16:42:22,243  Devicetime: 2014/01/29 16:42:23,392
selecting first remote gateway using strategy eFirst for PPTPSERVER
     => CurrIdx=0, IpStr=>ZIELIP<, IpAddr=ZIELIP, IpTtl=0s

[PPP] 2014/01/29 16:42:22,243  Devicetime: 2014/01/29 16:42:23,387
PPTP call control: closing call for PPTPSERVER

[PPP] 2014/01/29 16:42:22,243  Devicetime: 2014/01/29 16:42:23,400
PPTP call control: call destroyed for PPTPSERVER

[PPP] 2014/01/29 16:42:22,243  Devicetime: 2014/01/29 16:42:23,401
PPTP control channel: closing TCP connection to ZIELIP

[PPP] 2014/01/29 16:42:22,243  Devicetime: 2014/01/29 16:42:23,401
PPTP control channel: TCP connection to ZIELIP closed

[PPP] 2014/01/29 16:42:23,813  Devicetime: 2014/01/29 16:42:23,828
PPTP dispatcher: received GRE packet for unknown call id 5802 from ZIELIP - packet dropped

[PPP] 2014/01/29 16:42:23,813  Devicetime: 2014/01/29 16:42:23,856
PPTP dispatcher: received GRE packet for unknown call id 5802 from ZIELIP - packet dropped

[PPP] 2014/01/29 16:42:23,813  Devicetime: 2014/01/29 16:42:24,393
PPTP control channel: connecting to PPTPSERVER (ZIELIP)
PPTP control channel: waiting for TCP connect for PPTPSERVER (ZIELIP)
PPTP control channel: use local port: 12840 for PPTPSERVER

[PPP] 2014/01/29 16:42:24,018  Devicetime: 2014/01/29 16:42:24,956
PPTP control channel: TCP connection to ZIELIP established
PPTP control channel: StartControlConnectionRequest sent to ZIELIP

[PPP] 2014/01/29 16:42:24,520  Devicetime: 2014/01/29 16:42:25,577
PPTP control channel: received StartControlConnectionReply from ZIELIP
PPTP call control: OutgoingCallRequest sent for call id 5259 to ZIELIP

[PPP] 2014/01/29 16:42:24,740  Devicetime: 2014/01/29 16:42:25,909
PPTP dispatcher: received GRE packet for PPTPSERVER, call id 5259 in call state CALL - packet dropped

[PPP] 2014/01/29 16:42:24,740  Devicetime: 2014/01/29 16:42:25,909
Change phase to ESTABLISH for PPTPSERVER
Lower-Layer-Up event for LCP
Initializing LCP restart timer to 3000 milliseconds
Waiting up to 200ms for connection
Starting LCP restart timer with 200 milliseconds

[PPP] 2014/01/29 16:42:24,740  Devicetime: 2014/01/29 16:42:25,909
PPTP call control: received OutgoingCallReply from ZIELIP for call id 5259: peer call id 4633
PPTP call control: SetLinkInfo sent for call id 5259 to ZIELIP with SendACCM=0x00000000 and ReceiveACCM=0x00000000
PPTP call control: set remote window to 8 for PPTPSERVER
PPTP call control: connect request for PPP sent

[PPP] 2014/01/29 16:42:24,929  Devicetime: 2014/01/29 16:42:26,100
Positive Restart-Timeout event for LCP
Stop waiting for connection
Initializing LCP restart timer to 3000 milliseconds
Generating LCP configure-request for peer PPTPSERVER
Inserting local MRU 1460
Inserting local magic number bd0be844
Sending LCP configure-request with ID 00 and length 14 to peer PPTPSERVER (channel 0)
Starting LCP restart timer with 3000 milliseconds

[TraceStopped] 2014/01/29 16:42:25,070
Used config:
# Trace config
trace + PPP
Cheers,
Joe
backslash
Moderator
Moderator
Beiträge: 7129
Registriert: 08 Nov 2004, 21:26
Wohnort: Aachen

Re: PPTP PPP Trace verstehen

Beitrag von backslash »

Hi joeMJ,

es ist sinnvoller, den *ganzen* PPP-Trace zu posten...

ich vermute aber, daß die Gegensteite die Verbindung ablehnt, weil du die Verschlüsselung nicht aktiviert hast - da wäre vermutlich vorher im Trace zu sehen gewesen, daß die Gegenseite dir ein CCP-Paket schickt, was dein LANCOM ablehnt...

Gruß
Backslash
Benutzeravatar
joeMJ
Beiträge: 359
Registriert: 18 Feb 2005, 21:03
Wohnort: Krefeld/NRW
Kontaktdaten:

Re: PPTP PPP Trace verstehen

Beitrag von joeMJ »

^^VOLLTREFFER^^
... suche noch das *facepalm* icon. Es fehlte tatsächlich die Einstellung für MPPE in der PPTP-Liste. Das verworfene GRE-Paket habe ich in ein zwei Versuchen vorher tatsächlich gesehen. :oops:

Danke!
Cheers,
Joe
Antworten