WireGuard

170 readers

9 users here now

WireGuard - A fast, modern, secure VPN tunnel

founded 1 year ago

MODERATORS

[email protected]

RDP but no network shares? (self.wireguard)

submitted 2 weeks ago by Zachariah to c/[email protected]

5 comments fedilink hide all child comments

After using WireGuard to VPN into my LAN, I can use RDP or SSH+VNC to control machines on my LAN. I am able to reach them via IP or by host.domain.private for remote control, but I cannot browse to
\\host.domain.private\share for the same machine to access its network share.

you are viewing a single comment's thread
view the rest of the comments

[–] Zachariah 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I have pretty much everything. iOS, Mac, Linux clients for RDP. Windows, Mac, and Linux hosts.

\\IP\share doesn’t work either

I can’t remember if I tried \\hostname\ instead of FQDN.

My WireGuard IP pool is a different subnet than my LAN, so it could be that, but I’m not sure why RDP would work. Now that I’m spelling this all out: in the back of my head, I’m wondering if this is a NetBIOS issue.

[–] [email protected] 2 points 2 weeks ago* (last edited 2 weeks ago)

I prefer using a different IP pool than my LAN, otherwise you can run into routing issues (same IP on 2 segments).

If using the Wireguard IP doesn't work, then something is blocking SMB specifically (from memory that's UDP 137,138 and TCP 137,139, 445. Double check that).

I don't use Wireguard directly, but Tailscale, which uses Wireguard, and I'd have to specifically block those.

Try doing a trace (tracert on Windows) of the destination address (in both directions) to see where traffic goes.

On Linux you can traceroute the SMB ports, on Windows nmap.exe can effectively do the same thing.