RT-N66U VPN Issues

[bsn_mt]

I am trying to setup a VPN to allow for remote desktop connections and for file sharing and remote backup with my companies main server. I have setup the VPN Server as noted below and I have setup the Client connections. I am able to connect to the VPN and it shows as connects and assigns a Remote IP within the correct Client IP address pool. Once connected, I am able to use internet through the VPN (I do have "Use default gateway on remote network checked on the VPN Client), along with pinging various network computers and the server.

At that point, I am stuck. I am unable to access anything on the network via IP address and I am unable to connect to any network computers via Remote Desktop (I am able to connect to all computers via remove desktop from inside the network).

I am able to connect to the server if using internal IP (192.168...) it I type it in as an FTP address but not direct.

I am using a RT-N66U with Firmware Version 3.0.0.4.374_979

My VPN Clients will be both Windows 7 and Windows 8.1 and some Andriod Devices.

I have setup the RT-N66U VPN Server as follows:
Enable PPTP Server - Yes
Network Place (Samba) Support - Yes
Broadcast Support - Both
Authentication - Auto
MPPE Encryption - MPPE-128, MPPE-40, No Encryption
Connect to DNS Server Automatically - Yes
Connect to WINS Server Automaticlly - Yes
MRU - 1450
MTU - 1450
Client IP Address - 192.168.0.240 ~ 249

My LAN DHCP pool is set for 192.168.0.2 ~ 192.168.0.239

What am I missing or doing wrong? I can post additional info if needed.

Thanks,

Brad

 

[AdvHomeServer]

PPTP isn't the most secure VPN. Someone can break in if they really want to. The big advantage is that it's easy to set up and is mostly secure.

If you get addresses on the server from the pool you set up then you're connected via the VPN. The problem is on the server. If you don't have file access then perhaps the permissions on the server aren't correct. Try using unc paths. Are file shares set up properly?

If you're using Windows Server 2012 Essentials, Anywhere Access provides secure access and sets up fairly easily.

If you really want remote desktop access, then TeamViewer gives you it much easier. I've never set it up to pass through a Windows Server, but TeamViewer probably provides easy to follow instructions. It's not free for commercial use, but I suspect it costs less than Remote Desktop CALs.

 

[ColinTaylor]

Client IP Address - 192.168.0.240 ~ 249

My LAN DHCP pool is set for 192.168.0.2 ~ 192.168.0.239

The VPN clients (and their IP addresses) should be on a different subnet to your LAN. Change 192.168.0.240 ~ 249 back to 192.168.10.2 ~ 11