Cannot connect to AWS Windows Server 2016 – Error 138

Forum / NoMachine for Windows / Cannot connect to AWS Windows Server 2016 – Error 138

Tagged: , ,

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • October 12, 2017 at 08:49 #16031
    madcat117
    Participant

    I always get this error when I try to connect to my Windows Server 2016 on AWS:

    Could not connect to the server.
    Error is 138: Connection timed out
    My home computer is running Windows 7 Ultimate 64 bit and I used NX as protocol and host as: ec2-52-34-10-16.us-west-2.compute.amazonaws.com

    I used port 3389 and then I select RSA key pair for authentication and used no proxy and it never connects I turned off windows firewall too on AWS server.
    Logs attached!

    Note to moderator: please discard my first post attempt I did not finish my attachment uploads and accidentally hit submit too early!

    October 12, 2017 at 08:53 #16037
    Britgirl
    Keymaster

    Can you submit the logs directly to forum[at]nomachine[dot]com ?

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.