But mobile can connect to laptop with 4G, indicating that there is no problem that the relay serves for the public network.Įnter the hbbs host or IP Address in the ID Server input box (local side + remote side). When laptop could not connect to the home computer, the rustdesk client told me that can not connect relay server. So I confirm that the problem is in the rustdesk setting of the home computer or the NAT problem of the home computer.
The results: The mobile phone can connect to the laptop, but not to the home computer, and the home computer can not connect to the laptop.
Rustdesk server android#
I set the "ID server" at laptop rustdesk as abc.com as same as android mobile. Ps: There is a VPN between the home router and work computersįirst, I set the "ID server" at. *.20 for ports 21115, 21116(TCP/UDP), and 21117Ĭlients：Laptop at office and android mobile( wtih 4G ) WAN： I have public IP and did ddns for abc.com 10/24），rustdesk server（in debian docker, use the host mode）(ip is. I had the same situation, but it was resolved.Stated below:
Rustdesk server update#
Remember to update DHCP configuration: the DHCP server should send the IP address of this DNS server to all (interested) clients. You have to configure the DNS to forward all the queries to external DNS (google 8.8.8.8, quad9 9.9.9.9, cloudflare 1.1.1.1) and you have to add an override just for one host which should return the internal IP address of your NAS (hosting rustdesk). You need a DNS server inside your network (like pi-hole or the one that comes with your Synology).
So you circumvent that by "faking" the DNS. This doesn't work from inside your home because your router doesn't support "hairpin nat": your application (via a DNS request) resolves that is your external ip address and tries to use that address to access the rustdesk server, but the router doesn't allow that. So from the point of view of an external viewer, everything works by using as "ID server". Suppose you own the domain you add a DNS record pointing to the external IP address of your home.
I think a good solution for this scenario is using DNS instead of IP addresses. I will put a fix for this scenario, but I have no solution for now.
0 kommentar(er)
