Access to Internal Lan

[bobuser101]

I searched and cannot find the answer, I have just setup successfully my IPsec VPN and when connected via the VPN I can access my router (192.168.1.x). But when I try to RDP to the internal IP of my PC, it will not access it.

Do I have configure anything to get this to work

thank you.

[lszalontai]

Is RDP enabled on your PC? It's disabled by default.

[bobuser101]

Is RDP enabled on your PC? It's disabled by default.

Yes, previously I opened the RDP port on the firewall. But after reading up I found out this was not good for security.
So setup the VPN to the access the internal network and theN RDP in to my PC.

But through the VPN I cannot access the PC via RDP. I believe I need to setup the VPN so it allows access to the internal network, but not sure how to do this.

[lszalontai]

I meant to ask if you enabled RDP itself, not opening a port for it. I believe Windows (at least Win 7) sets up a firewall rule automatically.
- Can you RDP into your PC from the local network?
- Can you ping your PC through VPN?
- Do you have UT and a separate router at your home setup?

[bobuser101]

I meant to ask if you enabled RDP itself, not opening a port for it. I believe Windows (at least Win 7) sets up a firewall rule automatically.
- Can you RDP into your PC from the local network?
- Can you ping your PC through VPN?
- Do you have UT and a separate router at your home setup?

Yes from local network
No
Untangle is the only router

[lszalontai]

How does your vpn config look like? Can you post some screenshots?

[bornpilot]

I am going take a guess that this is the problem as described in this post. Of which I also have this issue. I can connect form my remote workstation to untangle but I can't access devices in the LAN side of untangle. The way I can get this to work as described in the post linked below if I create a local route on my remote workstation I can access the untangle LAN devices for which I created the route, this is given in the case you have more than one LAN on the untangle side in that case you would need to create more than one local route on the remote workstation client. So, my question to this is how do get l2tp client windows or other wise to create the route for me. Some deices such as iOS I am unable to create those routes.

https://forums.untangle.com/ipsec-vp...ipsec-psk.html

[sky-knight]

IPSec doesn't do NAT, no NAT means local Windows firewalls reject remote sessions.

If you fix it by adding a route, your VPN client is ignoring the route being pushed to it via the VPN service. Most of the time I see this happening because there's an IP address conflict. Check your VPN Config tab in the IPSec module and ensure you don't have any overlaps with the L2TP address pool, or the XAuth Pool.