Hi,
After virtual DHCP has enabled, the VPN Client will be in different network! So no ping between Server and Client, then no way to get access to any service such as RDP, sharing or printer!
Why? and How do we fix this please?
VPN Client is in different network because of virtual DHCP!
-
- Posts: 10
- Joined: Sun Aug 04, 2013 5:06 am
-
- Posts: 551
- Joined: Wed Jul 24, 2013 12:09 pm
Re: VPN Client is in different network because of virtual DH
SecureNAT is sharing the IP address of the VPN Server. VPN Server itself is accessible by external IP address with the client in the past. I don't know why the VPN Server itself is inaccessible now by the VPN Clients. Perhaps you need an external LAN adapter without configuring any IP address for local bridge.
-
- Posts: 7
- Joined: Wed Sep 18, 2013 12:33 am
Re: VPN Client is in different network because of virtual DH
I had a similar issue on XP stations and tracked it to the modification of the local physical LAN gateway address.
You can see this by doing an ipconfig after and before the VPN is up.
You can also see this by doing a route print and noticing where the default 0.0.0.0 is set to (VPN adapter instead of local adapter)
If you have turned on Virtual DHCP, you should also do these two things:
1: Go into the secureNAT configuration and uncheck Use Virtual NAT function (not the issue but recommended) - and 2: remove the gateway address from options applied to clients (the issue).
By removing the gateway from the DHCP server, no override on the local route is made (and you wont bypass any filtering since your still using local NIC to browse).
So if you want to RDP locally by name you can since all default packets are going out the local NIC. If you also put in the virtual DHCP DNS 1 setting, the address of the virtual switch (which is the same as the gateway you just pulled out) then you can also resolve DNS queries in the VPN on XP station AFTER the darn timeout of the first DNS (local NIC).
Hope this helps.
You can see this by doing an ipconfig after and before the VPN is up.
You can also see this by doing a route print and noticing where the default 0.0.0.0 is set to (VPN adapter instead of local adapter)
If you have turned on Virtual DHCP, you should also do these two things:
1: Go into the secureNAT configuration and uncheck Use Virtual NAT function (not the issue but recommended) - and 2: remove the gateway address from options applied to clients (the issue).
By removing the gateway from the DHCP server, no override on the local route is made (and you wont bypass any filtering since your still using local NIC to browse).
So if you want to RDP locally by name you can since all default packets are going out the local NIC. If you also put in the virtual DHCP DNS 1 setting, the address of the virtual switch (which is the same as the gateway you just pulled out) then you can also resolve DNS queries in the VPN on XP station AFTER the darn timeout of the first DNS (local NIC).
Hope this helps.