TheLanc3/rustdesk
1
0
Fork 0
mirror of https://github.com/rustdesk/rustdesk.git synced 2026-04-20 07:03:21 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ (markdown)

RustDesk
2025-08-23 11:11:20 +08:00
parent 8c20793a38
commit cb33c322ee
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
FAQ.md

@@ -464,8 +464,11 @@ Here is how ChatGPT explains NAT hairping.
Also we high recommend you deploy on cloud instance which make your life quite simple, here is an example. Also we high recommend you deploy on cloud instance which make your life quite simple, here is an example.
> User: Well, I DID deploy the server in intranet (LAN) but I also am using DNS and DID set up a DNS re-write to the LAN version of the Rustdesk server IP for intranet endpoints but I am still having these issues. I did #2 here: https://rustdesk.com/docs/en/self-host/nat-loopback-issues/, The NAT hairpinning *might* explain the lack of connectivity to an onsite endpoint that has VPN turned on. But it does not explain me being unable to remote control offsite endpoints from campus... > User: Well, I DID deploy the server in intranet (LAN) but I also am using DNS and DID set up a DNS re-write to the LAN version of the Rustdesk server IP for intranet endpoints but I am still having these issues. I did #2 here: https://rustdesk.com/docs/en/self-host/nat-loopback-issues/, The NAT hairpinning *might* explain the lack of connectivity to an onsite endpoint that has VPN turned on. But it does not explain me being unable to remote control offsite endpoints from campus...
>
> ... > ...
>
> ... > ...
>
> User: I just migrated it to a Linode instance and redirected DNS and everything is good now. Thanks for your help! > User: I just migrated it to a Linode instance and redirected DNS and everything is good now. Thanks for your help!