After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 500620 - Only allow local connectins feature doesn't work
Only allow local connectins feature doesn't work
Status: RESOLVED OBSOLETE
Product: vino
Classification: Applications
Component: Server
2.21.x
Other All
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-11-30 09:25 UTC by conny
Modified: 2009-09-01 19:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description conny 2007-11-30 09:25:20 UTC
Please describe the problem:
When the checkbox of Only allow local connectins is checked, local connection can not be accepted. 

Steps to reproduce:
1. Launch Remote Desktop Preferences
2. Ckeck Allow other users to view your desktop
3. Check Only allow local connectins in the Advanced tab
4. Try to connect with a local user*

*Local user is a normal user on the local machine, and a ssh tunelling connected user. 

Actual results:
Get message connection is refused 

Expected results:
Connection is accepted 

Does this happen every time?
yes

Other information:
Comment 1 Jonh Wendell 2007-11-30 12:28:35 UTC
Hi.

I think you're using the valid ethernet device to connect to server, not the loopback one (127.0.0.1).

Try to use vinagre (or vncviewer, or any vnc client) pointing to 127.0.0.1 (localhost) address, in the same machine that vino is running. Tell us if you get success.
Comment 2 conny 2007-12-03 10:16:56 UTC
When I delete the folder ~/.vnc and re-test, the connection successful, by vncviwer localhost:0. I am using the vncviewer on Solaris. 

But I am still not sure  about the ssh tunneling case. I tried to connect the server via ssh, with ssh -X username@vncserver, then connect with the vncserver by vncviewer hostname:0. the connection successful too. Do you think this is correct? IMO, the connection should work only the port forward setting up. 
Comment 3 Frederik Elwert 2008-07-29 15:17:51 UTC
I can confirm this. Deleting ~/.vnc didn't help for me.

I simply activated vino as described above, and then tried "vncviewer localhost". With only local connections allowed, I don't get a connection ("connection refused"). When I disable that option, it works.
Comment 4 ggjj11 2008-07-29 15:50:36 UTC
Hello,

I have the same problem. I use Ubuntu 8.04 and the bug is still not corrected! See here ( http://forum.ubuntuusers.de/topic/vnc-server-nicht-durch-ssh-tunnel-erreichbar/#post-1527732 ) to notice that I´m not the only one who complains about this bug.

I really appreciate your work go on to develop gnome and fix this bug :)
Comment 5 Jorge Pereira 2008-10-21 18:19:03 UTC
Hello,

1) in any part of the "vino source" uses something of ~/.vnc

2.1) i try connect from windows host using putty+ssh forward for connect in linux+vino(localOnly) and sucessful!

2.2) i try connect from linux host using ssh forward for connect in linux+vino(localOnly) and sucessful!

3) Completion, maybe you has same problem in your configuration!
Comment 6 Jonh Wendell 2008-10-21 18:34:00 UTC
Okay, I have tested and it works fine.

Maybe you have some issue with other vnc server, once vino doesn't use ~/.vnc.

ggjj11, I don't understand german.. or whatever it is :)

I'm closing this one as it seems to be a mistake. Feel free to reopen it if you don't think so.
Comment 7 Frederik Elwert 2008-10-21 20:34:26 UTC
I don't get it. How did you solve this? I deleted ~/.vnc, but I don't think this has anything to do with it. On my Ubuntu Hardy machine, I still have the same issue.
Comment 8 Jonh Wendell 2008-10-22 13:21:46 UTC
OK, so, please, do the steps:

1) Disable vino in the applet;
2) go to a terminal
3) type: killall vino-server
4) run /usr/lib/vino/vino-server (or /usr/libexec/vino-server depending on your distro)
5) start the applet, and enable the option 'local only'
6) wait a few seconds and disable that option
7) paste here your terminal output
Comment 9 Frederik Elwert 2008-10-22 19:56:43 UTC
I get this output:

22/10/2008 21:54:16 Autoprobing TCP port 
22/10/2008 21:54:16 Autoprobing selected port 5900
22/10/2008 21:54:16 Advertising security type: 'TLS' (18)
22/10/2008 21:54:16 Advertising authentication type: 'No Authentication' (1)
22/10/2008 21:54:16 Advertising security type: 'No Authentication' (1)
22/10/2008 21:54:36 Re-binding socket to listen for local VNC connections on TCP port 5900
22/10/2008 21:54:50 Re-binding socket to listen for all VNC connections on TCP port 5900

Comment 10 Jonh Wendell 2008-10-22 20:17:39 UTC
The code looks right to me, and it works fine here. So, please, add me on jabber so that we can investigate this issue deeper. My jabber id is jonh.wendell - gmail.com
Comment 11 Jonh Wendell 2008-12-12 20:25:30 UTC
Please, try vino trunk or wait until vino 2.25.x is released.

As discussed in bug 403183, local_only preference is now obsolete. Now you are able to select a network interface which vino must listen to.
Comment 12 komputes 2009-09-01 03:30:37 UTC
Hi John,

In response to your last post from December 2008. I still cannot see the option where I am able to select a network interface which vino must listen to.

I am using vino 2.27.91-0ubuntu1. The downstream bug can be found here:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/275340
Comment 13 komputes 2009-09-01 19:21:17 UTC
I had a short jabber talk with Jonh (sorry for misspelling your name, force of habit). And it seems the option to select interface is available in the back end but not directly in vino-preferences.

To set up localhost only, you have to open up gconf-editor and modify the following string value to be "lo" (without the quotes):

/desktop/gnome/remote_access/network_interface