Mounting SSH folders through nautilus

[zhark1]

Hello.

Since I've upgraded from Gutsy to Hardy I can no longer mount remote SSH folders through the built-in support in nautilus. Even sftp://serverort immediately gives the same connection denied error.

Anyone know how to fix this?

[_Narcisse_]

Hi zhark,

Did you try with Menu -> Places -> Connect to server, then choose SSH in server type, and check add bookmark to have it ready in "Places" next time...

[clint1010]

Hi, I am trying the same thing as zhark1 with no success

I can ssh to my server via a terminal no problem, but when I try Places=>connect to server, it creates a desktop link and puts the entry in the places menu, but I can't connect/browse this location with nautilus. Also, when I go through the "connect to server" method, it does not ask for a password? but it does when I use a terminal?

I must be missing something, please help

[arddwyn]

Has anyone found an answer to this question?
I used to have no problem connecting to the ssh server we keep in the house for our backups under Gutsy with Nautilus. I tried the "connect to server" option with the bookmark, but when it connects me i can see the folders in the server with my files, but if I try to open a folder or a file gnome-panel freezes. If I try to access my ssh server through the created bookmark it says it can not connect to location "sftp://... etc".
Is there any way to revert the ssh functionality to the previous version on Gutsy or to fix this?
Any help will be greatly appreciated.

[jtrindle]

Clint1010: Can you unmount the link on the desktop (right click, unmount) and try to reconnect?

Did you say you wanted the password remembered forever? If so, it might be in the keyring

Applications->Accessories->Passwords and Encryption Keys->Passwords

and delete the key corresponding to the user:server.

Then try and reconnect your normal way.

arddwyn: Possibly try deleting the bookmark and recreating it?

[arddwyn]

I recreated the bookmark and deleted the password on the keyring to start fresh. I was able to connect from the newly created bookmark but still when I access the ssh folders even though I can see my folders I can't do anything. Just now looking at it with only firefox and the nautilus window open, my CPU was at 94% and it took 30 seconds between clicking on the main menu and when my options showed up. I tried opening another window with the files I wanted to copy to the server and Nautilus shut down. I am running Gutsy server edition on the other computer and never had a problem before the Hardy upgrade

[jtrindle]

what's the output of:

top -n 1

? I'm curious about the first four lines. Doesn't matter if you're trying to open a Samba share at the time or not.

[sideshownick]

After fresh install of Hardy (8.04) "connect to server" no longer works for ftp. Same if I simply type ftp://ftp.servername.com in nautilus' address bar. I get the error:

Couldn't display "ftp://ftp.servername.com/"
Error: Invalid reply
Please select another viewer and try again.

Have never had this problem before, and the server(s) still accessible by other means. This is a piece of basic functionality I expect to just work... anyone know what's going on?

[Coombabah]

I've been having the same problem but only with some servers (Solaris).
I installed kubuntu-desktop via Synaptic and selected KDE instead of gdm for my session.
My tests found that nautilus (under Gnome) has problems with some servers (Solaris) but dolphin (under KDE) doesn't.
I love the way you can have Gnome and KDE and just pick which one you want for the session at the login screen.
There may be simpler workarounds but switching to KDE is one way of getting sftp to work from the file manager again.

Edit: I just found out you can run KDE and Gnome simultaneously switching between Gnome and KDE using ctrl+alt+( F7 or F8 ) if you have plenty of RAM.
Also noticed you can just run Dolphin under Gnome

[zhark1]

I just found out something, I've specified Port = 2002 in /etc/ssh/ssh_config, to make it easier to connect (w/console) to my own computers, which I'm running on that port. When connecting to my own computers, with ssh running on that port, it doesn't matter if I fill inn port in the connect dialog in gnome, but when I try to connect to others servers running on the standard port (22) it immediatly shows up with an error message. It seems the gnome client simply ignores the specified port, and connects to the default port in /etc/ssh/ssh_config.

BTW: I checked the gnome keyring beforehand, and it had no entries what so ever.