Forum Replies Created
-
Posts
-
Hello,
About the USB issue. How did you install the 4.2.27? Did you do an update or completely removed 4.2.26 and then installed 4.2.27? Also could you install 4.2.27 again and check if the USB module was built (check if this file exists: /usr/NX/bin/drivers/nxusb.ko). If not – please go (as root) to /usr/NX/share/src/nxusb/ and execute “make”. If there are errors, please send us the whole output of this command. Thanks.
Hello,
We can confirm that there is module compilation problem on Ubuntu 14.04, but it has already been solved and the fix will be released in the upcoming update.
Hello,
Could you please run cmd.exe as root (Administrator) and show us the result of the following commands:
sc qc nxaudio
sc query nxaudio
C:\Program Files (x86)\NoMachine\bin\nxdeviced64.exe –status nxaudio
C:\Program Files (x86)\NoMachine\bin\nxdeviced64.exe –uninstall nxaudio
C:\Program Files (x86)\NoMachine\bin\nxdeviced64.exe –install nxaudioand see if the problem still occurrs. Thank you.
Hello,
Could you please install NoMachine on the problematic PC where the “Cannot create the home directory for the nx user.” problem exists and send us contents of:
C:\ProgramData\NoMachine\var\log
folder? Please compress it and if it’s too big to attach to forum post, send it to issues [at] nomachine [dot] com. If you already have our software installed on the machine and the problem occurred during the installation you don’t have to re-install it. Just send us the logs. Thank you.
Hello,
You say that the first problem is still reproducible in 4.2.25. Is the second one also still present? If so – could you please send us compressed /Library/Application Support/NoMachine/var/log directory? You can attach it to the forum post, or it it’s too big – send it to issues[at]nomachine[dot]com.
Thank you.
Hello,
Could you please clarify how are you forwarding the device? Are you using the „Devices -> SmartCard Readers” menu or the USB devices forwarding menu? Also could you tell us how are you checking that the device is not available on the remote side?
As for your second issue – this is the normal behaviour when forwarding a USB device. It is being re-attached to our virtual hub on your client machine and all data from the device is being forwarded to the server host.Hello,
Could you confirm that you can log in with no problems to the same host using ssh? If so, please send us the output of the following command (ran as root):
grep -R nxexec /var/log/*
Could you also compress the /usr/NX/var/log and /etc/pam.d directories and send them to us? If they are too large to attach to forum, please send us an e-mail on issues [at] nomachine [dot] com.
Hello,
If firewall is not the issue, please make sure that your VPN is configured in a way that lets you connect to port 4000 on your remote machine.
Hello,
It depends on your VPS service provider. Which one are you using? You should make sure that you can connect to port 4000 on your cloud server (maybe there are some settings in your VPS that forbid this) if you have NoMachine Free. Or you may use SSH protocol with port 22 if you have one of the Enterprise family products. As for Direct Admin and firewall – it’s possible, but to make sure please give us the output of command (ran as root):
iptables -L INPUT -n –line-numbers
Hello,
We’re glad that you are able to connect to your system, but ideally we would need to investigate why public IP publishing did not work using our internal library and worked with the binary we supplied. To do so, we would have to prepare a debug version of the library to gather more information in logs. Would you be willing to help and test it for us?
Hello,
Yes, NoMachine can be ran on EC2. The public IP is not displayed in NoMachine GUI because the UPnP, which is used by us to obtain such addresses, is not compatible with the network infrastructure that Amazon has in their server rooms. It should work on your home or office setup. Nevertheless, to connect to the NoMachine on EC2 you need to use a public IP that is displayed in your Amazon console when you click on your Windows instance and see the “Description” tab. One of the fields reads ‘Public IP’. Please use the address stored there. Additionally you must make sure that port 4000 is allowed for traffic in your security group (same as you did with SSH). After doing so you should be set for using NoMachine to connect to your EC2 Windows.
Hello,
From your post it appears that you’ve ran the command with the wrong syntax. It seems that you’ve ran:
nxupnp.exe -A list 4000 -R <YOUR_PUBLIC_IP> TCP 600
instead of:
nxupnp.exe -A list 4000 -R <OUTSIDE_PORT> TCP 600
To clarify – the argument after “-R” should be a port that will be opened on your router and made available to access from the outside. So, an example of this command would be:
nxupnp.exe -A list 4000 -R 4000 TCP 600
Could you please try to run it with proper syntax and share the results?
Hello,
If you cannot send whole log files, could you please, after reproducing the issue, send us of the following command (ran as root):
grep -R nxexec /var/log/*
Knowing your PAM configuration would be also very helpful, so if you could share the contents of:
/etc/pam.d/nx
/etc/pam.d/su
/etc/pam.d/system-auth
we would be grateful.
Hello,
The USB redirecting should work on every system that has the capability of handling such devices. If your VPS host is, then we’d like to gather some more info about the issue. Firstly – are the Windows machines the same in both (working and not working) cases? Secondly – could you specify what you mean by “failed to connect”? Is the NoMachine GUI showing an error, or the device connects successfully, but is not shown on the remote system? And finally – could you please send us a set of logs following “How to gather node logs” and “How to gather client side logs” instructions from this article: https://www.nomachine.com/AR07K00677 ? An output of the following command would also be helpful:
cat /var/log/system.log | grep usb
Logs and output may be attached to log post or, if they are too long, sent to issues[at]nomachine[dot]com
Thanks.
Hello,
We are aiming for the next release provided there are no technical hitches. Here is the Feature Request for this speciffic case: