Simple Wireguard configuration: I can RDP in but can't ping, DNS, or map a drive

Routers VPN, DNS, Leaks
1

I have a very basic and simple Wireguard Setup. Mostly using defaults.

Remote network has only a GL.iNet on it. I have a default configuration for Wireguard Server setup on it. In the options I have Remote Access LAN, IP Masquerading, and Client to Client enabled. I created a profile for my home network and downloaded the configuration file.

From my home network, I import the wireguard configuration file into the wireguard desktop client app and can easily connect to the VPN. Once connected, I can connect to any web applications running on the Remote network, and I can RDP into any computers on the remote network, but I can't ping any computers on the remote network, I can't resolve their IP by their host names, and I can't map a drive to any of them (by IP or host name).

I can map drives between devices on the remote network just fine.

I have searched and searched on this, and the most common solution I have found is to use LUCI to configure the firewall zone forwarding so you have an entry for wgserver, lan/wan/wireguard, to accept input, accept output, and reject forward. This is all there there by default when I went in and checked. I didn't have to set anything.

I find it very odd that I can RDP but not ping. Any help would be greatly appreciated. Spent several hours on this to no avail. Thanks in advance.

2

Check the firewall on the devices itself. Guess they don't allow your WireGuard network to enter services.

1 Like
3

Thank you for the reply. I had been adjusting the windows firewall settings to try to troubleshoot it - enabling file and printer sharing inbound over all networks (public/private/domain/etc) and that didn't work, but just as a test, I disabled firewall completely and mapping a drive worked. So this is definitely a Windows firewall issue and not a VPN/router configuration issue. Thank you!

I still have the issue with being unable to resolve host names of machines on the VPN network but I think that is a very different issue so I will work on it separately and if I still can't figure it out, will create another post.

4

are you using the default dns server in the wireguard client config file?

if so then it doesn't use the router dns server so you can't do anything which needs local name resolution. weird that you can do some stuff though.

change the dns server to the router in your client config and try again.

1 Like
5

Thanks for the reply - can you help expand a bit for me? You are saying on the VPN server Wiregaurd screen, create a new client configuration profile, and in the settings of that ("Client Configuration"), set the DNS Server to 192.168.8.1 which is the internal host name for the VPN router in the remote network? If so, I tried that and it won't even connect from my laptop using the WireGuard client app because it can't find that DNS server. I also tried configuring it to the public IP address of the remote VPN network and that didn't work either.

As far as some things working - everything by IP works. Nothing by hostname works. So its definitely DNS related. I just don't know how to fix it.

6

yes that's what I meant. That issue you described is odd because it should work when you have remote access lan enabled.

Maybe try a factory reset?