Topic: WinSCP

[peterhocking]

Hi everyone

I've built a new SME server with 2 NICs in server-gateway mode.

I've enabled remote access via SSH in the server-manager, set the port I want to use, set Secure shell access to allow public access, (entire internet), set Allow administrative command line access over secure shell to yes & Allow secure shell access using standard passwords to yes. I can connect from a remote PC in another city using SSH, but if I try to connect using WinSCP I get "Network error: Connection refused".

I can connect using WinSCP from my internal network OK.

Can anyone think of what I may have missed?

TIA

Peter

[cactus]

I've enabled remote access via SSH in the server-manager, set the port I want to use, set Secure shell access to allow public access, (entire internet), set Allow administrative command line access over secure shell to yes & Allow secure shell access using standard passwords to yes. I can connect from a remote PC in another city using SSH, but if I try to connect using WinSCP I get "Network error: Connection refused".

I seriously suggest you to read and implement the following for your SSH access as the method there is much safer: http://wiki.contribs.org/SSH_Public-Private_Keys

[CharlieBrady]

I seriously suggest you to read and implement the following for your SSH access as the method there is much safer: http://wiki.contribs.org/SSH_Public-Private_Keys

While that is very good advice, it won't solve a "connection refused" problem.

peterhocking, make sure that you check messages, ssh and secure logfiles.

[cactus]

While that is very good advice, it won't solve a "connection refused" problem.

peterhocking, make sure that you check messages, ssh and secure logfiles.

I know, should have stated that. Thanks for pointing this out.

[qvindesland]

I notice that you say in the beginning "set the port that I want to use" did you change the port on ssh to other then 22?

[MSmith]

Set SSH back to local networks only, then use VPN to connect to the machine & use WinSCP to internal IP address.

[CharlieBrady]

Set SSH back to local networks only, then use VPN to connect to the machine & use WinSCP to internal IP address.

I wouldn't recommend that. SSH access using public/private keys is much more secure than PPTP. SSH using passwords on a non-standard port is also more secure.

[peterhocking]

Thanks everyone for your responses.

Turns out the issue was that I had FTP access allowed. Turning that off fixed. I had the same problem 2 & a half years ago when I build my last server.

Yes, I do use a non standard port for SSH for security reasons & thanks for the reminder to use Public & Private keys

Thanks again,

Peter

[CharlieBrady]

Turns out the issue was that I had FTP access allowed.

IIUC, the real issue was that you were configuring WinSCP to use the FTP protocol.