From: Arfin G. <Arf...@no...> - 2011-01-13 20:44:12
|
Mel, There are a couple of things that matter here. 1) The default port for VNC is 5900 (the 5800 port is the browser/Java client port). 2) Ubuntu -- at least up to 8.x -- running KDE or pretty much anything else, would not accept connections on the default port, as that would require sharing display 0 (zero). The standard virtual display port number range for most Linux/Unix applications would start at 5901 (display #1). You would have to configure the VNC server to listen on one of those ports, and the connection would be established by (assuming 5901) addressing either MyServerAddress:1 or alternatively MyServerAddress::5901. (Notice that when using the "display number" notation, a single colon and the display number are used; when using the "port number" notation, a double colon and the full port number are used.) 3) Ubuntu 10.x with KDE now supports -- as a default -- sharing display 0 (zero), and their RFB (krfb) application assumes it. I had to change my desktop to Gnome, because the new KDE 4 assumes that, if you create virtual sessions, you want to clone whatever is running on display 0. Further, it would launch applications in display 0 space even when the launch was initiated from the virtual session. I have no idea what they were thinking when they made sharing display 0 the default. Hope this information is of some use. ~~ Garry ----- On 01/13/2011 11:26 AM, Mel Burslan wrote: ----- > > I may be asking the question in the wrong environment as tightVNC is a > product whereas I am trying to connect to the native (???) VNC server > on ubuntu but I though it might be a good starting point. > > my viewer and my ubuntu host are on the same home network. So, there > is no funny business with virtual server settings on my home router. > When I put the IP address of my ubuntu host (no port numbers) on the > VNC viewer start screen, it immediately comes back with error # 10061, > connection refused. This makes me believe ubuntu's VNC server is > running on a different port than the tightvnc's port 5800. > > Does anyone know what the problem here is ? > > Thanks > Mel > ------------------------------------------------------------------------ > > > |