Forum Replies Created
-
Posts
-
Hi Juerg,
Can you please tell us, if the issue occurs when you are connecting to the login screen or if it doesn’t?
Thanks
Hello Swmmrman,
Thank you for sharing, we are glad that it works for you!
If you want to work on the audio problem, we can support you – just let us know.
Best regards,
Hello davide445,
“Since is working for the first I suppose there is no need to configure port forwarding or UPnP on my local router”
If it’s a local connecion then there is no need to configure anything, and there is no specific configuration that need to be done on Windows 10 to make him accept a connection; it should work out of box.
Can you please send us logs, it will provide us more information. You can send them to forum(at)nomachine(dot)com, making sure you reference the topic as subject.
If needed, the procedure to gather logs is explained here: https://www.nomachine.com/DT10O00163
Hi Juerg,
We have a trouble report that could be related: “Caps lock is no longer synchronized when it’s enabled whilst user is connected to the Windows 10 login screen” (https://www.nomachine.com/TR11P08979).
Can you check and tell us if your reproduce that issue on the Windows login screen ?
Hello Eugene,
Having analysed your scenario further, we are sorry that it doesn’t work over the internet.
NoMachine Network is the product you need.
You can tick the box in the feature request to be notified when it is released: https://www.nomachine.com/FR07J02731
Hi soldier89757,
here’s the summarised explanation.
nxd is NoMachine service for NX protocol, it is like sshd, it is listening (by default on 4000 port) and accepting user connections;
nxserver: nxserver –daemon process is responsible to start and monitor all NoMachine processes (nxd, nxnode, nxhtd) and to detect the physical session. Every user connection is handled by separete nxserver process;
nxhtd is the service for NoMachine web access;
nxnode: this node is responsible for the actual session, physical or virtual.
Hello catalina,
Thank you for reaching out to us.
This feature is currently in production, but no release date has been set yet.
We have a Feature Request for it (https://www.nomachine.com/FR03M02897), you can tick the box at the bottom (‘notify me’) in order to receive an e-mail when it is released.
Best regards,
Hello svanimisetti,
Thank you for reaching out to us.
This feature is currently in production, but no release date has been set yet.
We have a Feature Request for it (https://www.nomachine.com/FR09H02385), you can tick the box at the bottom (‘notify me’) in order to receive an e-mail when it is released.
Best regards,
Hi Eugene,
Thank you for contacting us.
Before going further, can you confirm that you followed the procedure explained here: https://www.nomachine.com/getting-started-with-nomachine
If yes, we will need to investigate further.
Thanks in advance for your feedback.
Hi merl77,
Can you confirm that you are on a physical session, and if you use nouveau drivers or proprietary ?
If you use proprietary, we suggest to try a different version of these drivers.
Please also tell us the version of the drivers, to allow us to try to reproduce the problem.
Hi hpb,
Thanks for updating us, it’s nice to read it.
Feel free to show off your achievements with NoMachine!
Hi argentoguy,
The patch has been sent to you by e-mail.
Please follow the standard procedure to gather logs from the server: https://www.nomachine.com/DT10O00163
To set debug level, please set
SessionLogLevel 7
in /usr/NX/etc/server.cfg
Restart nxserver.
Then after the issue occurs upload the logs, and send them via e-mail.
Hello Mantelis,
You can get your public IP address:
– if UPnP is enabled, by typing in CMD: “C:\Program Files (x86)\NoMachine\bin\nxserver.exe” –upnpstatus (with the quotation marks)
– from websites such as whatismyip[dot]com by example.
– on the router page – it depends on the router.
Could you please describe us exactly what problem you have? Is it only how to get the public IP address, or something else?
Hi dc2008,
Yes it is possible, you will have to change htd.cfg:
from:
”
<VirtualHost _default_:*>
RewriteEngine on
ReWriteCond %{SERVER_PORT} !^4443$
RewriteRule ^/(.*) https://%{SERVER_ADDR}:4443/nxwebplayer [R,L]
</VirtualHost>
”
to
”
<VirtualHost _default_:*>
RewriteEngine on
ReWriteCond %{SERVER_PORT} !^4443$
RewriteRule ^/(.*) https://%{SERVER_ADDR}:4443/nxwebplayer?desktop [R,L]
</VirtualHost>
”
exactly this line:
”
RewriteRule ^/(.*) https://%{SERVER_ADDR}:4443/nxwebplayer?desktop [R,L]
”
it will redirect from
to
https://example.com:4443/nxwebplayer?desktop
In case if you want to make the redirection from the default port (80), to have the redirection from
https://example.com to https://example.com:4443/nxwebplayer?desktop
You will have to add listening nxhtd on 80 port.
Edit htd.cfg file and add those lines:
”
Listen 0.0.0.0:80
”
Make sure that there isn’t any other service listening on that port, before making such a change.
However, there is one thing you should know when doing all of this: when you redirect or simply type by hand in browser’s URL:
” https://example.com:4443/nxwebplayer?desktop ”
the Web Player will try to load ‘desktop.nxs’ connection file, as described in
Hello Jaster,
Please collect logs (server side), following the procedure explained in this document https://www.nomachine.com/DT10O00163.
And send them to forum[at]nomachine[dot]com making sure to reference this forum topic.