Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Guest

Re: SSH to AWS EC2 instance using WinSCP not connecting after Windows 10 Pro update

Hi Martin.

martin wrote:

Can you connect with any other machine?

Before I started on my Windows 7 Pro m/c, I checked the IP address of my PC and it had changed for some reason unknown to me (Windows??).
So I adjusted the security access in my AWS instance and I'm now able to connect.

Thanks for your time.
Cheers
martin

Re: SSH to AWS EC2 instance using WinSCP not connecting after Windows 10 Pro update

Can you connect with any other machine?
krot

SSH to AWS EC2 instance using WinSCP not connecting after Windows 10 Pro update

Hi:

WinSCP Version 5.15.2 (Build 9590)
Windows 10 Pro 64bit - Version 10.0.17763 Build 17763
SFTP
[/url]
Error ..
Network error: Connection to "ec2-52-60-88-185.ca-central-1.compute.amazonaws.com" timed out.

I've been able to access my AWS EC2 instance perfectly to date.
Immediately after the Windows 10 Pro update on July 11, 2019 WinSCP gave the above error message on logging in.

I rebooted the PC and tried again. Same.
PuTTY was also unable to access the instance.

In order to see if the AWS EC2 instance had issues I followed the advice at
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html
and it showed all as it should be.
AWS EC2 Instance uses IPv4

Windows Defender Firewall is not active.
Norton Security has not changed. The WinSCP setting in the Norton Security firewall:
WinSCP SFTP, FTP, WebDAV, S3 and SCP client -> Allow

Log attached.

Any ideas on how I can restore the connection?
Cheers