- This topic has 3 replies, 2 voices, and was last updated 8 years, 1 month ago by
.
-
Posts
-
Hi all,
I am trying to work with NoMachine free on some XP SP3 machines. Win7 to Win7 testing went fine, so I tried physical WinXP machines, but got the following errors: “Error is 138: Connection timed out’.”
I then went to test NoMachine 5.1.40 on a Windows XP SP3 VM, acting as a server and on a Windows 7 VM, acting as a client.
On first install, I was able to connect from the Win7 machine to the WinXP machine, but there were some performance issues and I started getting dropped by the WinXP machine.
Now the WinXP machine service doesn’t seem to even start and I see some errors in the WinXP logs that say “204 1516 15:56:50 936.841 nxserviceExecuteProcess: Error is 32, ‘Broken pipe’.”
What can I do to get the service running again with a more stable connection?
Thank you.
Our internal tests show there a number of issues with using NoMachine on XP, and we are currently investigating how and if it’s possible to fix them. As soon as we have some news we’ll post it here.
One of the Trouble Reports can be found here: https://www.nomachine.com/TR07M05704 which is still open. You can sign up to receive notification when its fix is available.
This topic was marked as closed, you can't post.