RemoteDesktop plugin - requirements for using RDP on a Windows box?

  • Just installed the Remote Desktop plugin, and trying to get this working with a Windows 8.1 box and RDP.


    First up was the warning that the connection was not secure, you must use https to connect.


    So I generated a self-signed ssl cert in omv and enabled (but did not force) a secure connection in omv General Settings page. And I *can* login to the omv interface with https now, so the self-signed cert is working, but RDP is still telling me the same basic thing, that there is a problem with setting up the connection. I'm using https://192.168.x.x:3389 as the URL, and the resulting error is:



    The remote computer cannot be authenticated due to problems with its security certificate.
    Security certificate problems might indicate an attempt to fool you or intercept any data you send to the remote computer.
    Windows cannot continue setting up this connection. Contact your workplace administrator for assistance.


    Searching for similar topics didn't really help. One suggested I had to explicitly start the xrdp service (which I did) but that did not help.


    What am I missing, please? :)

    • Offizieller Beitrag

    1 - rdp doesn't use http or https.
    2 - I have never generated a cert for this plugin
    3 - the plugin enables and starts the xrdp service
    4 - I just tried it on a fresh VM and it works. This sounds like a setting on your windows 8.1 box that makes remote desktops conform to a certain rdp protocol level.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Dunno then.


    RDP in Win 8.1 (titled "Access RemoteApp and desktops" from Control Panel) asks for a URL or an email address, it will not take anything else.


    The help text on the setup screen specifies this and shows an example which is https:// (though it ends with a .aspx filename). Try to use http and you are told it must be https.


    Everything I've thought to try ends the same way:



    The remote computer cannot be authenticated due to problems with its security certificate.
    Security certificate problems might indicate an attempt to fool you or intercept any data you send to the remote computer.
    Windows cannot continue setting up this connection. Contact your workplace administrator for assistance.



    This was just an exercise to see if I could get it working, really, not something I "must have", but figured it was something I had simply overlooked. Any help appreciated, but don't lose sleep over it, lol.

  • Just updating....


    More digging and I see where I went wrong, though it still doesn't work properly.


    "Access RemoteApp and desktops" is not the right place or app. Have to show the Win8.1 main "Apps" screen, then choose Remote Desktop, right-click to run as Admin.


    Fill in details (192.168.x.x:3389) and I do get connected, I login, and then...... a screen that is entirely a washed-out gray within the normal RDP interface. (I use RDP for other things, so know what it *should* look like when in use.)


    Making progress, and will play with the RDP local settings, suspect it's to do with chosen screen resolution.

    • Offizieller Beitrag

    though it still doesn't work properly.

    There is something you are doing wrong or something you change on the OMV system that is conflicting then. I have never seen this app not work unless you try to login with root.


    "Access RemoteApp and desktops" is not the right place or app.

    That is for remote assistance I think.


    Have to show the Win8.1 main "Apps" screen, then choose Remote Desktop, right-click to run as Admin.

    You shouldn't have to run remote desktop as admin.


    Fill in details (192.168.x.x:3389) and I do get connected, I login, and then...... a screen that is entirely a washed-out gray within the normal RDP interface. (I use RDP for other things, so know what it *should* look like when in use.)

    That might mean you have previous desktop config files like .xinitrc in the user's home directory that have incompatbile settings. Make a completely new user and try logging in as that user.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Looks like this one's "my bad", though I'm puzzled why this happens


    From reading another topic, in which you replied and asked the op why they weren't using the ISO image, I wondered if that was relevant.


    Until now, I had used the Debian 8 Jessie netinstall cd, then the Guide here for installing omv on top of Debian Jessie. When I installed Debian, I chose all defaults except for enabling the ssh server, so by default it installed the desktop (Gnome?), and that seems to be where the issue lies.


    So I grabbed the ISO image from sourceforge instead, used it to install, then updated omv to latest, plus updates as shown on the Management page.


    And now it works perfectly. I have the desktop showing as it should in RDP.



    (As an aside..... is it just me not looking hard enough, or is the latest ISO image available on sourceforge, OMV version 3.0.58 ?)

  • UPDATE: For anyone who stumbles across this thread.....


    Yes, that was it.


    I reinstalled Deb 8 Jessie once more, but this time deselected Gnome (all other desktop choices were already), enabled ssh, and finished. Booted to terminal (just like the ISO had done), edited sshd config and took it from there. OMV3 installed and all updated.


    And now remote desktop works perfectly. Lesson learned. Thanks, rycoeaaron!

    • Offizieller Beitrag

    If you install a full desktop, it probably has incompatible settings for the remote desktop plugin. If you have a full desktop installed (and it actually works with OMV), you should just enable remote desktop from it instead of using the plugin.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Well.... that's the issue. If you do install their desktop (Gnome, anyway) they use a flavor of VNC with which my "VNC-Viewer" client just will not work.


    I've found what are claimed to be work-arounds, but none of them I tried, actually worked, lol.


    But by doing an install with no desktop, your plugin works perfectly, so I'll go with that.


    Thanks!

  • For those that do not get windows 10 to connect to the remote desktop on their openmediavault. You must use "%windir%\system32\mstsc.exe"
    in Dutch that is called "verbinding met extern bureaublad". It took me a while to find the right app, as there are several other remote desktop apps in windows 10 but I did not get those to work.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!