Mike Howles

Thank you! This was my problem. This solved it for me also.

Apologies if this has already been answered, but I searched and came up blank here and when Googling it. I get the following error in the log when trying to create a regular RDP connection to a new Windows 10 box. guacd[948]: INFO: User "@b28e83be-7933-4609-88c6-3752f3d9e8a6" disconnected (0 users remain) guacd[948]: INFO: Last user of connection "$464a76e4-48b9-4a35-a8b1-f46fd2646f22" disconnected guacd[14]: INFO: Connection "$464a76e4-48b9-4a35-a8b1-f46fd2646f22" removed. guacd[14]: INFO: Creating new client for protocol "rdp" guacd[14]: INFO: Connection ID is "$464a76e4-48b9-4a35-a8b1-f46fd2646f22" guacd[948]: INFO: Security mode: ANY guacd[948]: INFO: Resize method: none guacd[948]: INFO: User "@b28e83be-7933-4609-88c6-3752f3d9e8a6" joined connection "$464a76e4-48b9-4a35-a8b1-f46fd2646f22" (1 users now present) guacd[948]: INFO: Loading keymap "base" guacd[948]: INFO: Loading keymap "en-us-qwerty" connected to 192.168.1.186:3389 creating directory /root/.config/freerdp creating directory /root/.config/freerdp/certs creating directory /root/.config/freerdp/server certificate_store_open: error opening [/root/.config/freerdp/known_hosts] for writing SSL_read: Failure in SSL library (protocol error?) SSL_read: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error guacd[948]: ERROR: Error connecting to RDP server I have not changed or disabled any RDP parameters on the Windows 10 box aside from simply enabling Remote Desktop itself. The connection is set up to use NLA (Win 10 default from my reading) and Ignore Server Certificate. Any thoughts? I can connect fine via Mac RDP and Windows RDP clients to this box.

StarTech.com 4 Port PCI Express (PCIe) SuperSpeed USB 3.0 Card Adapter w/ 2 Dedicated 5Gbps Channels Chipset: Renesas/NEC - µPD720202 Findings: Purchased this because it had 4 individual USB controllers on the board thinking the extra price would allow for more flexibility with my VMs. Requires SATA/Molex power, works fine when booting native to Windows 10. It is recognized in Unraid under Settings -> Hardware however when passing through the PCIE card to a VM, while the card is detected, it always has an error with Code=10. This is with the standard Windows drivers and also with the drivers from the manufacturer's website. There are other posts online with the same result (Code=10 error in Device Manager) but not promising workarounds. I suspect this is something at the Linux level as when I do not pass through the PCIE card and hook up USB devices directly to the card, they also are not recognized by Unraid. I give up on this card.

Piling on to this thread. Spent $80 on this card thinking it would work and it recognizes and then just Code=10s in Device Manager :(

So I've done a semi-equivalent of what you guys are doing here except I'm using scp to pull my key down from an AWS micro instance (might switch this to a Pi Zero on premise though - thoughts on drawbacks/benefits here?) that is always on. I like the examples where I can delete the key after the disks are mounted which is why I stumbled onto this thread. One idea I had was to somehow enhance the scp/ftp/whatever protocol process to somehow fire off a process on the remote machine that holds the key to send maybe an SMS text to my phone where I respond with a PIN code to allow the key transmission to take place. Are there any inherent flaws with pursuing this? One concern I have is there will obviously be a lag between when the ssh command between Unraid go script and the key and be transmitted back and then it's a race condition? Is there a shell command on the Unraid side that I can call again to mount the drives once the file has been received?