The rdp client (at least in 10/11, I haven’t tried others) tells me I need at least pro instead of home to use it, thus my comment about upgrading windows. Thank you for the extra clarification for those that can use it though!
@socphoenix I re-read. The text says, it’s an open-source protocol implementation with a reference client. I can imagine why a replacement of Microsoft’s server and client might be beneficial:
* a higher security grade (limited, if any part on Windows, but still …)
* RDP server on Linux for mixed server environments to ease remote control, if the client is compatible with both Linux and Microsoft RDP servers
* extend user per server number without license costs
RDPWrap used to be able to run a patched version of RDP for Windows Home to enable incoming RDP but it isn’t maintained anymore. You didn’t need to upgrade to Pro.
@On@const_void@socphoenix RDP server = software on remote control target. So if this is about allowing incoming remote control on a Windows Home client machine: Use Rustdesk. ( https://rustdesk.com/ )
Windows Home is crippled. Microsoft in general is just a data vacuum cleaner, but functionally OK. But Windows Home …
Afaik Rustdesk server isn’t opensource and you’re limited to using their free servers in Europe for relay. I just need an alternative for lan remote desktop.
@On Rustdesk server software seems free to me. It is open source and free of charge. If you need service because you don’t succeed installing it, that service will not be free. I cannot see any limitation to use rustdesk with their or own relay servers, but I have not understood yet the difference the company defines between managed and unmanaged users. I guess it depends on your usage if you hit any hidden limits in the free plan, if they exist.
Alternatives for GUI remote control include VNC. But I’d tunnel it through SSH because it’s weakly encrypted, at least the last time I checked it.
If you find any evidence for your assumptions on rustdesk.com or experience, please let us know.
The rdp client (at least in 10/11, I haven’t tried others) tells me I need at least pro instead of home to use it, thus my comment about upgrading windows. Thank you for the extra clarification for those that can use it though!
@socphoenix I re-read. The text says, it’s an open-source protocol implementation with a reference client. I can imagine why a replacement of Microsoft’s server and client might be beneficial:
* a higher security grade (limited, if any part on Windows, but still …)
* RDP server on Linux for mixed server environments to ease remote control, if the client is compatible with both Linux and Microsoft RDP servers
* extend user per server number without license costs
RDPWrap used to be able to run a patched version of RDP for Windows Home to enable incoming RDP but it isn’t maintained anymore. You didn’t need to upgrade to Pro.
@On @const_void @socphoenix RDP server = software on remote control target. So if this is about allowing incoming remote control on a Windows Home client machine: Use Rustdesk. ( https://rustdesk.com/ )
Windows Home is crippled. Microsoft in general is just a data vacuum cleaner, but functionally OK. But Windows Home …
Afaik Rustdesk server isn’t opensource and you’re limited to using their free servers in Europe for relay. I just need an alternative for lan remote desktop.
@On Rustdesk server software seems free to me. It is open source and free of charge. If you need service because you don’t succeed installing it, that service will not be free. I cannot see any limitation to use rustdesk with their or own relay servers, but I have not understood yet the difference the company defines between managed and unmanaged users. I guess it depends on your usage if you hit any hidden limits in the free plan, if they exist.
Alternatives for GUI remote control include VNC. But I’d tunnel it through SSH because it’s weakly encrypted, at least the last time I checked it.
If you find any evidence for your assumptions on rustdesk.com or experience, please let us know.
@const_void @socphoenix