Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Can't Reach Internal Network

I can establish a connection to the pix fine, but cannot get to the internal lan. It appears the vpn pool addresses don't reach the dns/wins servers, as if there is a routing problem. Do I need to take one of those pool addresses and use it as a static route/default gw on the router that sits between the pix and local lan?

Thank you!


Re: Can't Reach Internal Network


If you have a router sitting between the inside of the PIX and your local LAN, yes you will need a route routing the VPN pool subnet to the inside interface of the PIX.

Hope that helps.

New Member

Re: Can't Reach Internal Network

Thanks for the reply, I'll try that.

New Member

Re: Can't Reach Internal Network

Hey Mike,

That didn't work. I got an error msg about a "classless" ip address and the config failed. I can connect and authenticate to the pix ok but I don't get the windoz login screen for userid, password and DOMAIN

name. Only the pix is talking back and forth to the client. It's like it can't find the dns/wins servers.

New Member

Re: Can't Reach Internal Network

i had a problem like that today with a PPTP based VPN

I had

LAN ---> Router ----> PIX --->Internet <---PPTP Clients

if you have a router in between the PIX make sure

that you are not NAT'ing the VPN traffic that is retruning to the VPN clients

(i.e., web page access)

VPN Client src port 1044 syn -->

InternalWWW dst port 80

VPN Client establishes session to the PIX outside interface/tunnel endpoint

VPN Client request for a web page gets to the Web Server sucessfully BUT the firewall tries to NAT the return traffic as soon as it hits the inside interface.

the return traffic ends up with:

InternalWWW src IP-OF-OUTSIDE-INTERFACE port 80 syn-ACK -->

(since the ACK bit is set the PIX looks for an active NAT translation slot - in which there is none so it won't work)

i fixed it like this :

ip local pool VPNUSERS

access-list 123 permit ip any host

access-list 123 permit ip any host

access-list 123 permit ip any host

access-list 123 permit ip any host

access-list 123 permit ip any host

nat (inside) 0 access-group 123

nat (inside) 1 0 0

global (outside) 1 interface

interface inside address

(the router is

sysopt connection permit-pptp

i checked syslog and it was barking about no active nat translation slots........

what was happening was traffic was coming into the VPn tunnel and going to the destinations but the return traffic could not go back because of there were no active NAT translation slots for the session (that were INITATED by the internal clients). so i had to make sure that traffic returning to the VPN clients requests were not getting NAT'd on the way back.

hope this helps

p.s. object grouping may help, this was tedious

Don Garnett

Network Support Specialist

New Member

Re: Can't Reach Internal Network

Thank's for the help Don. I'll give this a try.

New Member

Re: Can't Reach Internal Network

Mike and Don,

I added a static route in our router(cisco 6509) for the vpn pool and it worked!

Thank you for your help!!

CreatePlease login to create content