Forum Replies Created
-
Posts
-
Hi, this would appear to be a problem with Firefox profiles. More information about that is on their website. You mentioned a “virtual display”. Firefox will use the same profile for both the original OS and the virtual one that’s running. I think this could well be the issue.
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Have you tried with another browser, for example Safari?
Did NoMachine give any error messages at all?
The related Trouble Report for this topic is https://www.nomachine.com/TR03P08450.
Please sign up to receive a notification of the patch when it becomes available. Thanks!
From the logs we can see it was a network issue.
When the NoMachine (server) computer is behind a NAT router or a firewall, NoMachine tries to use the UPnP or NAT-PMP protocol (depending on what is supported by the router) to:
– Retrieve the public or external IP of the host machine where it’s installed.
– Configure the router to allow a NoMachine client to connect from outside of the private network.
Further reading:
How to connect to NoMachine when the server is behind a NAT router or a firewall
https://www.nomachine.com/AR11L00827So, we’ll need the logs 🙂 because we’re unable to reproduce this behaviour. Server-side logs can be extracted using the instructions here: https://www.nomachine.com/DT10O001630.
For client-side logs it’s enough to tick the box “Don’t delete log files on exit”. Send what you have to forum[at]nomachine[dot]com making sure to reference your topic.
Statistics would be very useful: https://www.nomachine.com/DT10O00157&dn=menu%20panel#9. Run the session, open the menu, click Connection and click “Take the statistics”.
Thanks 🙂Re-reading my earlier reply I realise my answer was a little incomplete. We generally suggest to upgrade to the latest version, even more so if there is a quite a difference between the version one has installed and the version available for download 🙂 That’s because there are many improvements that are implemented between one version and the other which are not back-ported to the older major.
So we can check whether the problem you are experiencing is one that has been resolved in a later version or whether it is also affecting the most recent version 6, please submit the logs (to forum[at]nomachine[dot]com) by following the instructions here:
https://www.nomachine.com/AR10K00697
Thanks!
Hi David,
on VMs on the same machine is fine, but ETS must be on one VM and TSN on a separate VM (just wanted to clarify that in case other readers are wondering). Can you tell me what virtualization software you’re using for the VMs?
Can you try connecting from a completely different client machine? Try from a different Windows computer and, if possible, a different OS. Is the problem still there?
NoMachine 4 Win 7 VM
If you are using version 4, I strongly suggest you update to the latest version which is v6 – both sides.
We got the logs and took a look. No indication of what could be happening.
They are from Enterprise Terminal Server which, I assume, you are using to connect to a number of Terminal Server Nodes. The problem is therefore on the Terminal Server Node and the logs must be enabled and extracted from the affected node.
Please clarify your set-up by confirming:
Enterprise Terminal Server and OS and version?
Terminal Server Node and its OS and version?So far we have been unable to reproduce the issue affecting your session.
Hi, before we go further, can you please disable HW decoding as Fra suggested and tell us if that helps?
“Disable client side hardware decoding” in Display settings in the session menu
We tested on the fly with SpyderPython and we weren’t able to reproduce the behaviour you are seeing. I can send you details on where to submit logs via email if disabling client-side HW decoding has no effect.
With any of the Terminal Server products, connecting to the physical display of the host is possible for those documented here:
https://www.nomachine.com/DT03O00126#10.4.
Connecting to the physical desktop of a Workstation is possible for Admins and trusted users. Authorization is implicit because they’re either admin (so need to do unattended admin stuff) or they are trusted. A non-owner can connect to a virtual desktop of the Workstation and authorization of the owner will be required.
@dmoors, there may have been a little confusion about what you need to send us. We received logs from the server component installed on your connecting client 🙁
What we need is:
– server logs from the server you are connecting to (the Enterprise/Terminal Server ?, you mentioned previously)
– client-side logs of the client component
The instructions are those that Fra mentioned previously. Btw, if you have a Subscription of Enterprise Server, might I suggest you open a support ticket from your customer area? Customers are provided with an upload area for logs.
@inscara, are you connecting to a NoMachine server version 5 or 6?