vino-preferences says that your system is reachable using 'localhost'

[Paul Larson]

Binary package hint: vino

When setting up vino to allow remote connections, it tells the user:
"Your desktop is only reachable over the local network. Others can access your computer using the address localhost"

Funny, but not helpful for actually connecting to the REMOTE machine :)

ProblemType: Bug
Architecture: amd64
Date: Fri Sep 4 18:50:40 2009
DistroRelease: Ubuntu 9.10
Package: vino 2.27.91-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SourcePackage: vino
Uname: Linux 2.6.31-9-generic x86_64

[Sebastien Bacher (seb128)]

Thank you for your bug report, that's an upstream issue and should be sent to GNOME

[Sebastien Bacher (seb128)]

https://bugzilla.gnome.org/show_bug.cgi?id=167690 indicates that should be fixed and in karmic it displays correctly the ip to use there and the boxname.local for local discovery

[®om (rom1v)]

It still happens in Maverick beta : there is no way to use remote desktop remotely.

I have this configuration on the server :
http://pix.toile-libre.org/upload/original/1286170680.png

I create a ssh tunnel from the client :
ssh -CNL 5900:localhost:5900 login@server

And try to connect to localhost:5900 : it does not work.

[joopbraak (joopbraak)]

Open gconf-editor, go to "/desktop/gnome/remote_access" and make sure the value network_interface is empty.

Also make sure "Remote Desktop" (command line "/usr/lib/vino/vino-server --sm-disable") is enabled in your Preferences, Startup Applications.

But I agree, this should work out of the box and vino-preferences should have an option to change that and the listening port without having to use gconf-editor.

[joopbraak (joopbraak)]

Make sure to have a good password or (better) use ssh tunneling because vino is not secure.

[Arie Skliarouk (skliarie)]

Same problem on natty (11.04).
Could be this is because the machine's IP number sits on "br0" interface, but IMHO it is still bug.

If I set the interface to br0 using the trick in comment #5, the IP is detected correctly.