USR8000A-02 + Verizon DSL -- Can't VPN?

Forum General Networking : VPN, VoIP, Video Conferencing, Remote Connections - USR8000A-02 + Verizon DSL -- Can't VPN?

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

Archived from groups: comp.dcom.vpn (More info?)

 

I have the following situation and cannot establish a VPN tunnel
connection from my home workstation to my office network.

W2K Pro->Cisco VPN Client->USR8000A-02 NAT Router/Firewall->Verizon DSL

Can someone explain the steps to get this working?

I have the URS8000A-02 Broadband Router set with these settings:

* Version 2.7 of the software
* MAC Address Control - Clients with certain MAC address can connect to
the router; others are denied
* PPPoE to Verizon
* PPPoE settings say 0.0.0.0 for "Assigned IP Address"
* Verizon grants me an IP address upon connection. It's dynamic, not
static.

This permits me to browse and use the Internet with no issues
sending/receiving email, web surfing, etc.

I have the Cisco VPN Client set with these settings:

* Transparent Tunneling
* Tried UDP version -- this at least gives me a popup login dialog but
then the login fails with error 414 that username cannot be
authenticated
* Tried TCP version on 10000 per my company's instructions -- this
bombs without a popup login dialog after a long delay, complaining
about 414 error
* Tried TCP version on 443 -- this gives me a popup login dialog but
fails on 414
* Tried above with "Local LAN Access" checked and unchecked

My thoughts are that if I at least get the popup login dialog, then the
VPN is working right except that maybe the company messed up my login??
Do you think the problem is perhaps that my username is not what I
think it is?

Sponsored Links
Register or log in to remove.

Archived from groups: comp.dcom.vpn (More info?)

 

HA! Turns out my ID was disabled for some reason. My admin re-enabled
it and I will test again tonight.

Reply to Anonymous

Archived from groups: comp.dcom.vpn (More info?)

 

Nope. Turns out that I've got more problems than this in getting
connected. I'm still stuck with the same errors. Please somebody help?

Cisco Systems VPN Client Version 4.0.3 (Rel)
Copyright (C) 1998-2003 Cisco Systems, Inc. All Rights Reserved.
Client Type(s): Windows, WinNT
Running on: 5.0.2195

40 21:19:18.096 03/01/05 Sev=Info/4 CM/0x63100002
Begin connection process

41 21:19:18.106 03/01/05 Sev=Info/4 CM/0x63100004
Establish secure connection using Ethernet

42 21:19:18.106 03/01/05 Sev=Info/4 CM/0x63100024
Attempt connection with server "rook01.rook1.com"

43 21:19:18.106 03/01/05 Sev=Info/6 IKE/0x6300003B
Attempting to establish a connection with 178.240.220.13.

44 21:19:18.176 03/01/05 Sev=Info/4 IKE/0x63000013
SENDING >>> ISAKMP OAK AG (SA, KE, NON, ID, VID(Xauth), VID(dpd),
VID(Nat-T), VID(Frag), VID(Unity)) to 178.240.220.13

45 21:19:18.507 03/01/05 Sev=Info/5 IKE/0x6300002F
Received ISAKMP packet: peer = 178.240.220.13

46 21:19:18.507 03/01/05 Sev=Info/4 IKE/0x63000014
RECEIVING <<< ISAKMP OAK AG (SA, KE, NON, ID, HASH, VID(Unity),
VID(Xauth), VID(dpd), VID(Frag), VID(?), VID(?)) from 178.240.220.13

47 21:19:18.507 03/01/05 Sev=Info/5 IKE/0x63000001
Peer is a Cisco-Unity compliant peer

48 21:19:18.507 03/01/05 Sev=Info/5 IKE/0x63000001
Peer supports XAUTH

49 21:19:18.507 03/01/05 Sev=Info/5 IKE/0x63000001
Peer supports DPD

50 21:19:18.507 03/01/05 Sev=Info/5 IKE/0x63000001
Peer supports IKE fragmentation payloads

51 21:19:18.507 03/01/05 Sev=Info/5 IKE/0x63000001
Peer supports DWR Code and DWR Text

52 21:19:18.587 03/01/05 Sev=Info/6 IKE/0x63000001
IOS Vendor ID Contruction successful

53 21:19:18.587 03/01/05 Sev=Info/4 IKE/0x63000013
SENDING >>> ISAKMP OAK AG *(HASH, NOTIFY:STATUS_INITIAL_CONTACT,
VID(?), VID(Unity)) to 178.240.220.13

