Error is 138: Connection timed out Forum / NoMachine for Windows / Error is 138: Connection timed out This topic has 2 replies, 2 voices, and was last updated 9 years, 3 months ago by othplay. Viewing 3 posts - 1 through 3 (of 3 total) Author Posts August 11, 2014 at 14:19 #4439 othplayParticipant NoMachine Version – 4.2.26 I try to connect from one laptop with Windows 7 enterprise to one desktop with windows 7 enterprise. I got an error with “Error is 138: Connection timed out”. I did the following test. 1. I can connect to the desktop using Remote Desktop Connection from the laptop. I think the IP and the desktop is fine for connection. 2. Then I tried the connection to the desktop from another laptop which running NoMachine with the same version. It works with the new laptop. So I think the connection to the desktop is no problem with the desktop. The problem may come from the 1st laptop. 3. I checked the fire wall of the 1st laptop and I found that NoMachine is allowed. I stopped the real time protection. I still can’t connect to the desktop with the 1st laptop. I don’t know what I can do to fix the connection problem for the 1st laptop. Could you please help with this? Best regards This topic was modified 9 years, 1 month ago by Britgirl. August 12, 2014 at 09:13 #4443 BritgirlParticipant Do any of these posts help? https://www.nomachine.com/forums/topic/error-is-138-connection-timed-out#post-4339 https://www.nomachine.com/forums/topic/cannot-connect-to-server Are you able to connect from the PC (the desktop you were trying to reach) to the first laptop? August 13, 2014 at 08:00 #4450 othplayParticipant Thank you for your reply. I still can’t connect to the desktop from the 1st laptop. But I can connect to the desktop from the 2nd laptop. I may reinstall the 2nd laptop in the worst case. Author Posts Viewing 3 posts - 1 through 3 (of 3 total) This topic was marked as closed, you can't post.