On Wed, 2010-02-24 at 23:45 -0700, Dimitris Anogiatis wrote:
<snip>
> John, > > > you're close but no cigar yet. > > > Let me attempt to explain again. > > > Assume that x2goserver is running on Debian Lenny with an IP of > 192.168.0.10 > Also assume that Virtualbox is running the XP virtual machine with an > IP of 192.168.0.109 > > > here's what i do in steps > > > 1) I turn on my laptop and boot into windows vista (IP 192.168.0.130) > 2) I load Remote Desktop Connection > 3) I type in the username & password, press enter and I can connect to > the Windows XP virtual machine (on 192.168.0.109). > 4) I then log off of Windows XP. > > > Now that I know that RDP works I'm trying to do the same with the x2go > client that I installed on Windows Vista. > > > 1) I load the x2goclient (for windows) on my laptop (192.168.0.130) > 2) I make a new session named Virtualbox XP > 3) Host: 192.168.0.109 > 4) Login: the same username I have on XP > 5) SSH Port: 3389 (this, I think is most likely the problem area cause > RDP doesn't use ssh) > 6) Session Type: Connect to Windows terminal server Server: > 192.168.0.109 (Not sure if this is correct but it's the same IP as the > host) > 7) I press OK set the password, press OK and I'm waiting for it to > connect > 8) An error message pops up "Connection Failed 192.168.0.109: > ssh_exchange_identification: read: Software caused connection abort" > > > and That's all. Same thing happens when I reboot the computer and > load xubuntu. > > > I can connect to the vm using Remotedesktop-Client (a gui of rdesktop) > but x2goclient-gtk on xubuntu reports the same error. > > > For other kinds of sessions i.e. Gnome, LXDE sessions (Not using KDE) > and single application sessions, x2goclient on both platforms works > like a charm. > > > Does anyone know what I'm doing wrong guys? or is it a bug that needs > squashing? > > > Thanks for all your help in advance > > > Regards > Dimitris Ah, now I see what you're doing but I'm not sure why you are doing it. Perhaps this is because I'm not familiar with using the terminal server session type. I think you are misusing it but my experience is not based upon X2Go server. I believe the terminal server option is not used for connecting the x2goclient to a terminal server. x2goclient does not "speak" RDP as far as I know, only NX. Instead, what it does is connect to the X2GoServer running on the Lenny server and then, instead of launching startkde or gnomesession, it starts rdesktop to connect to a terminal server. The important point is that the x2goclient is not connecting directly to the RDP server; it is connecting directly to the X2GoServer which then established an RDP connection to the Windows server. At least, that's how I think it works in NoMachine. I really don't know about X2Go. Sorry I can't be more authoritative - John
Thank you John,
What you described on your last reply worked just fine... I was going at it the wrong way. As you described everything happens on the x2goserver. I was under the impression that x2goclient talks directly to the RDP server.
Thank you very much
Regards, Dimitris
Hi, Dimitris. I'm glad it finally sorted. I've cc'd the list just in case someone else interprets the terminal server option the same way. Thanks for your patience working through it - John