Cannot redirect USB to AWS Windows Server 2019 USB

Forum / NoMachine for Windows / Cannot redirect USB to AWS Windows Server 2019 USB

Viewing 15 posts - 1 through 15 (of 18 total)
  • Author
    Posts
  • #29228
    SteveSpaw
    Participant

    We are evaluating NoMachine and it seems to work very well for us. We have been using Windows 10 to Windows 10 connections with USB forwards with good success through our VPN. We cannot get USB devices to forward to AWS Windows Server 2019 (1809). We have tried everything we can think of. Disk Connects also do not connect. All firewalls are turned off. Everything else works perfect. Is there anything else we should know about Server 2019? This is the only difference from our other setups.

    Thanks for any help

    #29407
    SteveSpaw
    Participant

    Has anyone ever done USB direction to Windows Server 2019?  AWS? Looking for any help here.

    Thanks!

    #29415
    Giorgi-G.
    Contributor

    Hi,

    I was able to reproduce this issue on AWS EC2 machines and can confirm that USB device forwarding does not work on it.

    The reason is that in that type of machine Universal Serial Bus Controllers drivers are missing on the Device Manager. Usually, that happens on VM because of USB functionality is disabled in VM’s settings. For now, we are trying to find a solution for that.

    Could you please share some info about what type of VM you use on AWS? And as well as attach a screenshot of Devices Manager?

    #29422
    SteveSpaw
    Participant

     

    OS Name Microsoft Windows Server 2019 Datacenter

    Version 10.0.17763 Build 17763

    Other OS Description Not Available

    OS Manufacturer Microsoft Corporation

    System Name AWS-system

    System Manufacturer Amazon EC2

    System Model g4dn.8xlarge

    System Type x64-based PC

    System SKU Unsupported

    Processor Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz, 2500 Mhz, 16 Core(s), 32 Logical Processor(s)

    BIOS Version/Date Amazon EC2 1.0, 10/16/2017

    SMBIOS Version 2.7

    BIOS Mode Legacy

    BaseBoard Manufacturer Amazon EC2

    BaseBoard Product Not Available

    BaseBoard Version Not Available

    Platform Role Desktop

    Secure Boot State Unsupported

    PCR7 Configuration Not Available

    Windows Directory C:\Windows

    System Directory C:\Windows\system32

    Boot Device \Device\HarddiskVolume1

    Locale United States

    Hardware Abstraction Layer Version = “10.0.17763.1131”

    User Name USER\Administrator

    Time Zone Central Daylight Time

    Installed Physical Memory (RAM) 127 GB

    Total Physical Memory 127 GB

    Available Physical Memory 113 GB

    Total Virtual Memory 145 GB

    Available Virtual Memory 127 GB

    Page File Space 18.0 GB

    Page File C:\pagefile.sys

    Kernel DMA Protection Off

    Virtualization-based security Not enabled

    Device Encryption Support Not Available

    A hypervisor has been detected. Features required for Hyper-V will not be displayed.

     

     

    #29427
    Britgirl
    Participant

    Steve, if there was an image attached to your reply, please submit it directly to forum[at]nomachine[dot]com.

    #29430
    SteveSpaw
    Participant

    Sorry I thought I attached this

     

    Thanks

    Steve

    #29443
    Giorgi-G.
    Contributor

    Hi Steve,

    Thanks for the provided info. I can confirm that we reproduced your issues on the same type of VM. Currently, we are focused on it’s fixing. I will share an update on the progress on this topic.

    #29494
    mikeduke111
    Participant

    The reason is that in that type of machine Universal Serial Bus Controllers drivers are missing on the Device Manager. Usually, that happens on VM because of USB functionality is disabled in VM’s settings. For now, we are trying to find a solution for that.

     

    Hope this information is helpful to you

     

    #29498
    Giorgi-G.
    Contributor

    Hi Mike, yes, that’s a reason. So for now we try to make it work even if Universal Serial Bus Controllers drivers are missing.

    #29500
    SteveSpaw
    Participant

    Also the Drive connections do not work either as a side note.

    Thanks for working on this, it will be a big deal to make this work!

    Steve

    #29624
    Giorgi-G.
    Contributor

    Hi Steve, Mike,

    I can confirm that this issue is fixed and will be released one release after the next (current release is 6.11.2). If you need a patched package with the fix, please don’t hesitate to ask and we will provide it before the official release.

    #29722
    SteveSpaw
    Participant

    Is this fix in the 6.12.3 package?

    If not I would really like to try the update ASAP.

    Thanks

    Steve

    #29770
    SteveSpaw
    Participant

    Bump for this request ; I would really like to try the patched package to test this.

     

    Thanks a lot!

    Steve

    #29901
    SteveSpaw
    Participant

    @Giorgi-G.

    I would still like to try out this update ASAP. I don’t know how to contact you any other way.

    Thanks,

    Steve

    #29904
    Giorgi-G.
    Contributor

    Hi Steve,

    Sorry for belated reply.

    No, as mentioned it will be released “one after next” release, so it’s not included in the current 6.12.3 version. I will prepare for you a 6.12.3 version with the mentioned patch this week and provide it to you.

     

Viewing 15 posts - 1 through 15 (of 18 total)

This topic was marked as closed, you can't post.