Link to home
Start Free TrialLog in
Avatar of d_melnyk
d_melnykFlag for Canada

asked on

Cannot access shared drives over VPN using Windows XP

Hi Folks:

   I am trying to set up a simple VPN with Windows XP Pro at each end.
 
   I have configured the VPN server and created a TestVPN user account. On the client machine I have set up the VPN connection and specified the correct IP address for the router attached to the VPN server computer. I have set the router to allow PPTP through to the VPN server.

  I can make the connection, but I cannot seem to access any shared folders on the VPN server. I have searched through the articles here and although they seem to address the issue, they always seems to be something which is unclear.

  I tried "net use x: \\Fileserver\testshare" where Fileserver is the name of the computer hosting the VPN, I also tried using the statric IP address of the Fileserver computer - i.e. 192.168.0.2, and I also tried using the IP address of the router which passes PPTP traffic to the fileserver computer - all to no avail.

Using an LMhosts file - could someone give me a clear example? Does this file have to be on the VPN host system - i.e. fileserver or just on the client system?

Do I have to install any other protocols on the systems other than TCP/IP and File and Printer sharing and CLient for Microsoft networks

Ideally I want to be able to map the shares / drives so that files can be accessed by the remote client - such as quickbook files - so that the files are updated on the VPN host server system and not simply copied to the remote client.

Thanks in advance.

Best regards, Dave Melnyk




Avatar of Rob Williams
Rob Williams
Flag of Canada image

Dave, one of the first things to check is both ends should be using a different subnet. If the office uses IP's belonging to the 192.168.1.x subnet , then the remote site needs to use something else such as 192.168.2.x
Also on your router you need to enable PPTP pass-through, as well as forward port 1723 to the VPN "server" computer.
Finally, does your router's WAN/Internet/Public interface have a true public IP ? In other words is it assigned the IP to which you are trying to connect, or is that assigned to your modem? If the latter, the modem needs to be put in bridge mode.
Avatar of d_melnyk

ASKER

RobWill:

   Thanks for the reply - the subnet thing may be an issue - the remote site is using the same subnet and providing me an IP address with 192.168.0.xxx.

  The subnet thing may be a bit of a problem to overcome as the two networks are already set up and starting to change things at either one would involve a fair amount of work - and probably grief! I guess there may be no way past that problem short of using an ssl based VPN.

  The router has PPTP forwarded to port 1723 on the VPN server

   The router at the office is assigned 192.168.0.1 and the modem has the true IP address - i.e. standard DLINK DI-524 - i.e. the router is lan address 192.168.0.1 and WAN is 70.xxx.xxx.xxx

How does one put the "modem" in bridge mode?

Best regards, Dave Melnyk
ASKER CERTIFIED SOLUTION
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi RobWill:

   Sorry I did not respond earlier - have been extremely busy. The issue is now no longer as pressing as we have opted to go with the netOp Remote Controlsolution which is dead simple to set up and thouroughly reliable for our needs.

   The router does indeed have the "public" or WAN address "70.xxx.xxx.xxx" and the router LAN address is 192.168.0.1.

The setup did have the "use default gateway on remote network" enabled, but there was still no ability to 'browse" for network shares.Could this be because the client machine also had a netbeui protocol installed as well as TCP/IP (netbeui was installed to use on another network when connected locally)?

Best regards, Dave Melnyk

>>"Could this be because the client machine also had a netbeui protocol installed as well as TCP/IP "
No that is fine. NetBEUI is not routable, so it doesn't help with VPN name resolution or browsing, but it will not interfere.

I suspect the problem is the subnets being identical. One of the primary rules of a VPN is they must be different. As pointed out above, it will "usually" work, but not always and it is not proper procedure.

Cheers Dave,
--Rob
Thanks Dave,
--Rob