pptp - Peer rejects authentication

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 - Peer rejects authentication

Beitrag von joeMJ »

Hallo,

da ich mit ipsecuritas weder eine vernünftige Verbindung hinbekomme noch anderweitige Clients bekannt sind, mit denen ich sprechen kann versuche ich zunächst mal pptp abgehend von Mac OS.

PAP ist mir zu unsicher, CHAP hätt' ich dann wenigstens schon gerne, ich schrei' ungerne ein Kennwort durch die Landschaft... CHAP hab' ich dann auch unter Kommunikation/Gegenstellen drin, aber er ignoriert mich irgendwie?

tr + ppp:

Code: Alles auswählen

80-254-74-149:~ joe$ ssh root@private.tralala.biz
root@private.tralala.biz's password:  


#
| LANCOM 1821+ Wireless ADSL (Ann.B)
| Ver. 7.58.0045 / 14.11.2008 / 6.26b/E74.02.54
| SN.  076781800045
| Copyright (c) LANCOM Systems

KR-JR001, Connection No.: 002 (WAN)


root@KR-JR001:/
> tr + ppp
PPP             ON 

root@KR-JR001:/
> 
[PPP] 2008/11/27 17:12:12,110

LCP polling timeout for peer AR-PIPE - echo-response received during last interval
Sending LCP echo-request with ID 06 and length 8 to peer AR-PIPE (channel 1)


[PPP] 2008/11/27 17:12:12,110

Received LCP frame from peer AR-PIPE (channel 1)

LCP echo-response with ID 06 and length 10 to peer AR-PIPE


[PPP] 2008/11/27 17:12:12,690
PPTP control channel: connect from 80.254.74.149


[PPP] 2008/11/27 17:12:12,700
PPTP control channel: received StartControlConnectionRequest message
PPTP control channel: StartControlConnectionReply sent


[PPP] 2008/11/27 17:12:12,760
Change phase to ESTABLISH
Lower-Layer-Up event for LCP
Initializing LCP restart timer to 3000 milliseconds
Waiting up to 3000ms for connection
Starting LCP restart timer with 3000 milliseconds


[PPP] 2008/11/27 17:12:12,750
PPTP call control: received OutgoingCallRequest for call id 274
PPTP call control: set remote window to 32 for DEFAULT
PPTP call control: OutgoingCallReply sent for call id 64558
PPTP call control: SetLinkInfo sent for call id 64558 with SendACCM=0x00000000 and ReceiveACCM=0x00000000
PPTP call control: connect indication for PPP sent


[PPP] 2008/11/27 17:12:12,820
PPTP call control: received SetLinkInfo for call id 64558 with SendACCM=0xffffffff, ReceiveACCM=0xffffffff


[PPP] 2008/11/27 17:12:12,840

Received LCP frame from peer DEFAULT (channel 0)
Stop waiting for connection
Stopping LCP restart timer
Initializing LCP restart timer to 3000 milliseconds
Generating LCP configure-request for peer DEFAULT
Inserting local MRU 1460
Inserting local authentication protocol PAP
Inserting local magic number 4f8cbf50
Sending LCP configure-request with ID 00 and length 18 to peer DEFAULT (channel 0)
Starting LCP restart timer with 3000 milliseconds
Evaluate configure-request with ID 01 and size 20
Peer ACCM 00000000000000000000000000000000, accepted
Peer magic number a1b9a7ad accepted
Peer requests protocol field compression, rejected
Peer requests address- and controlfield compression, rejected
Negative Configure-Request-Received event for LCP
Sending LCP configure-reject with ID 01 and length 8 to peer DEFAULT (channel 0)


[PPP] 2008/11/27 17:12:12,940

Received LCP frame from peer DEFAULT (channel 0)
Evaluate configure-nak with ID 00 and size 9
Peer NAKs for authentication protocol c223, ignore NAK
Configure-Nak/Rej-Received event for LCP
Initializing LCP restart timer to 3000 milliseconds
Generating LCP configure-request for peer DEFAULT
Inserting local MRU 1460
Inserting local authentication protocol PAP
Inserting local magic number 4f8cbf50
Sending LCP configure-request with ID 02 and length 18 to peer DEFAULT (channel 0)
Starting LCP restart timer with 3000 milliseconds


[PPP] 2008/11/27 17:12:13,000

Received LCP frame from peer DEFAULT (channel 0)
Evaluate configure-request with ID 02 and size 16
Peer ACCM 00000000000000000000000000000000, accepted
Peer magic number a1b9a7ad accepted
Positive Configure-Request-Received event for LCP
Sending LCP configure-ack with ID 02 and length 16 to peer DEFAULT (channel 0)


[PPP] 2008/11/27 17:12:13,000

Received LCP frame from peer DEFAULT (channel 0)
Evaluate configure-nak with ID 02 and size 9
Peer NAKs for authentication protocol c223, ignore NAK
Configure-Nak/Rej-Received event for LCP
Initializing LCP restart timer to 3000 milliseconds
Generating LCP configure-request for peer DEFAULT
Inserting local MRU 1460
Inserting local authentication protocol PAP
Inserting local magic number 4f8cbf50
Sending LCP configure-request with ID 04 and length 18 to peer DEFAULT (channel 0)
Starting LCP restart timer with 3000 milliseconds


