F5F Stay Refreshed Power Users Networks Using WireGuard through unRAID to connect to Windows shares and remote desktop

Using WireGuard through unRAID to connect to Windows shares and remote desktop

Using WireGuard through unRAID to connect to Windows shares and remote desktop

A
adz12345
Junior Member
31
03-09-2016, 04:21 PM
#1
I successfully set up WireGuard today and attempted to reach a Windows PC using remote access. I suspect the Windows Firewall might be blocking the connection. I temporarily turned it off to test, but the issue persists—my client doesn’t recognize it. Anyone have suggestions? It’s been frustrating since I’ve already spent a lot of time trying other methods like openVPN through the router.
A
adz12345
03-09-2016, 04:21 PM #1

I successfully set up WireGuard today and attempted to reach a Windows PC using remote access. I suspect the Windows Firewall might be blocking the connection. I temporarily turned it off to test, but the issue persists—my client doesn’t recognize it. Anyone have suggestions? It’s been frustrating since I’ve already spent a lot of time trying other methods like openVPN through the router.

A
AstroZone
Member
136
03-11-2016, 04:20 PM
#2
It seems you can reach the PC via IP address, but using its name triggers a "host can not found" issue.
A
AstroZone
03-11-2016, 04:20 PM #2

It seems you can reach the PC via IP address, but using its name triggers a "host can not found" issue.

O
OmqDace
Posting Freak
798
03-11-2016, 11:45 PM
#3
Unfamiliar with WireGuard, just know OpenVPN works, but I think Windows names can’t be routed through it, so you’ll need to use IP addresses when connected via VPN.
O
OmqDace
03-11-2016, 11:45 PM #3

Unfamiliar with WireGuard, just know OpenVPN works, but I think Windows names can’t be routed through it, so you’ll need to use IP addresses when connected via VPN.

S
ShinryuuKai
Junior Member
33
03-16-2016, 01:22 AM
#4
I'm feeling a bit confused. I had to rebuild the links using the IP address rather than the name. This resolves the issue for both WireGuard and OpenVPN. On my previous router, this wasn't a concern, so I assumed it wouldn't be a problem now.
S
ShinryuuKai
03-16-2016, 01:22 AM #4

I'm feeling a bit confused. I had to rebuild the links using the IP address rather than the name. This resolves the issue for both WireGuard and OpenVPN. On my previous router, this wasn't a concern, so I assumed it wouldn't be a problem now.