Cannot access shares/map network drives over VPN: using Linksys WRV54G router and Linksys quick VPN client

Same setup as Q_21773993.html, small network, no server, no domain.  Just a handful of workstations in a workgroup (all XP pro).  VPN is established (finally) and pinging computer at the office with the share but non-routability of netBIOS is flubbing up a simple networking operation.

Trying to map a network drive and I thought that "\\IP.address.goes.here\share" would do it, but still not getting to the share.  What might I be doing wrong, ie: permissioning on the directory itself or limitations of the linksys VPN client.  

Not sure of the type of VPN that is being established with the linksys quickvpn client either.  Does the type of VPN matter?
rossman2006Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
papimichelConnect With a Mentor Commented:
could it be that windows firewall in on ?
0
 
prashsaxCommented:
Have you opened port 445 on your router for VPN users.

This port is required for the share access.
0
 
rossman2006Author Commented:
haven't opened it, but not sure if it's inherantly closed.  The web interface on the linksys box is fairly basic.  I'm assuming you don't mean a port forward to the PC I'm trying to get to on the inside of the LAN, that would just open that port from one box to the public IP.  The frustrating thing about these low end boxes is you don't get a lot of control.
0
KuppingerCole Reviews AlgoSec in Executive Report

Leading analyst firm, KuppingerCole reviews AlgoSec's Security Policy Management Solution, and the security challenges faced by companies today in their Executive View report.

 
papimichelCommented:
there might be a firewall behind the router that blocks all traffic to your network.
when connected to VPN, try to telnet one of your computers' ip address on port 135.
(telnet x.x.x.x 135)

if it fails, there might be a firewall that blocks the packets..

yours,
Michel.
0
 
rossman2006Author Commented:
can't telnet to port 135.  the linksys is the only device between the internet and the hosts
0
 
rossman2006Author Commented:
d'oh.  I have a sinking feeling that that might be the cause.  I think windows firewall is on on the computer inside the network.  Won't be able to answer that until tomorrow, but that could be it.  Curse you aquascum!!!!  always with the helpful things that ain't as heppfull as we want
0
 
rossman2006Author Commented:
Yup, the firewall was on on the hosting PC.

All is well (well, as well as you can expect from a linksys)

as a side note, they told me to turn off the windoze firewall on the clients running their software, but said I could open ports 1723, 50, 51, 443, and 500 (not sure of UDP or TCP, what do you expect from outsourced tech support?).  Not sure if that'll make the client firewall happy, but the VPN works when you don't have any firewalls turned on (what great security for a small network, right?)
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.