Forum Replies Created
-
AuthorPosts
-
BilbotineParticipant
Hello cjm51213,
Please check again if ‘C:\ProgramData\NoMachine\var\log\’ directory doesn’t exist.
If you didn’t notice any errors during installation, it’s very unlikely that this directory wasn’t created.
If you find the directory, please send us the logs gathered using instructions: https://www.nomachine.com/DT07M00098.
If there’s no log directory, try reinstalling NoMachine application.
Should the problem persist, please send the ‘C:/Users/<USER_NAME>/AppData/Local/Temp/Setup-Log….2016-06-…’ file to forums[at]nomachine[dot]com using this topic as subject. If there are multiple files starting with ‘Setup-Log’ send them all.
Kind regards,
BilbotineParticipantHello tyman,
Please read the article ‘How to connect to NoMachine when the server is behind a NAT router or a firewall’ (here: https://www.nomachine.com/AR11L00827), it should help you.
Please let us know if you need further assistance.
Kind regards,
BilbotineParticipantHello again tryptych,
NoMachine guides for the enterprise mentioned previously apply to all server products except NoMachine free which has its own manual.
Since NoMachine Enterprise Desktop doesn’t support virtual desktops, sections related to virtual desktops do not apply.
– ‘Which versions of Linux is it compatible with?’: on the download page of each product you can find the list of supported Linux platforms. NoMachine officially supports RHEL 7, but it is suitable also for CentOS 7.
– ‘What is the name of the service on Centos7?’: the name of NoMachine services is pre-pended by the ‘nx’ keyword.
Main services are nxserver.bin and nxd, which is the NoMachine network service listening by default on port on port 4000 and ready to accept
connections by NX protocol.
– ‘How do I restart the service, or check it’s status?’
i) you can do that from the command line (see: https://www.nomachine.com/DT07M00090#3):
/etc/NX/nxserver –restart
/etc/NX/nxserver –status
ii) or via the graphical interface.
See this guide for the server GUI: https://www.nomachine.com/DT11M00107
– ‘Is any configuration required?’: NoMachine is designed to be up and running and ready to work as soon as the installation is completed. No further configuration is required.
In case of problems, we can assist you for finding a solution.
We suggest to open a Contact Request (at https://www.nomachine.com/contact-request) for describing the problem or to send a new post on the Forums to report the exact issue you are experiencing.
BilbotineParticipantHello tryptych,
You can read the following guides for your NoMachine Enterprise Desktop install: NoMachine Enterprise Products – Server Guide (https://www.nomachine.com/DT07M00090) and NoMachine Enterprise Products – Server Guide – Advanced Functions (https://www.nomachine.com/DT07M00091).
Kind regards,
BilbotineParticipantHello iceback,
We made some further tests, and we verified that the same key combination works with NoMachine Keyboard Grabbing activated.
The equivalent key combination to the MacOSX cmd+P on Windows is: Winkey+p.
You can find more information on how the Keyboard grabbing can be enabled in the ‘Guide to the Functionality in the Menu Panel’, under the section 3 (https://www.nomachine.com/DT10K00060&dn=#3).
Please let us know if your problem is solved or not.
BilbotineParticipantHi jgaalmeida,
Logs failed to attach, for security reasons. Could you send them (server and client side) to forum[at]nomachine[dot]com, making sure to reference ‘NoMachine Service failing on Windows 64′ as subject?
If needed, you can find instructions to gather the logs here: https://www.nomachine.com/AR07K00677
Installation logs would also be useful. In general in Windows 7 they are under <users_home>/AppData/Local/Temp and are the files starting with ‘Setup Log’. Please send the latest of these files.
Thanks.
BilbotineParticipantHello iceback,
It looks like you use ‘command-p’ to show up the menu where you can adjust the video settings (fit to window, full screen and so on). Is that correct?
If so, ‘command-p’ is not our default setting. By default we have ‘ctrl-alt-0’, which is valid on all platforms.
Please check the preferences (see the ‘Input’ menu in the screenshot attached), and let us know if it works now!
Attachments:
BilbotineParticipantHello zavio,
Thank you for reporting this issue. It should be fixed in the next update.
BilbotineParticipantHello Jose,
In order to help you, we need to investigate further.
Can you please send the standard debug logs to forum(at)nomachine(dot)com, making sure you reference ‘Error: Cannot create session directory on server’ as subject ?
If needed, the procedure to gather them is here: https://www.nomachine.com/DT04M00076#1
BilbotineParticipantHello Dream,
Thank you for letting me know. We’re happy it is solved!
BilbotineParticipantHi Andrin,
Can you clarify when you see that error (before log in screen, when you are requested to provide login and password, after that).
Could you also send us logs (server and client side) to forum[at]nomachine[dot]com, making sure to reference ‘Windows 10 pin′ as subject?
If needed, you can find instructions to gather the logs here: https://www.nomachine.com/AR07K00677
BilbotineParticipantHello iceback,
Could you please give us some clarification about magnifying ?
We have tested and do not have any reaction to cmd+p.
Thank you in advance.
BilbotineParticipantHello Dream,
We have a Trouble Report with a workaround for this issue:
‘Cannot reconnect virtual desktop sessions with NoMachine server v.4.6.12’ (https://www.nomachine.com/TR08M05855)
Let us know if you still encounter problems!
BilbotineParticipantHello xinwang,
In order to help you, we need to investigate further.
Can you please send the standard debug logs to forum(at)nomachine(dot)com, making sure you reference ‘RHEL5 authentication to NX server failed’ as subject ?
If needed, the procedure to gather them is here: https://www.nomachine.com/DT04M00076#1
BilbotineParticipantHi RichCrane,
We need more details to investigate this issue.
Could you please send logs (server and client side) to forum[at]nomachine[dot]com, making sure to reference ‘Connect Ubuntu 14.04 from MAC OS X 10.10.4’ as subject?
If needed, you can find instructions to gather the logs here: https://www.nomachine.com/AR07K00677
-
AuthorPosts