Solved WireGuard VPN problems

Before reading all this detail ... I spent the whole day wondering why 'VPN wasn't working' but it now occurs to me that VPN is working, the tunnel is working, but there is some sort of file share / networking problem. I can ping and the router says the 11client is connected.
I am wondering if it's something as simple as the 11client PC not having network file sharing enabled. The 11client is a brand new computer and it only connects to a FIOS router as far as I know. The client is out of state. I would ask the guy but he's unavailable. Since I typed out this whole thing I might as well ask.

Detail:
I am using a Gl.inet Mt6000 w4.7.0 "FLint2" router which includes WireGuard server. I am using DDNS.

I have 2 clients, one is W10home, one is W11 (not sure if home/pro)
The host, connected via ethernet to Flint2, is 11pro.
Host has a few folders shared out and is essentially our file server.

The local network, literally just shared folders on 11host (W11Pro), works fine. It's set up with password protection, once you've gained access...no PW required.

On F2 when you go to the WireGuard (WG) tab you are able to create configuration files for each client, so you get a unique private key.

I set up 10Home 1st. The config file uses the F2 supplied DDNS address xxxxxxxxx.glddns.com:51820, which points to our public FIOS router IP. This is all done by the router.

in 10H's config file it is: Endpoint = xxxxxxx.glddns.com, with AllowedIPs = 0.0.0.0/0,::/0 (automatically given by F2 - I did not change the config file at all)
It connects and when it does so it asks for Log/Pass and when you enter the user/pw that exists on the 11Pro, you get access just like you're on the local network. Wonderful.

11client I tried essentially the same conf except with a different private key.
It did not work. I changed the endpoint to our public ip with port 51820. Nada.
I changed the allowed IPs to 192.168.8.250/32 which is the static address of the 11P file share. Nada

On the 11 client I cannot get access to the 11host shared folders. When you enter 192.168.8.250 it opens a browser and then times out.

I tried 11client with DDNS enabled and disabled. I tried both of those settings using the glddns.com endpoint and the public Verizon FIOS IP.

However...the router shows that the client is connected and I can ping from 11client to 192.16.8.250 and I can ping 11client from my personal laptop which is on the F2/11host local network.

The 10H client that connects successfully is also behind a Verizon FIOS router.

I have not made any changes to either FIOS router.

Reboot the router

Dannydet said:

Reboot the router

Click to expand...

Yes #1 rule of tech support accomplished.