Strange Client Problem

Mar 24, 2005 1 Replies

Hi all,



I am having trouble connecting a client using Cisco's VPN Client 4.x to a PIX Firewall 506. I setup 5 computers for different locations and tested them in my office before I set them up. 4 of them worked fine but the 5th one is giving me some trouble. The client connects to the PIX fine, but when I try to ping anything on the remote network, I get no reply (pinging hosts on the remote network works fine at the other locations). So I guess I am not sure what the problem is. When I turn on logging from the VPN Client I see a lot of repeated lines after the connection is made to the PIX that none of the other locations show once they have connected. Here is a sample from the log (with the remote PIX's IP replace w/ X.X.X.X):


65 11:57:10.062 03/21/05 Sev=Info/6 IKE/0x6300003D Sending DPD request to X.X.X.X, seq# = 133952472


66 11:57:10.062 03/21/05 Sev=Info/4 IKE/0x63000013 SENDING >>> ISAKMP OAK INFO *(HASH, NOTIFY:DPD_REQUEST) to X.X.X.X


67 11:57:10.187 03/21/05 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = X.X.X.X


68 11:57:10.187 03/21/05 Sev=Info/4 IKE/0x63000014 RECEIVING > ISAKMP OAK INFO *(HASH, NOTIFY:DPD_REQUEST) to X.X.X.X


72 11:57:20.718 03/21/05 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = X.X.X.X


73 11:57:20.718 03/21/05 Sev=Info/4 IKE/0x63000014 RECEIVING > ISAKMP OAK INFO *(HASH, NOTIFY:DPD_REQUEST) to X.X.X.X


77 11:57:30.953 03/21/05 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = X.X.X.X


78 11:57:30.953 03/21/05 Sev=Info/4 IKE/0x63000014 RECEIVING > ISAKMP OAK INFO *(HASH, NOTIFY:DPD_REQUEST) to X.X.X.X


82 11:57:41.484 03/21/05 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = X.X.X.X


83 11:57:41.484 03/21/05 Sev=Info/4 IKE/0x63000014 RECEIVING > ISAKMP OAK INFO *(HASH, NOTIFY:DPD_REQUEST) to X.X.X.X


87 11:57:51.953 03/21/05 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = X.X.X.X


88 11:57:51.953 03/21/05 Sev=Info/4 IKE/0x63000014 RECEIVING


I did some more searching and found that adding the line: isakmp nat-t

fixed the remote access problem.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required