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

Netgear FV318 & Prosafe Client - connects but can't access server share

I have a Netgear FVS318 at the office and Netgear Prosafe VPN Client installed on my laptop.
I have an XP Pro computer with a share at the office. The office network is setup as "WORKGROUP"
When at the office, I can see the computer in my network neighborhood andI can access the share just fine.
The computer with the share has a static ip address.(192.168.0.4) (computer name is "server" and shared folder is "sharedfiles").
From home, I can connect to the vpn just fine and can access the router admin menu of the fvs318.
I can also ping the computer that I am trying to get share access to.
I have tried \\192.168.0.4\sharedfiles and \\server\sharedfiles but neither work.
I don't see the computer in my workgroup either from home.
It was my understanding that once I had a valid VPN connection, my mapped drive to the share would work just like when I was connected at the office, but I guess not.
I believe I have the router setup properly and so does netgear support but they feel I need to adjust windows firewall settings or something else on the computer with the share, but don't know what to have me adjust?? I don't really want to turn off the windows firewall on that computer but do I need to? Is there any sort of wins or dns settings I need to adjust or lmhosts files, etc....? I am a noob when it comes to this sort of vpn stuff.

0
notbobj1
Asked:
notbobj1
  • 2
1 Solution
 
dpk_walCommented:
Are both the networks running on the same IP subnet: 192.168.0.0/24; if yes, then you would need to change subnet at one of the ends.

Please advice if you can ping the remote server IP 192.168.0.4 from your machine after establishing VPN tunnel.

Thank you.
0
 
notbobj1Author Commented:
I found the solution last night.
There is a setting under network connections - called "incoming connections"
I enabled the checkbox for allowing vpn access to that computer, which then added a couple check boxes to allow vpn tunnels in the firewall and it seems to have done the trick.
0
 
dpk_walCommented:
Good to know that the problem is resolved! :)
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

Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

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