• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 421
  • Last Modified:

Cisco VPN and Port Forward Issue

All,
I have a Cisco PIX I have setup for VPN and Port Forwarding. I am forwarding two ports, web server and terminal services, to a server on the internal network. My problem is when I attempt to access terminal server or web server of that server while connected to VPN, I am unable to to connect.

Is it possible to connect to those ports if I am forwarding from my public IP address also?

Thanks,
Tareef
0
TareefA
Asked:
TareefA
  • 3
  • 3
1 Solution
 
lrmooreCommented:
Are you trying to access these by their public IP that you have static xlates for?
Are you using IP address or DNS name?
Yes, it should be possible to access those ports through the VPN even though you have static nat.
Are you using a different IP subnet for your clients than the inside network?
Can you access anything else on the network while connected via VPN?
Do you have any access-groups assigned to the inside interface?
Do you have split-tunneling enabled?
0
 
TareefAAuthor Commented:
Hello lrmoore,
Answers below:

Are you trying to access these by their public IP that you have static xlates for? No, private/internal
Are you using IP address or DNS name? tried both
Are you using a different IP subnet for your clients than the inside network? Yes, inside is 10.0.0.0, client vpn network is 10.1.0.0
Can you access anything else on the network while connected via VPN? Yes, anything not using port forwarding
Do you have any access-groups assigned to the inside interface? Yes, allowing all traffic from VPN client network
Do you have split-tunneling enabled? Yes

Thanks
0
 
lrmooreCommented:
>Do you have any access-groups assigned to the inside interface? Yes, allowing all traffic from VPN client network
Can you post your acl?
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
TareefAAuthor Commented:
Here is my acl:

access-list inside_outbound_nat0_acl permit ip any 192.168.3.0 255.255.255.0
access-list outside_cryptomap_dyn_40 permit ip any 192.168.3.0 255.255.255.0
access-list 103 permit icmp any any
access-list splitvpn permit ip 192.168.0.0 255.255.255.0 192.168.1.0 255.255.255.224
access-list splitvpn permit ip 192.168.1.0 255.255.255.0 192.168.3.0 255.255.255.224

Thanks,
Tareef
0
 
lrmooreCommented:
None of those will be applied to the inside interface...

Hint: don't use "any" in the vpn specific acls. Assuming inside lan is 192.168.1.0 and VPN client pool is 192.168.3.0:

access-list inside_outbound_nat0_acl permit ip 192.168.1.0 255.255.255.0 192.168.3.0 255.255.255.0
access-list outside_cryptomap_dyn_40 permit ip 192.168.1.0 255.255.255.0 192.168.3.0 255.255.255.0
0
 
TareefAAuthor Commented:
I think that worked.

Thanks!
Tareef
0

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now