No connection with ssh over nautilus

[Kristian Kißling]

Have 2 computers connected by cable. Try to reach the other via Nautilus and SSH,
it fails with a timeout. Using SSH on bash works, using Konqueror and Fish works too.
This is where it hangs:

debug2: key: /home/zap/.ssh/identity ((nil))
debug2: key: /home/zap/.ssh/id_rsa ((nil))
debug2: key: /home/zap/.ssh/id_dsa ((nil))

Connection is indeed a bit slow. Can I change the timeout for SSH
connections in Nautilus?

br
Kris

[Saivann Carignan (oxmosys)]

Thanks for your bug report.

I'm not a expert with ssh but the debug outputs seems to demonstrate that nautilus didn't have necessary files for authentication with the server.

Since SSH is a encrypted communication protocol that can be used for a lot of purpose, can you be more specific about the configuration of the server? Did you use sshfs to share files through SSH?

Unless someone that have more knowledge than me on this point, I would suggest you to ask a question in https://answers.launchpad.net/ to see if you get clues or answers that could help finding more informations about that bug/problem.

[Kristian Kißling (kkissling)]

Saïvann Carignan schrieb folgendes am 12.12.2007 07:30:
> Thanks for your bug report.
>
>
Hi,
> I'm not a expert with ssh but the debug outputs seems to demonstrate
> that nautilus didn't have necessary files for authentication with the
> server.
>
It has. It's a local network, 2 computers directly connected via cable,
no Router between.
As I wrote, it works when I use SSH and SCP on Bash like "ssh
user@192.168.1.10" and with Konquerors "fish".
I guess, it just takes Nautilus to long to verify the passphrase, so it
gives me an error.
> Since SSH is a encrypted communication protocol that can be used for a
> lot of purpose, can you be more specific about the configuration of the
> server? Did you use sshfs to share files through SSH?
>
No SSHFS. Just openssh-server and openssh-client.
> Unless someone that have more knowledge than me on this point, I would
> suggest you to ask a question in https://answers.launchpad.net/ to see
> if you get clues or answers that could help finding more informations
> about that bug/problem.
>
I appreciate your help, but I know how to connect via SSH with Nautilus.
It worked before.
I don't think people there can help me with that issue. But I can post
more infos later.

br
Kris

--
Kristian Kißling, Redakteur
Linux New Media AG, Süskindstr. 4, 81929 München, Germany
<email address hidden> - http://www.linuxnewmedia.de

Linux New Media - The Pulse of Open Source
Malaga - Manchester - München - Sao Paulo - Timisoara - Warszawa

---------------------------------------------------
Sitz der Gesellschaft: Süskindstraße 4, 81929 München
Amtsgericht München: HRB 129161
Vorstand: Rosemarie Schuster, Hermann Plank
Aufsichtsratsvorsitzender: Rudolf Strobl

[Sebastien Bacher (seb128)]

Does gnomevfs-ls work correctly there?

[Kristian Kißling (kkissling)]

Ping:
=====

PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_seq=1 ttl=64 time=3.15 ms
64 bytes from 192.168.1.10: icmp_seq=2 ttl=64 time=1.00 ms
64 bytes from 192.168.1.10: icmp_seq=3 ttl=64 time=1.45 ms
64 bytes from 192.168.1.10: icmp_seq=4 ttl=64 time=0.915 ms
64 bytes from 192.168.1.10: icmp_seq=5 ttl=64 time=5.39 ms
64 bytes from 192.168.1.10: icmp_seq=6 ttl=64 time=0.793 ms
64 bytes from 192.168.1.10: icmp_seq=7 ttl=64 time=35.2 ms
64 bytes from 192.168.1.10: icmp_seq=8 ttl=64 time=0.615 ms
64 bytes from 192.168.1.10: icmp_seq=9 ttl=64 time=1.03 ms
64 bytes from 192.168.1.10: icmp_seq=10 ttl=64 time=1.45 ms
64 bytes from 192.168.1.10: icmp_seq=11 ttl=64 time=0.895 ms

--- 192.168.1.10 ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10001ms
rtt min/avg/max/mdev = 0.615/4.721/35.227/9.740 ms

Error Message is:
=================

Nautilus kann »ssh://zap@192.168.1.10« nicht anzeigen.
Bitte wählen Sie eine andere Ansicht und versuchen Sie es noch einmal.

Nautilus is not able to show »ssh://zap@192.168.1.10«. Please chose
another view and try again.

GNOMEVFS-LS:
===========

gnomevfs-ls -v ssh://zap@192.168.1.10
Error opening: Datei nicht gefunden (File not found)
Error opening: Zeitüberschreitung (Timeout)

Strace:
=======
Attached

[Sebastien Bacher (seb128)]

The issue happens also when using gnomevfs-ls, reassigning, that's not a nautilus specific issue. What sort of ssh server are you using?

[Kristian Kißling (kkissling)]

sshd -v
OpenSSH_4.6p1 Debian-5build1, OpenSSL 0.9.8e 23 Feb 2007

[Sebastien Bacher (seb128)]

the bug deprecated now than nautilus uses gvfs, open a new bug against gvfs if you still get the issue in hardy or intrepid