Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 257
  • Last Modified:

After creating VPN with FVG318NA and prosafe client, internet access is lost

After creating the the VPN conncection via prosafe client and FVG318na, i remote desktop to one of the pc and i can no longer access the internet from the pc that im in. any suggestions why this is happening? The entire office looses connection to the internet but not the LAN.
0
techsolutionusa
Asked:
techsolutionusa
  • 6
  • 5
1 Solution
 
Rob WilliamsCommented:
Do you men you can no longer access the Internet from the computer you are connecting from?
If so, it is due to a security feature in the VPN client that blocks local connections, including local Internet access, to protect the office/remote network. You can disable this if you wish.:
-Right click on the ProSafe icon and choose Security policy editor
-open your policy
-on the identity page next ti virtual adapter set it to required
-reboot the PC
-go to control panel | network connections | right click on the new VPN/Virtual adapter and choose properties | Networking | TCP/IP -properties | Advanced | General | un-check  "Use default gateway on remote network"
0
 
techsolutionusaAuthor Commented:
No what i mean is that when i VPN i use remote desktop use the IP to get to the server once im in the server when i open IE and try to get into the Internet lik www.google.com i get page cannot be displayed. the the other pc's in the office loose internet access. I wonder if the VPN tunnel is cause this. I worked yeasterday to re-brige the neotopia to the netgear and reset all the setting to get it the internet to work again at the office. once they were back up i VPN again and the internet access went down for them.
0
 
Rob WilliamsCommented:
It can be due to the VPN. There have been similar questions in the past with the Windows VPN client, but I have seen no solutions. It is likely a routing issue, but surprised it happens with the Netgear as the VPN end point. Usually the problem is with incorrectly configured RRAS on the server some how blocking local access and attempting to push all traffic through the VPN, but you would have had no need to work with that.
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
techsolutionusaAuthor Commented:
So what can be done?
0
 
Rob WilliamsCommented:
Might the subnet at the site from which you are connecting be the same as the server's LAN? i.e. might both sites be using something like 192.168.1.x ?  They must be different, or if there are multiple subnets anywhere along the path, they must all be different.
0
 
techsolutionusaAuthor Commented:
only got the 1 subnet its 192.168.0.2 - 255.255.255.0 should i create a different one for the VPN? is so how>
0
 
Rob WilliamsCommented:
>>"only got the 1 subnet its 192.168.0.2 "
Is this your site, the server site, or both?
They cannot be the same, if they are you have to change one site or the other. This is a basic routing rule, and may well be the source of the problem.
The VPN configuration does not have to change.
0
 
techsolutionusaAuthor Commented:
so i should change the site to another subnet like 10.0.0.1 255.255.255.0
0
 
Rob WilliamsCommented:
Are they both the same? If so yest.
It is quite alright to use something like 192.168.0.x at one site and 192.168.2.x at the other, so long as the subnet masks are 255.255.255.0
Using 10.0.0.1 is also fine.
However if changing one site or the other consider the repercussions first. You have to change server IP's all statically assigned devices such as printers, DHCP scopes, DNS, etc.

Can you test by finding a remote site that does not use 192.168.0.x to verify this is the problem?
It's usually easer to change the site from which you are connecting such as home, but if you are changing the server/Netgear site, avoid common subnets as listed below. Mobile users will sometimes have problems when connecting from some public sites such as hotels if you use common subnets.
Common ones to avoid:
192.168.0.x  192.168.1.x  192.168.2.x  
192.168.100.x  192.168.111.x
10.0.0.x  10.0.1.x 10.1.1.x
10.10.10.x
172.16.0.x
0
 
techsolutionusaAuthor Commented:
Might be eaier for me to change at the site since its only 2 pcs, 1 server and 1 printer... wont take long to do that. and try not to use the common ip address
0
 
Rob WilliamsCommented:
If possible, that is the better solution, long term.
Are you able to try connecting from another site to see if that is the problem? Regardless they need to be different for proper routing.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

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