[PPP] 2008/11/27 17:12:13,050

Received LCP frame from peer DEFAULT (channel 0)
Evaluate configure-nak with ID 04 and size 9
Peer NAKs for authentication protocol c223, ignore NAK
Configure-Nak/Rej-Received event for LCP
Initializing LCP restart timer to 3000 milliseconds
Generating LCP configure-request for peer DEFAULT
Inserting local MRU 1460
Inserting local authentication protocol PAP
Inserting local magic number 4f8cbf50
Sending LCP configure-request with ID 05 and length 18 to peer DEFAULT (channel 0)
Starting LCP restart timer with 3000 milliseconds


[PPP] 2008/11/27 17:12:13,100

Received LCP frame from peer DEFAULT (channel 0)
Evaluate configure-nak with ID 05 and size 9
Peer NAKs for authentication protocol c223, ignore NAK
Configure-Nak/Rej-Received event for LCP
Initializing LCP restart timer to 3000 milliseconds
Generating LCP configure-request for peer DEFAULT
Inserting local MRU 1460
Inserting local authentication protocol PAP
Inserting local magic number 4f8cbf50
Sending LCP configure-request with ID 06 and length 18 to peer DEFAULT (channel 0)
Starting LCP restart timer with 3000 milliseconds


[PPP] 2008/11/27 17:12:13,160

Received LCP frame from peer DEFAULT (channel 0)
Evaluate configure-nak with ID 06 and size 9
Peer NAKs for authentication protocol c223, ignore NAK
Configure-Nak/Rej-Received event for LCP
Initializing LCP restart timer to 3000 milliseconds
Generating LCP configure-request for peer DEFAULT
Inserting local MRU 1460
Inserting local authentication protocol PAP
Inserting local magic number 4f8cbf50
Sending LCP configure-request with ID 07 and length 18 to peer DEFAULT (channel 0)
Starting LCP restart timer with 3000 milliseconds


[PPP] 2008/11/27 17:12:13,220

Received LCP frame from peer DEFAULT (channel 0)
Evaluate configure-reject with ID 07 and size 8
Peer rejects authentication
Administrativ-Close event for LCP
Initializing LCP restart timer to 3000 milliseconds
Change phase to TERMINATE
Sending LCP terminate-request with ID 08 and length 4 to peer DEFAULT (channel 0)
Starting LCP restart timer with 3000 milliseconds


[PPP] 2008/11/27 17:12:13,270

Received LCP frame from peer DEFAULT (channel 0)
Terminate-Ack-Received event for LCP
Stopping LCP restart timer
This-Layer-Finish action for LCP
Disconnecting because LCP was finished


[PPP] 2008/11/27 17:12:13,280
Change phase to DEAD
Stopping LCP restart timer
Stopping IPXCP restart timer
Stopping IPCP restart timer
Stopping CCP restart timer
Stopping BACP restart timer


[PPP] 2008/11/27 17:12:13,280
PPTP call control: DisconnectNotify sent for call id 64558
PPTP call control: disconnected call id 64558


[PPP] 2008/11/27 17:12:13,290
PPTP: Error: Auth.-rejected (0x8002) for DEFAULT (80.254.74.149)

[PPP] 2008/11/27 17:12:13,310
PPTP call control: call destroyed


[PPP] 2008/11/27 17:12:13,310
PPTP control channel: closing TCP connection


[PPP] 2008/11/27 17:12:13,310
PPTP control channel: TCP connection closed
PPTP control channel: TCP job destroyed
Cheers,
Joe
backslash
Moderator
Moderator
Beiträge: 7127
Registriert: 08 Nov 2004, 21:26
Wohnort: Aachen

Beitrag von backslash »

Hi joeMJ,

damit das LANCOM von Anfang an CHAP fordert, mußt du in der PPP-Tabelle beim DEFAULT-Eintrag die Authentifizierung von PAP auf CHAP umschalten. Das ist aber letztendlich egal, solange der Client PAP nicht akzeptiert - was hier eh der Fall ist. Der Client fordert MSCHAPv2, was vom LANCOM z.Zt nicht unterstützt wird (kommt mit der 7.60)...

Du mußt dem Client also sagen, daß er entweder MSCHAP oder CHAP-MD5 akzeptieren soll... Das hilft dir aber noch nicht weiter, denn du ihm auch noch sagen, daß unverschlüsselt arbeiten soll.

Gruß
Backslash
Benutzeravatar
tbc233
Beiträge: 350
Registriert: 01 Feb 2005, 21:56

Beitrag von tbc233 »

Zwischenfrage (schon allein weil ich pptp für sehr unbefriedigend halten würde, selbst wenn du es hinkriegst):

hast du mal den vpntracker probiert? Dessen Kompatibilitätsliste enhält sogar das Lancom Logo.

http://www.equinux.com/de/products/vpnt ... ility.html
Liebe Grüße,
michael
Antworten