Forum / NoMachine for Windows / Problems with NoMachine on Windows 10
- This topic has 14 replies, 6 voices, and was last updated 3 years, 7 months ago by Britgirl.
-
AuthorPosts
-
December 28, 2020 at 18:31 #30979DisasterParticipant
Hi
I have recently updated my computer to Windows 10.
Before that i was on Win7 and all NoMachine functions work very well.
But now it doesn’t work.
I explain:
I cannot connect to the NoMachine server running Windows 10, it say “error 108” or “104” sometime. “no available session”.
First thing:
If I’m not logged physically on the server, it can connect but freeze just after hit the ok button for password…
If I’m already logged on this server physically it could not connect and say error 108 or 104. no available session.
Second thing:
Server doesn’t show the public address in the setting. This is on every Win10 machine. Why ? before on win7 it works very well …
Forry for my English i’m French
Best regards
December 28, 2020 at 18:45 #30983BritgirlKeymasterNoMachine works on Windows 10 out-of-the-box as it did with Windows 7. Has something changed on your network since you updated? For example, is your Windows NoMachine server on the same network as the connecting client? By the way, which OS are you connecting from?
Next, have you installed version 7 of NoMachine software on both computers?
What specific update of Windows 10 are you running on the NoMachine server side?
Please gather server side logs as explained in https://www.nomachine.com/AR10K00697. You can send them to forum[at]nomachine[dot]com.
December 29, 2020 at 09:37 #30986DisasterParticipantThere was no change in my network, i have only change the main drive of the server because the SSD who’s running Windows 7 died and I decided to upgrade to Windows 10 on the new one. That the only change in the house.
I run NoMachine in local network to pilot my computer “server” (plex etc…) who are in the basement of the house.
The other “Gaming” computer are upstairs and I want to pilot with this one.
I want to pilot with my smartphone too when I go away from home. (samsung note9)
It works very well before my SSD died lol
Every computer have Windows 10 last update so i think its: 20H2
Last version of NoMachine are installed on each computer.
I have install / desintall on each sides no ways
I ll send the logs files as soon as possible.
Best regards
December 29, 2020 at 16:49 #31008MthContributorHello.
The problem is with starting of nxclient –monitor process.
Unfortunately it is started as standard user and the logs will be saved in the home directory.From the main logs the path in this case should be ‘C:\Users\Disaster\.nx\’
Just to be on the safe side please send us the whole ‘.nx’ directory to the same address.
/Mth
December 29, 2020 at 18:22 #31021DisasterParticipantHello.
i have send it but the folders weight is 18mo so i host it on onedrive.
there are 64000 files inside lol
December 31, 2020 at 12:12 #31065BritgirlKeymasterWe’ve found the cause and opened a Trouble Report.
Connecting to the Windows physical desktop is not possible when the system account name contains non-latin characters
https://www.nomachine.com/TR12R10003December 31, 2020 at 12:31 #31067BritgirlKeymasterWe can provide a patched component for you to try if you’re interested. I’ve sent you a link to the download package. Please check for emails from the forum.
January 4, 2021 at 09:04 #31095DisasterParticipantHi. Happy new year.
Of course I will test that patch as soon as possible.
Hope it will work.
Thanks a lot for helping me. You do amazing job!
January 4, 2021 at 09:06 #31097DisasterParticipantIt works! You are amazing ! I have never seen devs doing a personal patch for customer, you are the best! Keep it up!
I don’t know why it work before on win7. I have never change my computer’s name since 15 years.
Big Up to NoMachine team !
Takes care.
Best regards
January 4, 2021 at 09:58 #31112BritgirlKeymasterHi, I’m pleased to know the patch worked 🙂 Using an earlier version of NoMachine probably would have produced the same results, so it was just easier if we sent you a working version from the start, at least that way you can use the software again rather than wait for the next maintenance.
Why it happened…. Could it be that you had Win7 set to English and then in Win10 you chose your native French? Maybe that Win10 translates the system username?
January 5, 2021 at 10:18 #31125DisasterParticipantI don’t know and i used exactly same system name. The fault is win10, its a purge lol !
January 12, 2021 at 10:11 #31211rempaParticipantHi,
I am having the same problem on my computer.
Will I be able to receive the patch too please?Thank you !
Best RegardsJanuary 15, 2021 at 15:15 #31284cstaffbradParticipantHi,
I am having the same problem on my computer.
Will I be able to receive the patch too please?Thank you !
Best Regards
Error: from the session log:
ClientSession: Failing reason is 'The connection with the server was lost.
Error is 108: Connection reset by peer.'.
January 18, 2021 at 12:35 #31296MeumdavParticipantHello,
same here. Could you please kindly send me the patch ?
Thanks
Kind regards
April 7, 2021 at 08:59 #32795BritgirlKeymasterThe patch was officially released in 7.1.3.
-
AuthorPosts
This topic was marked as solved, you can't post.