We are not aware of any issues similar to what you have described. A reset of the NoMachine settings might help. This will allow us to see if the problem persists:
1. On Win XP navigate to \etc directory in NoMachine folder (in default is in “Program Files”).
You will see some sample cfg template files: node.cfg.sample and server.cfg.sample. You will also see node.cfg and server.cfg files. You should delete the node.cfg and server.cfg files or if you prefer to keep them, simply rename them node.cfg.old and server.cfg.old. Then rename the sample cfg files to node.cfg and server.cfg. Then restart nxserver – run cmd as a Administrator – navigate to bin directory in NoMachine folder and execute command: nxserver –restart
2. On Win 7 navigate to C:\Users\<your username> and delete or rename (if you want to save old preferences)the .nx directory. After that Create new connection to the XP machine.
And if that doesn’t help, we’ll need to look at the debug logs. Reproduce the problem – send logs from server and client side to forum[at]nomachine[dot]com? Instructions about collecting logs you can find: https://www.nomachine.com/DT04M00076.