Your best friend for file transfer.Fetch
DNS resolution by FTP but not SFTP (4 posts)
- Started 1 year ago by Greg
- Latest reply 1 year ago from Greg
I have a server setup using Win2k8 Server, originally as plain FTP served up by IIS7, then added SFTP/SSH server through 3rd party app. The server has a static IP as well as a subdomain. One of my users is having an odd issue. Using Fetch, he can access the server via subdomain address using FTP, but not SFTP. However, if the user enters the static IP instead of the subdomain address in Fetch, SFTP connects properly.
I know DNS resolution is fine for the server since I have tested it using many other clients on Windows and mobile devices, and all successfully access the SFTP server via subdomain. Does anyone has any ideas what might cause this (either client or server side)?
As an addendum, a snippet from the transcript showing an initial login attempt through SFTP trying to access using the subdomain (xxx.xxx.edu), followed by the start of a successful SFTP connection using the direct IP:
"Connecting to UserName@xxx.xxx.edu port 22 (9/13/11 9:39:53 AM)
Connecting to UserName@xx.xxx.x.xxx port 22 (9/13/11 9:40:12 AM)
SSH2_FXP_REALPATH 1, ."
The actual error window following the aborted SSH2 INIT command:
"SFTP connection to xxx.xxx.edu could not be opened because the connection to the SFTP server could not established or was lost."
Jim Matthews Administrator
Can you connect to the subdomain using the "sftp" command in Terminal? You might try running Terminal (it's found in the Utilities folder inside the Applications folder) and typing:
sftp -v UserName@xxx.xxx.edu
What do you see then?
I will try this. Another curious tidbit: people using Filezilla on Mac can use SFTP and the subdomain address.
- Page 1