54 21:19:18.587 03/01/05 Sev=Info/4 IKE/0x63000082
IKE Port in use - Local Port = 0x01F4, Remote Port = 0x01F4

55 21:19:18.587 03/01/05 Sev=Info/4 CM/0x6310000E
Established Phase 1 SA. 1 Crypto Active IKE SA, 0 User Authenticated
IKE SA in the system

56 21:19:18.687 03/01/05 Sev=Info/5 IKE/0x6300002F
Received ISAKMP packet: peer = 178.240.220.13

57 21:19:18.687 03/01/05 Sev=Info/4 IKE/0x63000014
RECEIVING <<< ISAKMP OAK TRANS *(HASH, ATTR) from 178.240.220.13

58 21:19:18.687 03/01/05 Sev=Info/4 CM/0x63100015
Launch xAuth application

59 21:19:18.847 03/01/05 Sev=Info/4 IPSEC/0x63700008
IPSec driver successfully started

60 21:19:18.847 03/01/05 Sev=Info/4 IPSEC/0x63700014
Deleted all keys

61 21:19:24.165 03/01/05 Sev=Info/4 CM/0x63100017
xAuth application returned

62 21:19:24.165 03/01/05 Sev=Info/4 IKE/0x63000013
SENDING >>> ISAKMP OAK TRANS *(HASH, ATTR) to 178.240.220.13

63 21:19:26.278 03/01/05 Sev=Info/5 IKE/0x6300002F
Received ISAKMP packet: peer = 178.240.220.13

64 21:19:26.278 03/01/05 Sev=Info/4 IKE/0x63000014
RECEIVING <<< ISAKMP OAK TRANS *(HASH, ATTR) from 178.240.220.13

65 21:19:26.278 03/01/05 Sev=Info/4 IKE/0x63000013
SENDING >>> ISAKMP OAK TRANS *(HASH, ATTR) to 178.240.220.13

66 21:19:26.278 03/01/05 Sev=Info/4 IKE/0x63000017
Marking IKE SA for deletion (I_Cookie=84BF4E8E132F71A8
R_Cookie=42DB78B693499CFF) reason = DEL_REASON_WE_FAILED_AUTH

67 21:19:26.278 03/01/05 Sev=Info/4 IKE/0x63000013
SENDING >>> ISAKMP OAK INFO *(HASH, DWR) to 178.240.220.13

68 21:19:26.388 03/01/05 Sev=Info/5 IKE/0x6300002F
Received ISAKMP packet: peer = 178.240.220.13

69 21:19:26.388 03/01/05 Sev=Info/4 IKE/0x63000057
Received an ISAKMP message for a non-active SA,
I_Cookie=84BF4E8E132F71A8 R_Cookie=42DB78B693499CFF

70 21:19:26.388 03/01/05 Sev=Info/4 IKE/0x63000014
RECEIVING <<< ISAKMP OAK INFO *(Dropped) from 178.240.220.13

71 21:19:26.839 03/01/05 Sev=Info/4 IKE/0x6300004A
Discarding IKE SA negotiation (I_Cookie=84BF4E8E132F71A8
R_Cookie=42DB78B693499CFF) reason = DEL_REASON_WE_FAILED_AUTH

72 21:19:26.839 03/01/05 Sev=Info/4 CM/0x63100014
Unable to establish Phase 1 SA with server "rook01.rook1.com" because
of "DEL_REASON_WE_FAILED_AUTH"

73 21:19:26.839 03/01/05 Sev=Info/5 CM/0x63100025
Initializing CVPNDrv

74 21:19:26.859 03/01/05 Sev=Info/4 IKE/0x63000001
IKE received signal to terminate VPN connection

75 21:19:27.349 03/01/05 Sev=Info/4 IPSEC/0x63700014
Deleted all keys

76 21:19:27.349 03/01/05 Sev=Info/4 IPSEC/0x63700014
Deleted all keys

77 21:19:27.349 03/01/05 Sev=Info/4 IPSEC/0x63700014
Deleted all keys

78 21:19:27.349 03/01/05 Sev=Info/4 IPSEC/0x6370000A
IPSec driver successfully stopped

Reply to Anonymous
Tom's Hardware > Forum > General Networking > VPN, VoIP, Video Conferencing, Remote Connections > USR8000A-02 + Verizon DSL -- Can't VPN?
Go to:

There are 1226 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them