I have been unable to connect to my FTP server behind Wingate when using SFTP. There is no problem connecting when using regular FTP.
I have been using Microsoft IIS FTP for well over a year since installing Wingate. The FTP client is CuteFTP Pro. Wingate FTP Proxy is setup to pipe the request directly through to the LAN server machine's IP. ENS Port Security shows a Hole for the appropriate port and the packet is Allowed.
I just recently installed Globalscape's Secure FTP Server 2. IIS is stopped and IIS port pooling is disabled. With regular FTP there is no problem connecting to the new server either from the LAN or from a remote location. When I switch to SFTP the connection fails. (In Wingate, FTP Proxy is set to Port 22 and ENS Port security also reflects Port 22.) The SFTP server is setup for password only. Following is the error message:
STATUS:> Initializing SFTP21 module...
STATUS:> Connecting to SFTP server 69.xxx.xxx.xxx:22 (ip = 69.xxx.xxx.xxx)...
ERROR:> The file being transferred in ASCII mode appears to be a Binary file. Proceed anyway?
ERROR:> Can't connect to 69.xxx.xxx.xxx:22. SFTP21 error = #0.
STATUS:> SFTP21 connection closed
Yesterday, Globalscape support asked me to check if I could connect directly to the server using the server's LAN IP. It worked just fine. Which leads me to believe that Wingate is interferring in SFTP mode.
Additionally, I have no problem connecting from the LAN to our third party web site host's SFTP server.
Anyone have any suggestions?
Thanks for your help!