Forum Replies Created
-
Posts
-
Regarding NoMachine products and version… is this a known bug affecting certain versions? I am always updating whenever there is an update available so I suppose it’s the lastest. Server shows it’s 7.7.4
I don’t really understand why you ask this, but OK maybe I could have Windows 11 instead of 10 if that could make any issues…
1st machine is Windows 10 pro 20H2 and I am connecting to Windows 10 Enterprise 21H1
Right now when I was connected the numpad didn’t work at all on the target machine (like it was switched off), but on the host machine numlock was on and I could type numbers normally. So I tried switching it off and reconnect, then I switched it on with NoMachine window in focus and the result is again what I describe – only every other keystroke is being recognized. On machine I am connecting from it works just fine.
So it works now. Not sure what was the problem, but likely the ip address of the machine changed and I was actually connecting to some other PC on the network :-]
Reboot of the target machine seems to be working as workaround, but it’s not practical to close and open all the apps again :-]
well this is really weird. Yesterday it worked. Today it worked. Then I got an NoMachine update alert, so I did the update and AFTER it I can’t connect and have the same error!
I checked nestat -a and utility TCPView but NONE of the ports mentioned in nxserver.log as used by another application are there as listening or established! Seems like an error in your application or something weird in my system blocking the NXTryBindLocal function :-\
Funnily enough today it started to work again! But I am nervous if it happens again what will I do. Wait until next day? :-]