Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cisco VPN 3005 Concentrator - configuration tips?

Status
Not open for further replies.

endtinger

Technical User
Feb 5, 2001
1
0
0
CH
we have a problem to configure a cisco 3005 for vpn access. the vpn is in parrallel to the firewall, so the problems shoulodn't be from there. I have connected the external interface directly to the internet (via cable and a cisco 2500) the private interface directly to the lan. I can ping and admin the vpn device from inside and outside. I have used the sample configuration from ciscos website to establish a vpn connection over PPTP with internal user and PAP authetification without encryption. Any variations in routingtables and/or clientadress managment doesn't change anything. As client I used a w2k worstation with lan access to the internet and get the folloeing error on w2K:

"error 619: to the given port no connection is established."

the vpn event log says:

**********************************************************

1 02/05/2001 11:57:52.720 SEV=8 PPTPDBG/20 RPT=13
Accept connection on socket 12

2 02/05/2001 11:57:52.720 SEV=8 PPTPDBG/26 RPT=13
pptp_create_ptcb: for 212.243.131.253

3 02/05/2001 11:57:52.720 SEV=7 PPTPDBG/2 RPT=13 212.243.131.253
TCP up: peer 212.243.131.253, socket 12, ptcb 1c3f9a0

4 02/05/2001 11:57:56.010 SEV=9 PPTPDBG/21 RPT=61
pptp_sock_accept_cb: from 212.243.131.253 (12), buf_desc 1184000, abort 0

5 02/05/2001 11:57:56.010 SEV=9 PPTPDBG/13 RPT=58
pptp_parse_pkt: Start-Control-Connection-Request from 212.243.131.253 (1c3f9a0)

6 02/05/2001 11:57:56.010 SEV=9 PPTPDBG/23 RPT=46
pptp_sock_send: from 212.243.131.253 (1c3f9a0), socket 12, buf_desc 1184000

7 02/05/2001 11:57:56.010 SEV=4 PPTP/47 RPT=77 212.243.131.253
Tunnel to peer 212.243.131.253 established

8 02/05/2001 11:57:56.110 SEV=9 PPTPDBG/21 RPT=62
pptp_sock_accept_cb: from 212.243.131.253 (12), buf_desc 11b7800, abort 0

9 02/05/2001 11:57:56.110 SEV=9 PPTPDBG/13 RPT=59
pptp_parse_pkt: Outgoing-Call-Request from 212.243.131.253 (1c3f9a0)

10 02/05/2001 11:57:56.110 SEV=7 PPTPDBG/14 RPT=37
pptp_get_ids: local -1, peer 32768

11 02/05/2001 11:57:56.110 SEV=8 PPTPDBG/29 RPT=13
pptp_create_pscb: for 212.243.131.253, id 32768

12 02/05/2001 11:57:56.110 SEV=8 PPTPDBG/16 RPT=25
pptp_rm_request_id: type 5, userptr 1c3d644

13 02/05/2001 11:57:56.110 SEV=8 PPTPDBG/15 RPT=85
pptp_rm_resp_cb: 1177/0/5/0/1c3d644

14 02/05/2001 11:57:56.110 SEV=7 PPTPDBG/6 RPT=25
RM allocated id 1177 for resource 5 for 1c3d644

15 02/05/2001 11:57:56.110 SEV=8 PPTPDBG/17 RPT=25
pptp_rm_request_res: type 5, id 1177, userptr 1c3d644

16 02/05/2001 11:57:56.110 SEV=8 PPTPDBG/15 RPT=86
pptp_rm_resp_cb: 1177/1/5/0/1c3d644

17 02/05/2001 11:57:56.110 SEV=7 PPTPDBG/8 RPT=25
RM allocated resource 5 (id 1177) for 1c3d644

18 02/05/2001 11:57:56.110 SEV=7 PPTPDBG/11 RPT=37
pptp_dm_send_ctrl: to ip id 1177

19 02/05/2001 11:57:56.110 SEV=7 PPTPDBG/11 RPT=38
pptp_dm_send_ctrl: to gre id 1177

