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

Issue connecting via VPN

Hello,

I have a CISCO ASA5505 PIX Firewall and I'm having a problem mapping a drive and using Remote Desktop Connection to our server after I make a successfull VPN Connection. I'm not sure what the issue is. The only thing that has changed is our External IP Address due to changing ISP providor. I made all of the modifications to connect to the remote LAN.

Thanks, in advance.
0
aromeo409
Asked:
aromeo409
  • 7
  • 4
1 Solution
 
aromeo409Author Commented:
modification
0
 
agriesserCommented:
So you can establish the VPN connection without problems? Where is the terminal server located you're trying to connect to? Behind the ASA or in your local network?

Can you ping it?

Are you using Cisco's VPN client to connect to this ASA?
0
 
aromeo409Author Commented:
I can establish a VPN Connection with no problems and the TS is on our Local network behind the ASA. We also cannot oing it while connected to the VPN and we are using the CISCO VPN client 5.0.01.0600.
0
The Lifecycle Approach to Managing Security Policy

Managing application connectivity and security policies can be achieved more effectively when following a framework that automates repeatable processes and ensures that the right activities are performed in the right order.

 
agriesserCommented:
I think I still did not understand you.

Let's say your local network (the network where you're currently sitting) is 192.168.1.0 and you try to establish a VPN connection to the network 192.168.2.0.
Where is the terminal server located? In 192.168.1.0 or 192.168.2.0?

I assume it's in 192.168.1.0 which would make sense since you said you can't even ping it when connected to the VPN tunnel.
Therefore I further assume that you probably have a VPN configuartion file (.pcf) which probably simply has the EnableLocalLanAccess disabled?

Open your pcf file (or modify the connection entry in the GUI) and enable local LAN access.
Did this help?
0
 
aromeo409Author Commented:
The network I'm currently sitting in is my home local network (192.168.1.0). The terminal server is located at our office which has a local netwok range of 192.168.1.0 and the TS local IP is 192.168.1.2.  

I now establish a VPN connection and I do have the enable local LAN access option selected within the pcf file. Once I make a successfull VPN connection, I' unable to map a network drive of connect to the TS in my remote office. This only started when we just switched to a new ISP provider.

Thanks, in advance.
0
 
agriesserCommented:
That won't work. You can't have the same network range at home and at work.
You need to either change all ip-adresses at work or at home.

The best idea for people who are using VPN connections very often is to use unusual network addresses at home.
I, f.ex., use 10.255.255.0 at home.

If your local network is in the same IP range than the remote network, you can't route packets there because your local LAN adapter always thinks that 192.168.1.0 is on the wire in your house.

Change the network addresses on one of these two sides and the VPN connection will work.
0
 
aromeo409Author Commented:
i'll try it and let you know. Thanks!
0
 
aromeo409Author Commented:
what class subnet?
0
 
agriesserCommented:
Doesn't matter, it just has to be different from the one you're connecting too.
Take 10.255.255.0/255.255.255.0 for example and you will most likely never have problems again (except when trying to establish a VPN connection to me ;) ).
0
 
aromeo409Author Commented:
Works, like a charm....Thanks so much....
0
 
aromeo409Author Commented:

Works, like a charm....Thanks so much....
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

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