| W7 VPN: Connected but no network shares Setting up my first VPN using Windows 7 on both endpoints.
I am able to make the connection, but when I enter the IP address of the other remote computer it brings my local shares up on my own local computer. I do not understand this, it's like it remaps the remote computers IP to mine but uses my local shares instead of the remote workstation network shares.
My local IP range is 192.168.254.x
The remote computer's IP range is 192.168.0.x
The remote computer running the VPN (Incoming Server Connection) is 192.168.0.100
When I type \\192.168.0.100 to access the remote workstation shares, it brings up the shares for my local computer, which is 192.168.254.55.
I tried to ping the other remote workstations with no luck
I was able to ping the remote router IP address, 192.168.0.1, but I'm curious if it is actually the remote router or something else.
Here are two pics of the connection if that helps: |
|
|
|
1 edit | I was able to confirm the remote IP of the router is working as it should be. I put the IP, 192.168.0.1 into my browser and it gave me access to the remote router.
So what is keeping me from accessing the remote shares, and why does 192.168.0.100 keep opening my local network shares on this computer instead of it's remote network shares?
That just baffles me!
I was finally able to connect to one of the other remote workstations. Though I still can not connect to the computer that is running the VPN connection (192.168.0.100). Is that by design? Do I need to run the vpn from another workstation so that I can access it's net shares from 192.168.0.100? If so that doesn't seem right. |
|
| reply to Modify_inc
Is the other side of this VPN connection on your local LAN, or over the internet?
I'd try using the PUBLIC IP address of the other end -- making sure that the proper port(s) are open
and port forwarding is set up.
$20 says if you tried to traceroute from your PC to 192.168.0.x, you get a bunch of ***s after the 2nd
or 3rd hop?
Regards |
|
| Yes it is over the internet and the remote location has a static IP address from the ISP. Yes port 1723 is forwarded in the router at the remote endpoint. I can see the other workstations, though I do not need to access them. I need to access the workstation that is running the Incoming Connection, but for some reason it remaps that workstation to my own local computer's network shares. I'm thinking it must be by design, and am tempted to run the Incoming Connection on one of the other remote workstations so then I can hopefully access the computer that I need.
If you notice in the first picture it show the client's IP address of 192.168.0.100. The client is me, but that address should be the remote workstation's IP. Why is it giving it to me and using my own network shares? I do not know how to access this particular computer with this happening. |
|
| Any other suggestions before I try setting up the Incoming Server to another workstation on the remote network? |
|
TheWiseGuyDog And ButterflyPremium,MVM
join:2002-07-04
East Stroudsburg, PA
kudos:2 Reviews:
 ·Optimum Online
| reply to Modify_inc
According to the first screen capture, the client IP is 192.168.0.100 but the server IP is 192.168.0.4
Are you sure your computer is not the client and the IP you want for the shares is not the server 192.168.0.4?
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
