Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - pcampbell

Pages: [1] 2

Virtual private networks / Re: Windows 10: VPN works, DNS does not.

« on: December 03, 2020, 10:32:20 pm »

Strange, but at a glance it appears to be a almost identical setup to mine. Surprised you had trouble, but like you said, maybe Win10 20H2 makes the difference. Glad you got it working.

Virtual private networks / Re: Windows 10: VPN works, DNS does not.

« on: December 03, 2020, 05:51:40 am »

Upon looking at my strongswan.conf, it looks like you "before". (see attached). Not sure why yours would not work until you add it manually. I also do not show a "rightdns" in my ipsec.conf. Can you provide screenshots of the Mobile Client settings in the GUI? That may help. Also what does your network map look like?

Virtual private networks / Re: Windows 10: VPN works, DNS does not.

« on: November 25, 2020, 03:32:13 am »

Are you also supplying your DNS to your VPN client in the Mobile Clients setup? If not check the box that says "Provide DNS Server List to Clients" under the DNS Servers section and put you DNS Server IP addresses in there.

Virtual private networks / Re: Bridge and DHCP

« on: November 25, 2020, 03:28:31 am »

What do you have set for your IPv4 Tunnel Network and IPv4 Local Network? Also do you have "Address Pool" checked?

Virtual private networks / [SOLVED] L2TP Plugin

« on: November 25, 2020, 03:20:46 am »

After much trial and testing, I've come to the determination that the cause of my issue stems around something in the Interface Scrub. If I disable that RDP works fine. If it's on I cannot get it to work properly. I've tried setting an individual setting for the IPsec interface and if I change the Max MSS to 2400 it will allow me to connect to one of my servers. If it try a desktop it will not work. If I change it to 2500 I can connect to the desktop but then I cannot connect to the Server. I have tried different combinations of settings and not made any progress. As I say though, just turning off the Interface Scrub works, so I guess I'll leave it at that.

Thanks to all who helped
Philip Campbell

Virtual private networks / Re: L2TP Plugin

« on: November 16, 2020, 03:17:40 am »

Here you go. It appears to be passing traffic (from what I can see). But it never finishes loading the Remote Desktop into the server or a desktop I tried as well.

Thanks
Philip

Virtual private networks / Re: L2TP Plugin

« on: November 14, 2020, 05:57:50 pm »

Have never had to turn it off before, but did and still no luck.

Virtual private networks / Re: L2TP Plugin

« on: November 14, 2020, 01:31:54 pm »

Ok, may have spoke too soon $:-\$ While I can see my network and do some things (ping several devices and access some machines) I cannot use Remote Desktop (RDP) to connect to my server. I can ping the server by DNS name and by IP, but not RDP into it. Thoughts?

Virtual private networks / Re: L2TP Plugin

« on: November 14, 2020, 04:39:17 am »

Ok. I have to say thank you for all of your help. Last thing I have done is change the Local Network address in the Tunnel Phase 2 to 0.0.0.0/0 and it is all finally routing properly. LAN items to to LAN and I have internet access through the Tunnel.
Again, thanks for all of your help.

Virtual private networks / Re: L2TP Plugin

« on: November 13, 2020, 05:36:47 pm »

I did not change my p2 tunnel, only updated p1 with a different subnet.

Virtual private networks / Re: L2TP Plugin

« on: November 13, 2020, 04:39:27 am »

Ok, after some playing around I'm part way there. I can now route traffic to my internal network, but I still cannot get to the Internet via my VPN tunnel. Had to add rule to IPsec to allow my IPsec addresses (VIP now starts at 10.10.0.100/24) to my LAN (or "any" in this case). DNS and everything there seems to be working fine, but like I said, no internet. I've tried adding a rule to the WAN, and another rule to the IPsec, but must not have them right. I also tried adding another outbound NAT to see if that would be the issue.

Pages: [1] 2