September 21, 2020 at 09:06 #29529
I just finished building a new system Asus Tuff Z390 gaming WiFi edition. When I finished the install I added NoMachine to the system. Upon reboot, multiple NoMachine icons showed up in systray moving all over the place and I couldn’t go into the settings to do anything. I uninstalled and reinstalled with the same results. This is the first time that I have noticed this on a build and I’ve done about 10 so far with NoMachine added.
Any guesses or better suggestions?
ThanksSeptember 22, 2020 at 08:57 #29557
I forgot to mention that both machines running latest Windows 19042.508 with latest NoMachine version. Connection is physical and I am using onboard graphics. The hourglass kept turning and turning as if NoMachine was trying to create a connection.
This system has WiFi integrated card.
Thanks for all my issues. I’m not very good with NX connections. 🙁September 23, 2020 at 16:01 #29590
Please submit logs. The logs that you already sent for the other topic, do they contain also information about the session when this happened? If not, we’ll need a fresh set.September 24, 2020 at 08:42 #29594
It is almost impossible to copy the folders. Like I said !M icons are popping in and out all over the systray and creating folders over and over. I will send what I was able to extract.
Thanks.September 24, 2020 at 08:42 #29595
BTW, it’s not the same system.September 24, 2020 at 08:45 #29600
If it’s a different computer, then you were right to send us new logs. Thanks.September 24, 2020 at 16:18 #29603brotechParticipant
you send logs of nxclient – .nx from userhome which is not enough to find a reason of problem appearing on your host,
please send to us logs of nxserver of the affected computer, the procedure and paths are here:
1.4. Server on Windows
[…]September 25, 2020 at 08:54 #29615
I just sent the updated files. I hope that it gives you a clue. I just keep seeing a bunch of icons popping up in the systray and I can see that it’s creating a bunch of folders in the log section.
5080 1432 21:13:30 420.106 Utility: WARNING! Changed environment HOME to C:\Users\Admin.
5080 1432 21:13:30 420.106 Utility: WARNING! Changed environment USERPROFILE to C:\Users\Admin.
5080 1432 21:13:30 420.106 Utility: WARNING! Changed environment HOMEPATH to \Users\Admin.
5080 1432 21:13:30 420.106 Utility: WARNING! Changed environment HOMEDRIVE to C:.
5080 1432 21:13:30 420.106 Utility: WARNING! Changed environment LOCALAPPDATA to C:\Users\Admin\AppData\Local.
5080 1432 21:13:30 420.106 Utility: WARNING! Changed environment TEMP to C:\Users\Admin\AppData\Local\Temp.
5080 1432 21:13:30 420.106 Utility: WARNING! Changed environment TMP to C:\Users\Admin\AppData\Local\Temp.
5080 1432 21:13:30 420.106 Utility: WARNING! Changed environment APPDATA C:\Users\Admin\AppData\Roaming.
5080 1432 21:13:30 432.720 OsDetect: Setting os type to ‘Windows’.
5080 1432 21:13:30 432.720 Main: Creating a new connection monitor.
5080 10772 21:13:30 432.720 MdnsdListThread: WARNING! Could not open directory ‘C:\Users\Admin\.nx\cache’.
5080 1432 21:13:30 685.101 ClientThread: Creating new thread.
5080 6284 21:13:35 433.752 IoMonitorPid/PidMonitor: ERROR! Watchdogged process 8096 exited.
5080 6284 21:13:35 433.752 System: ERROR! Killing the process 5080 with watchdog signaled.
Error: Killing the process 5080 with watchdog signaled.
5080 6284 21:13:35 433.752 Process: WARNING! Dumping stack for thread 6284:
5080 6284 21:13:35 433.752 Process: #0 0x75d78930 msvcrt.dll(unlock).
5080 6284 21:13:35 433.752 Process: #1 0x75d89bd9 msvcrt.dll(fwrite).
5080 6284 21:13:35 433.752 Process: #2 0x67728dfd libnx.dll(Z11ProcessKillv).
5080 6284 21:13:35 433.752 Process: #3 0x67743a1f libnx.dll(ZN6System12handleSignalEi).
5080 6284 21:13:35 433.752 Process: #4 0x677466c2 libnx.dll(ZN10PidMonitor8eventPidEv).
5080 6284 21:13:35 433.752 Process: #5 0x773df5f2 KERNELBASE.dll(WaitForSingleObject).
5080 6284 21:13:35 433.752 Process: #6 0x6774532b libnx.dll(ZN10PidMonitor9notifyPidEv).
5080 6284 21:13:35 433.752 Process: #7 0x75f3f989 KERNEL32.DLL(BaseThreadInitThunk).
5080 6284 21:13:35 433.752 Process: #8 0x77eb74b4 ntdll.dll(RtlGetAppContainerNamedObjectPath).
5080 6284 21:13:35 433.752 Process: #9 0x77eb7484 ntdll.dll(RtlGetAppContainerNamedObjectPath).September 25, 2020 at 16:21 #29629
I sent the files. But I found the problem.
I would also like to share a remark. Is it necessary to moderate every post even after a user has been identified as legit? In my 20 plus years of doing desktop support this the first time that I have seen a forum that moderates all posts. It’s long and strenuous. I understand that trolls can be annoying but this forum is based more on concrete help and not opinions on any and everything.
I’m sure I’m not the first to suggest this. Thanks.September 25, 2020 at 16:31 #29633
To answer your question about moderation, we moderate everything because unfortunately trolls, like you rightly mention, are frequent as are spammers as are shills, so whilst this is indeed a public forum in that anyone can join and comment, it also means that the few who don’t behave force us to monitor constantly. I think it’s a small price to pay for free help from our developers who are the main contributors here in this forum.September 25, 2020 at 16:34 #29634
I sent the files. But I found the problem
Thanks for letting us know by the way, but what was the problem?September 25, 2020 at 16:49 #29635
From the logs it would appear that you are using unicode characters in the hostname. And this is a known issue.
Cannot start the nxnode program on Windows if hostname or username contains non-Latin symbols https://www.nomachine.com/TR12M06315September 28, 2020 at 08:07 #29636
Sorry, you hit the nail on the head!!
I run most computers in French Canadian. I had named the computer guêpe. I hadn’t though of it and I looked at the logs and figured also that that was the issue. I renamed it and all is well.
You are great detectives! Thanks.
You must be logged in to reply to this topic.