Forum Replies Created
-
Posts
-
you have file transfer, not folder transfer unless you zip. Also you can’t drag and drop from one machine to another.
File transfer is done via the !M in the system tray from the remote computer to the local desktop. You’ve probably seen the tutorial here: https://www.nomachine.com/sharing-files-between-computers
By folder transfer, do you mean ‘Connect a disk or drive’? You can do that via the connection menu.
– Start a connection from your computer to the remote computer you want to access.
– Once connected, open the session menu (Ctrl-Alt-0).
– Go to Devices and click on ‘Connect a disk’.Any disk drives available either on your PC/Mac or the remote one will show up like below, and you select the one you want to access.
A remote disk will show up in your local file explorer or finder. A local disk or drive will show up in your remote desktop’s explorer or finder.
Can you try this and let us know that it works?
Drag and drop should be working. Can you confirm what the OS and version is on your side and what you are connecting to? And what type of file are you trying to drag?
What’s the desktop environment? If you’re running Wayland, we don’t support that protocol yet, but it’s coming soon. Please see the associated feature request here: https://www.nomachine.com/FR10N03221. It includes a workaround.
From the log extracts it seems to be an X.org problem rather than a NoMachine problem. If you can send us some complete backtraces from X.org we can try to help you with debugging by taking a look at them. There is a useful guide with tips on debugging the Xserver on X.org Foundation website: https://www.x.org/wiki/Development/Documentation/ServerDebugging/
After further investigation, we found a bug which is most likely affecting you. When changing network the the new IP does not show in the Welcome Panel. It’s now been queued up for fixing and you can see it here: https://www.nomachine.com/TR01P08354. Use the ‘notify me’ tool to find out when a fix has been released.
Can you restart the nxserver on the affected host? Does it help?
The option disables the use of DirectX which NoMachine uses DirectX to capture images from applications. We are currently investigating why some users have observed this unusual behaviour.
From the logs it seems that the router wasn’t ready and so nxserver skipped portmapping. Please run again
nxserver --upnpstatus.The logs didn’t show any information that would help us to understand where the problem is other than that we don’t receive any information from the router. Is it at all possible that UPnP is still disabled on the router?
This might be helpful for enabling it on the problematic router.
From an earlier post we understand that your friend’s router is the same model as yours – does it have the same version of firmware and are the firewall rules the same? Can you enable UPnP on the router and restart the router?
Can you send those session logs directly to forum[at]nomachine[dot]com?
Also, confirm that what version of NoMachine is installed on the server and also on your Windows client. What OS & version is the server as well?
Thanks!
What product and version from NoMachine did you install on the connecting client?
What product and version from NoMachine did you install on the remote server?
If you have an Enterprise Desktop Subscription, you can get access to the support team by logging in with the customer ID and password you received at the time of purchase 😉
Switching to the production version shouldn’t trigger such problems with logging in or multiple processes. These need to be investigated thoroughly: the support team will be able to assist you further.
Logs show that there’s a bug in the UDP code. A temporary workaround is to disable UDP in the connection preferences. Sign up to receive notification of the fix using ‘notify me.’
Some things you can check are that
EnableUPnP NXis uncommented in the server.cfg i.e you should make sure it’s without ‘#’ 🙂
And if you open a terminal window on the server (cmd) and runnxserver --upnpmap(it has to be executed once you’re in the %ProgramFiles(x86)%\NoMachine\bin directory) it should show the external IP and port.If that still doesn’t work we’ll need the logs (see my instructions from an earlier post) and
nxserver --upnpmapoutput.We’re not able to reproduce this behaviour at all. What’s the version of Chrome and Chromium you can reproduce this problem on?