20 02/05/2001 11:57:56.110 SEV=8 PPTPDBG/16 RPT=26
pptp_rm_request_id: type 8, userptr 1c3d644

21 02/05/2001 11:57:56.110 SEV=8 PPTPDBG/15 RPT=87
pptp_rm_resp_cb: 1178/0/8/0/1c3d644

22 02/05/2001 11:57:56.110 SEV=7 PPTPDBG/6 RPT=26
RM allocated id 1178 for resource 8 for 1c3d644

23 02/05/2001 11:57:56.110 SEV=8 PPTPDBG/17 RPT=26
pptp_rm_request_res: type 8, id 1178, userptr 1c3d644

24 02/05/2001 11:57:56.110 SEV=8 PPTPDBG/15 RPT=88
pptp_rm_resp_cb: 1178/1/8/0/1c3d644

25 02/05/2001 11:57:56.110 SEV=7 PPTPDBG/8 RPT=26
RM allocated resource 8 (id 1178) for 1c3d644

26 02/05/2001 11:57:56.110 SEV=7 PPTPDBG/11 RPT=39
pptp_dm_send_ctrl: to gre id 1177

27 02/05/2001 11:57:56.110 SEV=9 PPTPDBG/23 RPT=47
pptp_sock_send: from 212.243.131.253 (1c3f9a0), socket 12, buf_desc 11a1800

28 02/05/2001 11:57:56.110 SEV=4 PPTP/42 RPT=77 212.243.131.253
Session started on tunnel 212.243.131.253

29 02/05/2001 11:57:56.160 SEV=9 PPTPDBG/21 RPT=63
pptp_sock_accept_cb: from 212.243.131.253 (12), buf_desc 11a1800, abort 0

30 02/05/2001 11:57:56.160 SEV=9 PPTPDBG/13 RPT=60
pptp_parse_pkt: Set-Link-Info from 212.243.131.253 (1c3f9a0)

31 02/05/2001 11:57:56.160 SEV=7 PPTPDBG/14 RPT=38
pptp_get_ids: local 261, peer -1

32 02/05/2001 11:58:32.110 SEV=8 PPTPDBG/15 RPT=89
pptp_rm_resp_cb: 1178/2/8/0/1c3d644

33 02/05/2001 11:58:32.110 SEV=7 PPTPDBG/9 RPT=37
RM deallocated resource 8 (id 1178) for 1c3d644

34 02/05/2001 11:58:32.110 SEV=9 PPTPDBG/23 RPT=48
pptp_sock_send: from 212.243.131.253 (1c3f9a0), socket 12, buf_desc 10f2800

35 02/05/2001 11:58:32.110 SEV=7 PPTPDBG/32 RPT=28 212.243.131.253
Session FSM unexpected event: peer addr 212.243.131.253 (peer 32768, loc 261, se
r 36706), state 8, event 19

37 02/05/2001 11:58:32.170 SEV=9 PPTPDBG/21 RPT=64
pptp_sock_accept_cb: from 212.243.131.253 (12), buf_desc 10de800, abort 0

38 02/05/2001 11:58:32.170 SEV=9 PPTPDBG/13 RPT=61
pptp_parse_pkt: Call-Disconnect-Notify from 212.243.131.253 (1c3f9a0)

39 02/05/2001 11:58:32.170 SEV=7 PPTPDBG/14 RPT=39
pptp_get_ids: local -1, peer 32768

40 02/05/2001 11:58:32.170 SEV=8 PPTPDBG/19 RPT=25
pptp_rm_free_res: type 8, id 1178, userptr 1c3d644

41 02/05/2001 11:58:32.170 SEV=8 PPTPDBG/15 RPT=90
pptp_rm_resp_cb: 1178/2/8/0/1c3d644

42 02/05/2001 11:58:32.170 SEV=7 PPTPDBG/9 RPT=38
RM deallocated resource 8 (id 1178) for 1c3d644

