Hi guys, I am not sure if I have posted this in the right forum, apologies if I haven't.
I have recently installed a Ubuntu 9.04 Jaunty server and very much enjoy this side of the computing world.

I simply wanted to be able to access this server from the internet. I installed TightVNC on a remote windows machine and turned on the remote desktop preferences on my Ubuntu server. All worked fine and I could access my server. But I needed to be able to transfer files. TightVNC has this ability but seemed to require a server version of TightVNC on the host computer, so consequently, I installed it on my Ubuntu machine.
However, now, I keep getting an error.

I log onto the address of my server from the internet and all is fine so far, it asks me for the password, which I type in. It recognises the password, but then has problems and instantly kicks me, displaying the message 'Connection Closed'

I have a log of what is going on and if I posted it here, just wondered if anyone could shed some light as to what is going on as I can't make head nor tail of it. Any response would be greatly appreciated

log:
vncSockConnect.cpp: accepted connection from 86.137.127.198
vncClient.cpp: vncClient() executing...
vncClient.cpp: client connected : 86.137.127.198 (id 20)
vncServer.cpp: AddClient() done
vncClient.cpp: negotiated protocol version, RFB 3.8
vncClient.cpp: enabling TightVNC protocol extensions
vncClient.cpp: performing VNC authentication
i:\tightvnc-1.3.10-setup\vnc_winsrc\winvnc\vncPasswd.h: PASSWD : ToText called
i:\tightvnc-1.3.10-setup\vnc_winsrc\winvnc\vncPasswd.h: PASSWD : ToText called
Wed Jun 24 15:31:53 2009
vncMenu.cpp: tray icon updated ok
WallpaperUtils.cpp: KillActiveDesktop
WallpaperUtils.cpp: unable to access Active Desktop object:80040154
vncDesktop.cpp: initialising desktop server
vncDesktop.cpp: KillScreenSaver...
vncDesktop.cpp: SCR-WBB: current display: w=1024 h=768 bpp=32 vRfrsh=60.
vncService.cpp: unable to open desktop, error=120
vncService.cpp: SelectHDESK() to Default (3 from 38
vncService.cpp: SelectHDESK failed to close old desktop 38, error=170
vncServer.cpp: failed to initialize desktop object
VSocket.cpp: closing socket
vncDesktop.cpp: killing desktop server
vncServer.cpp: Authenticated() done
vncServer.cpp: RemoveClient() done
vncClient.cpp: ~vncClient() executing...
vncClient.cpp: deleting socket
vncMenu.cpp: tray icon updated ok
vncMenu.cpp: tray icon updated ok
WallpaperUtils.cpp: unable to access Active Desktop object:80040154
Jay100 is online now Report Post Edit/Delete Message

if you're doing this over the net, then please please please stop using vnc. use nx instead, which will give you proper user authentication and connection security over ssh. And a much much nicer user experience too. VNC is so weak is so many ways you're bound to be compromised sooner or later.

nx ? WTF is that ?
Oh! Here: http://www.nomachine.com/select-pack...?os=linux&id=1
It looks very interesting. Thanks for that one

OK thanx acid, for that advice. I have had a look at the link provided by tredegar but not sure what the limitations of the free edition are exactly. Also I need to be able to access my Ubuntu server from a windows pc over the net. Any advice on software and/or links to setup instructions would be greatly appreciated in order for me to accomplish this

It looks like nx doesn't care.

See here: http://www.nomachine.com/documents.php

and here: http://netx.sourceforge.net/

All the docs you need are in the three links I have given you.

OK thanx for the info links, tredegar... I shall delve into this NX stuff and see what happens when I come out the other side. Shall post my success or failure after:P

We look forward to hearing about your progress.
... And welcome to LQ!

the free edition is that it is only useful for system administration, not user applications, in that it only allows two connections at once, which, if you were aware, is how Windows remote desktop compares to terminal services. 2 connections vs loads.

Most people who mention nx will also mention freenx as an alternative nx server without limitations, but AFAIK freenx was initiated before an official free version of the real nx server was available and it's not nearly as user friendly. So if you only want personal access, freenx provides nothign interesting at all.

OK, I am at a point of joy but also of near crying! I have the nxserver installed and the client installed on the remote windows computer.
I have a user configured and can log in with user details on the windows machine. All is well and it seems great.
However the one big problem that I can't seem to find any info on, is just how do I actually transfer files across from my windows machine to my ubuntu using this nxserver? or upload for that matter?
Any help really will be hugely appreciated as I am at a complete loss
regards
James

I can't remember exactly where it's done, but in the normal windows nx client there's an option to share drives one way or another.

on the main login screen, hit configure, then on the linux client there's a services tab which I assume is there on windows too.

note that nx uses ssh for all it's doings, so you could easily just use an ssh file transfer program like winscp to bypass the need to do it all laahh dee dah in the nx client.

Thanks for the quick reply. Yes I have had a look at the services tab and I click to 'enable SMB printer and file sharing' and then an error message telling me the SMB server is not running
I use bitvise tunnelier and I have just edited this post as I have seen that I can indeed use this across the internet. It means that as good as this nx server appears to be, there seems to be so much hassle trying to get file transfers up and running (at least to someone like me who is only half tech savvy, if that, with this stuff) I may just have to forget nxserver for now, or maybe look into this samba stuff. It does look like a real task so at the moment I think I will have to look into acheiving what I want from tunnelier, now that I have discovered its internet capabilties. Thanks for your eye opening information. I will keep an eye on this thread in case there is any more light to be shed on the issues raised.
Kind regards
James

I think on the windows client it just means that you have no windows shares created to take across with you.