Netgear VFL328 VPN Remote Desktop Issues

I'm using Netgear VPN software to connect to a FVL328 VPN box. I can sucessfully connect to the VPN. I can ping the server with responses. But when I try to
connect using Remote Desktop, it can't make the connection.

Just to give some background. We have used this VPN box sucessfully at the old office, since we moved to this office, The only thing that we changed was
the IP information. ie static IP, subnet mask, DNS

Locally I can connect to the server using Remote Desktop from another workstation but not thru the VPN.

I can't figure out if the problem lies in the Router or the server??

Thanks for the help in advance!!!!
shake74Asked:
Who is Participating?
 
Rob WilliamsConnect With a Mentor Commented:
Problem sounds like same subnets. The subnet at the main office must be different than the remote office, or you will have results exactly as described. As an example if the main office is using 192.168.1.x then try for the remote office 192.168.2.x (assuming a subnet mask of 255.255.255.0 at both sites)
0
 
shake74Author Commented:
The main office is using 192.168.0.x and remote computer is using 192.168.1.x
Subnet mask at both locations is 255.255.255.0
0
 
Rob WilliamsConnect With a Mentor Commented:
Odd...
-Can you perform any other tasks, for example can you open a share?. If not that can sometimes be an MTU issue.
http://www.dslreports.com/faq/7752
http://www.dslreports.com/faq/5793 
-At the site from which you are connecting, has the router been assigned a public IP ? No chance the modem is a combined router and modem and it is performing NAT and assigning the router a private IP (double NAT devices) ? Doubtful this is the problem where you can get so far as to ping.
-How far do you get with the remote desktop connection any error messages, or gray or black screens?
0
 
shake74Author Commented:
I found the stupid problem.
The subnet mask entry on the VPN client was set to 255.255.255.255
Instead of 255.255.255.0


Thank you very much for you prompt responses. I've split the points.
0
 
Rob WilliamsCommented:
Glad to hear you were able to resolve. Sometimes we overlook the obvious :-)
Note though that with some VPN clients 255.255.255.255 is correct. However, if connecting to a subnet with the ProSafe client, as you are aware, that is not correct.
Thanks,
--Rob
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.

All Courses

From novice to tech pro — start learning today.