sftp does not connect

tpjets62 · 02-14-2004, 01:10 PM

I have fedora core 1 loaded and ssh is running. When I try to connect with sftp #22 with cute pro 1, it gets as far as:
STATUS:> Getting listing ""...
STATUS:> Initializing SFTP2 module...
STATUS:> Connecting to sftp server 192.168.9.4:22 (ip = 192.168.9.4)...
ERROR:> A timeout occurred.
ERROR:> Can't connect to 192.168.9.4:22. Socket error = #-1.
I can connect thru ftp thru #21, no problems. Thoughts? Tom

spuzzzzzzz · 02-14-2004, 10:34 PM

Probably because the ftp server is only running on port 21. So when you try to connect to 22, it times out. If you really want to connect to 22, you will need to change the configuration of the server.

tpjets62 · 02-16-2004, 07:56 PM

Where would I change this config at? I never had this problem with RH 73, 8, 9, must be another "security move" Any info would be great. TKS, Tom

spuzzzzzzz · 02-16-2004, 11:11 PM

That depends what the server is. The only one I know well is proftp. In proftp, all the configuration options are in /etc/proftpd/proftpd.conf. I don't know what the default ftp server daemon is in Fedora, but there might be a graphical configuration utility. But apart from that, is there any reason you need port 22? 21 is the default and I wouldn't know of any reason to change it.

homey · 02-17-2004, 12:30 AM

tpjets62,

Don't be too quick to make those changes. SFTP is really more along the lines of scp and slogin which use ssh. That's why it needs port 22 not 21.
Could be getting blocked at the firewall.
Try the command: slogin 192.168.9.4:22 or what ever the remote machine is.

spuzzzzzzz · 02-17-2004, 12:38 AM

Oh of course - I forgot you were using sftp instead of ftp. 22 is the way to go. Sorry.

tpjets62 · 02-17-2004, 10:09 AM

Quote:

Originally posted by spuzzzzzzz
Oh of course - I forgot you were using sftp instead of ftp. 22 is the way to go. Sorry.

No problem. I try to stay away from defaults and I prefer to use "S" for a little more security. I am by no means a security nut, but i like to look over my shoulder.

tpjets62 · 02-17-2004, 10:14 AM

Quote:

Originally posted by homey
tpjets62,

Don't be too quick to make those changes. SFTP is really more along the lines of scp and slogin which use ssh. That's why it needs port 22 not 21.
Could be getting blocked at the firewall.
Try the command: slogin 192.168.9.4:22 or what ever the remote machine is.

I get the response "this port has been closed for security reasons". When I do "nmap localhost, it is open, and I can get in thru ssh fine. There must be a config file some where that blocks sftp on this port. I disabled the firewall also.

tpjets62 · 02-17-2004, 10:24 AM

Now if I try@ a terminal sftp 192.168.9.4:22, its ask for my password, then says "Couldn't stat remote file: No such file or directory File "/root/22" not found. If I try to log on as a user, I get the same response except it cannot find the file /home/user/22. Wierd??? HHMMM!

tpjets62 · 02-17-2004, 10:45 AM

Well for kicks, I tried to get in using cute ftp pro 3.3, and I get right in. Everything works as advertised. My version, cute ftp pro 1, must be missing something that Fedora needs. This is the first version of Linux it would not connect to. I also use slackware and have had no problems there either. Oh well time to update. This 3.3 runs much faster than ! did. Hey, thanks to both of you for the replies and help. Who woulda guessed?