43 02/05/2001 11:58:32.170 SEV=7 PPTPDBG/32 RPT=29 212.243.131.253
Session FSM unexpected event: peer addr 212.243.131.253 (peer 32768, loc 261, se
r 36706), state 9, event 26

45 02/05/2001 11:58:32.170 SEV=8 PPTPDBG/18 RPT=25
pptp_rm_free_id: id 1178

46 02/05/2001 11:58:32.170 SEV=4 PPTP/35 RPT=77 212.243.131.253
Session closed on tunnel 212.243.131.253 (peer 32768, local 261, serial 36706),
reason: Error (No additional info)

48 02/05/2001 11:58:32.170 SEV=8 PPTPDBG/28 RPT=13
pptp_drive_sfsm: term 212.243.131.253 (1c3f9a0) 32768/261/36706 (1c3d644)

49 02/05/2001 11:58:32.170 SEV=8 PPTPDBG/30 RPT=13
pptp_delete_pscb: for 212.243.131.253 (1c3d644), 32768/261/36706

50 02/05/2001 11:58:32.360 SEV=9 PPTPDBG/21 RPT=65
pptp_sock_accept_cb: from 212.243.131.253 (12), buf_desc 11ba000, abort 0

51 02/05/2001 11:58:32.360 SEV=9 PPTPDBG/13 RPT=62
pptp_parse_pkt: Stop-Control-Connection-Request from 212.243.131.253 (1c3f9a0)

52 02/05/2001 11:58:32.360 SEV=9 PPTPDBG/23 RPT=49
pptp_sock_send: from 212.243.131.253 (1c3f9a0), socket 12, buf_desc 11ba000

53 02/05/2001 11:58:32.360 SEV=8 PPTPDBG/24 RPT=22
Close socket for 212.243.131.253 (0)

54 02/05/2001 11:58:32.360 SEV=7 PPTPDBG/22 RPT=13
pptp_sock_close_cb: from 212.243.131.253 (12)

55 02/05/2001 11:58:32.360 SEV=8 PPTPDBG/19 RPT=26
pptp_rm_free_res: type 5, id 1177, userptr 1c3f9a0

56 02/05/2001 11:58:32.360 SEV=8 PPTPDBG/15 RPT=91
pptp_rm_resp_cb: 1177/2/5/0/1c3f9a0

57 02/05/2001 11:58:32.360 SEV=7 PPTPDBG/9 RPT=39
RM deallocated resource 5 (id 1177) for 1c3f9a0

58 02/05/2001 11:58:32.360 SEV=8 PPTPDBG/18 RPT=26
pptp_rm_free_id: id 1177

59 02/05/2001 11:58:32.360 SEV=8 PPTPDBG/24 RPT=23
Close socket for 212.243.131.253 (0)

60 02/05/2001 11:58:32.370 SEV=4 PPTP/34 RPT=77 212.243.131.253
Tunnel to peer 212.243.131.253 closed, reason: None (No additional info)

61 02/05/2001 11:58:32.370 SEV=8 PPTPDBG/27 RPT=13 212.243.131.253
pptp_delete_ptcb: for 212.243.131.253 (1c3f9a0), try 0

**********************************************************


second client is a macintosh using NTS TunnelBuilder Clientsoftware for VPNs (PPTP and L2TP). The errormessages on the vpn are similar (no additional info...). On the mac the error is: LCP: VPN Server is not responding to configure request. First it seems that the tunnel is established (TCP and PPTP requests are negotiated the the server drops the connection).

Anyone out there any ideas where I can seek the failure or where I can get further information about configuring?

Thanks Andreas

 
Well on the Mac if it is failing in the LCP area, Your problems could be different. For the log I would check your vpn server. It seems like from the capture resources are not being allocated. Could be configuration, could be hardware or bug. You would have to capture more info or log more. But if you Mac is not getting past the lcp area then the problem is most likely config on the mac part. Question:is your ppp configured correctly after the tunnel is terminated ppp is suppose to terminate as well.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top