Incoming Connection IP Address Assignment (VPN)

[guest]

I'm having issue with Incoming Connection IP address assignment. If I select "Assign IP addresses automatically using DHCP", connection from VPN clients would fail. Please note that my router is acting as the DHCP server in my network.

If I select "Specify IP addresses", clients would be assigned IP as specified. However, there is an issue with this. If I connect using an Android device, its IP and Subnet Mask are assigned correctly. If I connection using Windows 7 or Windows 8, the IP is correctly assigned, but the Subnet Mask is always 255.255.255.255, thus causing the client to be unable to communicated with other devices in the network. How does Windows 8 come out with the subnet mask?

Any help would be greatly appreciated.


Edit:

VPN clients can access devices within the internal network. This includes file sharing and "ping". However Remote Desktop fail to connect to the host in the internal network.

[guest]

Since this is peer to peer VPN, Subnet Mask is always 255.255.255.255 and you should be able to ping or access each other, but not other network resources. this post may give you more details.

Vista: VPN client is assigned 255.255.255.255 mask - ChicagoTech.net
correct, but the vpn miniport has the wrong subnet mask. instead of getting
255.255.255.0 I get 255.255.255.255. I have tried deleting and ...
www.chicagotech.net/netforums/viewtopic.php?t=562


The issue you have could be the firewall or 3dr party software block the Remote Desktop Conenction. Can you telnet port 3389? Or post back the results of both computers' ipconfig /all.


--------------------------------------------------------------------------------

[guest]

VPN connections do not work like LAN connections!

I agree with Bob. The subnet mask is a red herring. A VPN connection is a point to point connection (that is it emulates a cable connection) so a subnet mask is meaningless. Data just goes in one end and out the other. The routing is done at the other end.

If the VPN client is using IP addresses in the same IP subnet as the LAN (issued by DHCP), no routing happens. (You can only route between subnets). What happens is that the VPN server does proxy ARP for the guest and sends the replies back over the point to point connection. In other words the server just acts as a proxy for the remote client on the LAN.

[guest]

The firewall has been configured correctly, else I wouldn't be able to established a Remote Desktop Connection to the host from my internal network.

Router - 192.168.2.1

•DHCP server configured with scope 192.168.2.100 - 192.168.2.199.
Host PC (VPN server) - 192.168.2.100 (Dynamic IP with fixed IP reserved by DHCP server)

•Incoming Connection configured with TCP/IPv4
•IP address assignment -> Assign IP addresses automatically using DHCP = does not work and VPN client fails to connect in.
•IP address assignment -> Specify IP address -> 192.168.2.48 - 192.168.2.55
•Able to ping 192.168.2.101
•Able to ping 192.168.2.48
PC A (local network) - 192.168.2.101

•Able to remote desktop to 192.168.2.100
•Able to access shared folder hosted by 192.168.2.100
•Able to ping 192.168.2.100
PC B (VPN client) - 192.168.2.48

•Unable to remote desktop to 192.168.2.100
•Able to access shared folder hosted by 192.168.2.100
•Able to ping 192.168.2.100
Android Device (VPN client) - 192.168.2.49

•Able to remote desktop to 192.168.2.100 using PocketCloud
•Able to access shared folder hosted by 192.168.2.100
•Able to ping 192.168.2.100

[guest]

I assume you can't telnet port3389 from the VPN client to VPN Host. If this is the case, try to turn off the firewall for a test. If it doesn't work, it could be 3dr party security software. This search result may help.

The client could not connect to the remote computer
The LAN users can access Remote Desktop computer but not not VPN clients. After checking the Norton Security settings, we find the firewall allows only local IP ...
www.chicagotech.net/remoteissues/rdc2.htm

--------------------------------------------------------------------------------

[guest]

Finally I resolved the problem. It has nothing to do with the host PC. It's the client PC. I have Microsoft Firewall Client (Microsoft ISA) installed on the VPN clients. Disabling it before connecting resolve the problem. Weird though, when I was using OpenVPN, there is not such problem.

Anyway, thanks everybody for the help.