Download Rustdesk For Windows ^NEW^
Lorie Silano
I wanted to ask if anyone knows why rustdesk 1.1.9 not compatible with windows 10 pro. I have installed it on a laptop with windows 11 pro and there has been no problem, but when trying to install it on a desktop with windows 10 pro it tells me that it is not compatible.
I'm trying to use rustdesk At the school I work at. We use VNC but some teachers have scaling enabled and VNC doesn't like that. Anyway It will give a windows firewall prompt when I attempt to connect and teachers don't have the ability to allow the connection. I tried deploying a Windows firewall rule to allow 21115-21119 tcp 21116 UDP and 8000 TCP like listed in the manual but I still get the prompt on my testbench. And If I click the allow from there it works fine so it is just windows firewall that's in the way.
Hello r/rustdesk, I have to work on three different clients computers that are located in another country. This work has to be done on regular basis. For which I was thinking of using RustDesk. I have some questions before I make the change. Can someone please guide me about the following: 1- Does the Rustdesk has unattended access? 2- what about its latency and lags? 3- is it easy to use like anydesk or does it require bit of coding/developer knowledge. 4- Is it a good alternative to Anydesk or TeamViewer i.e. does it gives a smooth workflow? 5- Any glitches in cross border connections.
Lets assume you have local network and you want to allow RustDesk clients to access each other both in public and local network. That means you have local Windows PC that will act as RustDesk server and internet connection with static public IP address. Local network is behind NAT router. You will use dedicated domain for service named rustdesk.mydomain.org. You have a router which allows you to set NAT rules and that also acts as DNS for local network with option to set static DNS entries.
Set up domain rustdesk.mydomain.org to point to public IP address assigned to your router. That would allow clients from internet to search for the server in your network. Lets assume that rustdesk.mydomain.org points to IP 94.214.56.108. That is address that all RustDesk clients located on Internet should connect to to access your self hosted RustDesk Server.
Make static DNS entry in router that would point domain rustdesk.mydomain.org to local IP address you assigned to the server (assumed to be 192.168.1.4). This allows clients in your local network to also see the server on that domain. Although domain is the same, IP address they get would be different from IP that clients on the public Internet would see. What matters is that they deal with the same domain.
You can simplify this settings if you set RustDesk server outside of your network, on some bare bone hosting or cloud server. That way you will not have to deal with router, NAT and static DNS. Your server would have public IP, visible from everywhere, and you would simply point domain rustdesk.mydomain.org to that IP.
Download portable RustDesk Client from and unpack rustdesk.exe (it would probably have version number in file name) wherever you want. Desktop would be fine. RustDesk Client version I did this with is 1.1.9.
Most usual issue is that someone already has installed RustDesk Client that connects to public server. If that is the case he must deinstall that client. If he needs to connect to public server too, he can just copy exe you provided into new file named rustdesk.exe. That one would be portable and it would connect to the public server. He just must may attention that he cannot have running two clients connected to self hosted and public server at the same time. One that is run first would work, other one would go crazy.
df19127ead