From freenx-knx Wed Jan 23 09:07:41 2008 From: Phuoc Trung Nguyen Date: Wed, 23 Jan 2008 09:07:41 +0000 To: freenx-knx Subject: Re: [FreeNX-kNX] Black Screen after Establishing the NX-Session - Message-Id: <479703DD.10307 () maas ! de> X-MARC-Message: https://marc.info/?l=freenx-knx&m=120107963106878 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0030390501==" This is a multi-part message in MIME format. --===============0030390501== Content-Type: multipart/alternative; boundary="------------020000040904040404080008" This is a multi-part message in MIME format. --------------020000040904040404080008 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Joe Baker schrieb: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Phuoc Trung Nguyen wrote: > >> Holger Krull schrieb: >> >>> Phuoc Trung Nguyen schrieb: >>> >>> >>>> I use the windows NXClient v 3.1.0.3 from NOMACHINE to connect to the >>>> freeNX server using the option Desktop->Unix->Gnome. It works fine !!! >>>> >>>> Now I try to connect to a linux machine which runs X-server too, via >>>> freeNX server. Therefore I need to set the NXClient as below : >>>> >>>> *Desktop->Unix->XDM ->Settings->Login->Query an X desktop manager->host >>>> 192.168.1.227, port 177* >>>> >>>> Scenario: >>>> *Windows NXClient -> freeNX server 0.7.1 -> linux server (x-server)* >>>> >>>> The test using NXSERVER version 2.1.0-22 -LTE from Debian runs fine, >>>> which was installed with apt-get. I can connect to 192.168.1.227. >>>> >>>> What did I do wrong here ? >>>> Do I forget something ? >>>> >>>> >>>> >>> As far as i know, freenx doesn't support choosing via XDMCP. >>> Would be cool, but just not implemented. >>> >>> ________________________________________________________________ >>> >>> >> Hi >> thanks for quick answer. I assume freeNX v 0.7.1 does not support XDMCP. >> It would be great if it supports it in the next version. >> Anyway I will save my time instead looking for answer. >> > > There is a Display Manager used in Edubuntu that might fit the bill. It > might have you loose all your speedup benefits, but maybe not. > It's called LDM for LTSP Display Manager. > It's sort of like XDMCP over SSH. > > - -- > Joe Baker > "I want my country back!" > Vote Ron Paul for President > http://www.ronpaul2008.com > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHlmgs7J1dPd3sAmARAmCMAJ93OtDZFLXNQ28UeTjmzR8CkZZVtgCgpetD > 7BRTBmKmm1mL7+CHO39nFsU= > =c4l+ > -----END PGP SIGNATURE----- > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/ > > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@kde.org > https://mail.kde.org/mailman/listinfo/freenx-knx > ________________________________________________________________ > if I set the option AGENT_EXTRA_OPTIONS_X="-query 192.168.1.227" in the file node.conf, it will work, because the nxserver send the login request to XDMCP service of target system. In this case I can only access to one system. My intention is the access to many X-systems (aix; solaris, linux ..) I am missing options in node.conf as below : ENABLE_INDIRECT_XDM_QUERY, ENABLE_DIRECT_XDM_QUERY, ENABLE_BROADCAST_XDM_QUERY It seems they are not implemented :-( Regards Phuoc Trung Nguyen --------------020000040904040404080008 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Joe Baker schrieb: 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Phuoc Trung Nguyen wrote:
  
Holger Krull schrieb:
    
Phuoc Trung Nguyen schrieb:
  
      
I use the  windows NXClient v 3.1.0.3 from NOMACHINE to connect to the 
freeNX server using the option Desktop->Unix->Gnome. It works fine !!!

Now  I try to connect to a linux machine which runs X-server too, via 
freeNX server. Therefore I need to set the NXClient as below :

*Desktop->Unix->XDM ->Settings->Login->Query an X desktop manager->host 
192.168.1.227, port 177*

Scenario:
*Windows NXClient -> freeNX server 0.7.1 -> linux server (x-server)*

The test using NXSERVER version 2.1.0-22 -LTE  from Debian  runs fine, 
which was installed with apt-get. I can connect to 192.168.1.227.

What did I do wrong here ?
Do I forget something ?

    
        
As far as i know, freenx doesn't support choosing via XDMCP.
Would be cool, but just not implemented.

________________________________________________________________
  
      
Hi
thanks for quick answer. I assume freeNX v 0.7.1 does not support XDMCP.
It would be great if it supports it in the next version.
Anyway I will save my time instead looking for answer.
    

There is a Display Manager used in Edubuntu that might fit the bill.  It
might have you loose all your speedup benefits, but maybe not.
It's called LDM  for LTSP Display Manager.
It's sort of like XDMCP over SSH.

- --
Joe Baker
"I want my country back!"
Vote Ron Paul for President
http://www.ronpaul2008.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHlmgs7J1dPd3sAmARAmCMAJ93OtDZFLXNQ28UeTjmzR8CkZZVtgCgpetD
7BRTBmKmm1mL7+CHO39nFsU=
=c4l+
-----END PGP SIGNATURE-----
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
if I set the option AGENT_EXTRA_OPTIONS_X="-query 192.168.1.227" in the file node.conf, it will work,
because the nxserver send the login request to XDMCP service of target system. In this case I can only access to one system.
My intention is the access to many X-systems (aix; solaris, linux ..)

I am missing options in node.conf  as below :

ENABLE_INDIRECT_XDM_QUERY, ENABLE_DIRECT_XDM_QUERY, ENABLE_BROADCAST_XDM_QUERY

It seems they are not implemented :-(

Regards
Phuoc Trung Nguyen
--------------020000040904040404080008-- --===============0030390501== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ________________________________________________________________ Were you helped on this list with your FreeNX problem? Then please write up the solution in the FreeNX Wiki/FAQ: http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ Don't forget to check the NX Knowledge Base: http://www.nomachine.com/kb/ ________________________________________________________________ FreeNX-kNX mailing list --- FreeNX-kNX@kde.org https://mail.kde.org/mailman/listinfo/freenx-knx ________________________________________________________________ --===============0030390501==--