Hi,
I just checked and apparently it is fixed for me.
On Tue, Jun 24, 2008 at 23:53, Sebastien Bacher [EMAIL PROTECTED] wrote:
could anybody try if that's still an issue in hardy? nautilus is using
gvfs not and the bug might be fixed there
** Changed in: nautilus (Ubuntu)
Status: New
thank you for the update, closing the bug
** Changed in: nautilus (Ubuntu)
Status: Incomplete = Fix Released
** Changed in: nautilus
Status: Incomplete = Fix Released
--
Access to remote SSH server does not distinguish the connection by port
https://bugs.launchpad.net/bugs/59882
could anybody try if that's still an issue in hardy? nautilus is using
gvfs not and the bug might be fixed there
** Changed in: nautilus (Ubuntu)
Status: New = Incomplete
** Changed in: nautilus
Status: New = Incomplete
--
Access to remote SSH server does not distinguish the
On one machine which has been upgraded from 6.06 through to 7.10 the
multiport connection was working ok until a few weeks ago when I
suddenly found I was getting through to the same server whichever port
connection was used. So that suggests to me that there has been some
change in the
On one machine which has been upgraded from 6.06 through to 7.10 the
multiport connection was working ok until a few weeks ago when I
suddenly found I was getting through to the same server whichever port
connection was used. So that suggests to me that there has been some
change in the
I am using 6.10 Nautilus version 2.16.1
I have several servers behind a firewall to which I connect with SSH with
private keys. ie. ssh://[EMAIL PROTECTED]:2201, ssh://[EMAIL PROTECTED]:2201
etc.
This works ok for command line ssh/scp/sftp
Using the Places:Connect to server menu I can create
Thank you for your bug. That looks really a corner case, we don't have
enough people working on bugs to spend time on that for the moment and
it should probably be forwarded upstream, opening an upstream task
** Also affects: nautilus (upstream)
Importance: Undecided
Status: Unconfirmed
Hello,
I tried testing that here, and I also had problems. I think the problem
is with remote host identification.
ie, if you try to connect to the servers using ssh from the command
line, like ssh -p 2201 192.168.2.1 and ssh -p 2202 192.168.2.1, one
command will work, the other will fail with
