Ubuntu Remote Desktop -> Connection Refused - Intrepid Ibex Alpha 2

[Philip Wyett]

Setting up the remote desktop on Intrepid Ibex Alpha 2 and attempting to
connect to the machine results in a connection refused.

[Connor Imes (ckimes)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" [WWW] http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at [WWW] http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[komputes (komputes)]

I have tested this many times ans I can confirm this issue.

Steps to reproduce:

On host/server computer
1) Install Ubuntu 8.10
2) System > Preferences > Remote desktop
3) Turn on remote desktop (with or without password/confirmation is not a factor)
--
On client computer
4) (Ubuntu 8.04) open a vnc client such as vinagre (Remote Desktop Viewer), Note: this has been tested with other like tsclient and krdc
5) Connect to the server
6) Get rejected -> "Connection Refused"

It seems that the VNC server is not running properly. I expect #6 to be show remote desktop. Please request specific files if needed to debug this issue.

[Fahim Abdun-Nur (fahim-a)]

My VNC client reports "Connection refused (10061)".

Furthermore, the vnc server doesn't seem to be running on port 5900 (or at all) when I did a netstat -l

Any ideas?

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in vino.

For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

[Fahim Abdun-Nur (fahim-a)]

Apparently, the server never got started?

Once logged in, had to manually start sudo /usr/lib/vino/vino-server to get the VNC server started and listening.

fahim@fahim-gx280:~$ nmap localhost

Starting Nmap 4.53 ( http://insecure.org ) at 2008-07-26 12:37 EDT
Interesting ports on localhost (127.0.0.1):
Not shown: 1708 closed ports
PORT STATE SERVICE
22/tcp open ssh
139/tcp open netbios-ssn
445/tcp open microsoft-ds
631/tcp open ipp
5900/tcp open vnc
8000/tcp open http-alt

So this could in fact be more a Gnome issue and not necessarily a fault in vino. If anybody's looking at this, let me know if you need any further logs etc. etc.

[Jonh Wendell (wendell)]

This is due to new gnome-session. I think we should have this fixed for 2.23.6.

[Sebastien Bacher (seb128)]

the bug has been fixed upstream now

[Fahim Abdun-Nur (fahim-a)]

Fix came in as part of the gnome 2.23.90 tarballs...got them August 19, 2008...verified that vino is indeed running :)