Forum Replies Created
Thanks Dawid, I have come across that article and tried to follow all of the steps. It did not get me any closer to getting Smart Card Authentication or USB forwarding to work.
It has been uninstalled and reinstalled multiple times, with reboots in-between. There is no mention of “NoMachine USB Hub Filter” in the Windows Registry.
Thanks for differentiating between the different modules.
My main concern is this:
With Enterprise Client 6.11.2 installed, I am able to connect a USB drive from the client to an Enterprise Desktop 6.10.12 machine. The server has complete access to the client USB device. No problems here.
If I uninstall Enterprise Client 6.11.2, perform three restarts and then install Enterprise Client 7.0.208, I receive an error for the USB adapter install. Why the USB module fails with version 7 and not 6 is beyond me.
My concern is what happens if version 7 is applied over version 6. The installer for 7.0.208 will remove 6.11.2 and install as normal, however, there is no error for the USB adapter install, even though it does not install correctly.
Users installing version 7 over version 6 may lose the ability to connect USB devices and there is no indication from the installer.
Definitely agree. I really enjoy the default options for remote sessions, especially the “scale to window” option. Trying to explain that to non technical users was, entertaining. Now it just works out of the box.
Install and device logs have been emailed. Additionally, I’ve sent the failed connection logs for smart card authentication using NX and SSH protocols.
Most users authenticate to the Windows AD Domain using their smart card, they insert their card into the reader and enter their pin.
Smart card users do not have password authentication.
1. Users insert their smart card into a USB card reader at their workstation.
2. Users enter their pin at the logon prompt and are granted access to their Windows workstation.
3. Users launch the NoMachine Enterprise Client and connect to the NoMachine Enterprise Server.
4. Since users have no passwords, they must use a Smart Card to authenticate the remote connection.
5. Once connected to the server, the user must then authenticate again into the domain on the server, hence the need for USB forwarding.
I hope this provides some clarity into what I need to accomplish.
Thanks for taking the time to help.
Thanks for the help Britgirl,
I was able to get it sorted it out.