May 13, 2020 at 15:44 #27423
I’ve updated our Cloud Server to 6.10.12, along with a Mac and Windows 10 Enterprise Client. Neither no longer connect to the Cloud server by the desktop app.
After clicking Connect to the Cloud Server, I’m asked for the credentials, which it accepts (it rejects false credentials). It then just states ‘Connecting to…’ with the spinning beach ball until I close the window. Once the Window 10 client stopped and said the connection to the server was lost. At this point it allowed me to save some logs. In the Session log, this is repeated:
log4cplus:ERROR No appenders could be found for logger (AdSyncNamespace).
log4cplus:ERROR Please initialize the log4cplus system properly.
Qt: Untested Windows version 10.0 detected!
Both the Cloud Server and Enterprise Client are running Windows 10 Pro 1903
I can connect OK via the web browser from both the Mac and PC.
I’ve tried reinstalling the Enterprise client on both computers, resetting preferences etc.
Can anyone help?
TomMay 13, 2020 at 16:28 #27440
Just to add: Rolling back the Windows 10 Enterprise Client to v6.9 allowed me to connect to the Cloud Server again.May 14, 2020 at 16:15 #27483
Tom5, can you send us the user/.nx from your Windows Enterprise Client? Then from the Cloud Server host, send us the var/log. Instructions are here: https://www.nomachine.com/AR10K00697.
Then send everything to forum[at]nomachine[dot]com. Make sure you place the title of the topic in the subject. Thanks!May 15, 2020 at 15:31 #27522
Thanks for the reply. I’ve just emailed the requested log files.
TomMay 19, 2020 at 08:31 #27608
I’m having this problem too, can’t connect 6.10 clients to 6.9 cloud server, it just hangs. Had to revert all clients to 6.9 for now.
Any updates on this?May 19, 2020 at 15:05 #27620
Hello mw32. Not yet. I’ll update here when I do.May 19, 2020 at 17:45 #27639
This is a race condition due to network speed and server load. Closing the connection and trying to connect, even multiple times, can sometimes help.
NoMachine client never stops showing the spinning wheel when connecting to a server
If you need a quick fix, try setting the
ClientMenuConfigurationkey in the server.cfg on the server to the default value, i.e. comment it out:
Such a change doesn’t require a restart of NoMachine server
Does the fix help?May 20, 2020 at 08:48 #27652
Thanks, that seems to have fixed it for now.
However, I had hidden most of those options before within the server/node.cfg files on the workstations. Now they are showing up again on the client interface (recording, USB, devices). They are disabled/non-functional, but not hidden as before. Not sure if this is related or separate issue (or I’m remembering incorrectly ;o).May 20, 2020 at 17:04 #27674
So with 6.9 we had this in the server.cfg for the Cloud Server and Workstations
When a client connect to the CS and then to WS, all others would be disabled (devices, USB, network, etc.)
So when I commented that line out in the CS to get the 6.10 client to connect, not when someone connected to a WS through the CS, those options are enabled in the menu again (they don’t work because I have them disabled elsewhere in the config, but you can click into the menus).
It seems really weird that the config on the CS is overruling the config on the WS for the client.
It’s OK for now, just didn’t know if that’s a unknown bug or how its supposed to work.May 21, 2020 at 07:15 #27685
Thanks for the quick reply. That workaround has worked for us, and showing connected users in Cloud Server is more important to us than hiding menu items at this stage.
6.10.12 seems to have broken disk sharing though. I’ll create a new post about this.
Thanks for your help! TomMay 21, 2020 at 11:01 #27706
Hello tom5 and mw32, please check for emails from our forums which include links to a patched package.May 21, 2020 at 13:20 #27707
Thanks again for all of your efforts with this. With that updated package, I can now connect to the cloud server and various menu items are hidden. Tested OK on a Mac and PC client. Wonderful.
As mentioned, I’ll now see if this updated package has had a positive impact on the USB sharing and disk sharing posts I created.
You must be logged in to reply to this topic.