[FreeNX-kNX] Mac client cannot connect to server (worked fine for 2 or 3 times)

Prakash Velayutham prakash.velayutham at cchmc.org
Fri Mar 28 22:08:29 UTC 2008


Hi Fabian,

I do not see anyone else in the list complaining about this. So I am  
thinking it has to be something I did incorrectly on the client-side.  
Just wanted to confirm if the same setup is working for others. Could  
you confirm if you have heard about this bug from any one else?

Thanks,
Prakash


On Mar 28, 2008, at 5:51 PM, Fabian Franz wrote:

> hi,
>
> this is a client-side problem. Please report to NoMachine!
>
> Best Wishes and Have Fun,
>
> Fabian
>
> -------- Original-Nachricht --------
>> Datum: Fri, 28 Mar 2008 11:27:47 -0400
>> Von: Prakash Velayutham <prakash.velayutham at cchmc.org>
>> An: User Support for FreeNX Server and kNX Client <freenx- 
>> knx at kde.org>
>> Betreff: [FreeNX-kNX] Mac client cannot connect to server (worked  
>> fine for 2	or 3 times)
>
>> Hello All,
>>
>> I just now installed a OpenSuSE 10.3 server with the following RPMs
>> (from OpenSuSE download).
>>
>> nxshell-1.3-27.1
>> qtnx-0.0.1SVNr281-78.1
>> nxclient-3.1.0-6
>> NX-2.1.0-131.1
>> FreeNX-0.7.2-1.1
>> knx-0.1-37.1
>>
>> My setup is a little different in that my FreeNX server gets its root
>> file system NFS mounted (read-only) from a NFS server, so in
>> nxloadconfig I changed the relevant parameters to /var/rw/etc/ 
>> nxserver
>> and /var/rw/lib/nxserver where required. nxsetup --install --setup-
>> nomachine-key worked fine too (I will change the key as soon as
>> everything is setup correctly and working consistently).
>>
>> Also, my node.conf is the default that comes with the installer.
>>
>> From both a Mac NX Client (3.1.0-6) and Windows NX Client (3.1.0-6) I
>> was able to connect to this server for at least a couple times.
>> Actually after suspending from Mac client, I was even able to resume
>> on the Windows (through Mac VMWare fusion) client.
>>
>> But, now I am able to start new sessions/resume suspended sessions
>> from the Windows client, but cannot start / resume sessions from the
>> Mac client totally. This is what I see when I click on the "Details"
>> button.
>>
>> #####################################################################################################################
>>
>> NXPROXY - Version 3.1.0
>>
>> Copyright (C) 2001, 2007 NoMachine.
>> See http://www.nomachine.com/ for more information.
>>
>> Info: Proxy running in client mode with pid '8625'.
>> Session: Starting session at 'Fri Mar 28 10:47:28 2008'.
>> Warning: Connected to remote version 2.1.0 with local version 3.1.0.
>> Info: Connection with remote proxy completed.
>> Error: Call to bind failed for font TCP port 11000. Error is 48
>> 'Address already in use'.
>> Session: Session terminated at 'Fri Mar 28 10:47:28 2008'.
>>
>> #####################################################################################################################
>>
>> On the server's nxserver.log, this is what I get:
>>
>> #####################################################################################################################
>>
>> NX> 103 Welcome to: bmiclusterlogin1 user: prakash
>> NX> 105 listsession --user="prakash" --status="suspended,running" --
>> geometry="1440x900x32+render" --type="unix-kde"
>> NX> 127 Sessions list of user 'prakash' for reconnect:
>>
>> Display Type             Session ID                       Options
>> Depth Screen         Status      Session Name
>> ------- ---------------- -------------------------------- --------
>> ----- -------------- ----------- ------------------------------
>>
>>
>> NX> 148 Server capacity: not reached for user: prakash
>> NX> 105 startsession  --link="modem" --backingstore="1" --
>> encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1"  
>> --
>> strict="0" --composite="1" --samba="1" --media="0" --
>> session="bmiclusterlogin1" --type="unix-kde" --
>> geometry="1024x768+208+53" --client="macosx" --keyboard="query" --
>> screeninfo="1024x768x32+render"
>>
>> &link=modem&backingstore=1&encryption=1&cache=16M&images=64M&shmem=1&shpix=1&strict=0&composite=1&samba=1&media=0&session=bmiclusterlogin1&type=unix-kde&geometry=1024x768+208+53&client=macosx&keyboard=query&screeninfo=1024x768x32+render&clientproto=2.1.0&user=prakash&userip=10.19.100.24&uniqueid=20CBF3A6F2150BD48DAE1DCFA5A5AFF8&display=1000&host=127.0.0.1
>> Password:
>> NX> 1000 NXNODE - Version 2.1.0-131.1 OS (GPL, using backend: 2.1.0)
>> server_nxnode_echo: NX> 1000 NXNODE - Version 2.1.0-131.1 OS (GPL,
>> using backend: 2.1.0)
>> NX> 700 Session id:
>> bmiclusterlogin1-1000-20CBF3A6F2150BD48DAE1DCFA5A5AFF8
>> NX> 705 Session display: 1000
>> NX> 703 Session type: unix-kde
>> NX> 701 Proxy cookie: a1a8a8e356423cc3e42037ca4eb50569
>> NX> 702 Proxy IP: 127.0.0.1
>> NX> 706 Agent cookie: a1a8a8e356423cc3e42037ca4eb50569
>> NX> 704 Session cache: unix-kde
>> NX> 707 SSL tunneling: 1
>> server_nxnode_echo: NX> 700 Session id:
>> bmiclusterlogin1-1000-20CBF3A6F2150BD48DAE1DCFA5A5AFF8
>> server_nxnode_echo: NX> 705 Session display: 1000
>> server_nxnode_echo: NX> 703 Session type: unix-kde
>> server_nxnode_echo: NX> 701 Proxy cookie:
>> a1a8a8e356423cc3e42037ca4eb50569
>> server_nxnode_echo: NX> 702 Proxy IP: 127.0.0.1
>> server_nxnode_echo: NX> 706 Agent cookie:
>> a1a8a8e356423cc3e42037ca4eb50569
>> server_nxnode_echo: NX> 704 Session cache: unix-kde
>> server_nxnode_echo: NX> 707 SSL tunneling: 1
>> NX> 709 File-sharing port: 445
>> server_nxnode_echo: NX> 709 File-sharing port: 445
>> NX> 1009 Session status: starting
>> server_nxnode_echo: NX> 1009 Session status: starting
>> NX> 710 Session status: running
>> NX> 1002 Commit
>> NX> 1006 Session status: running
>> server_nxnode_echo: NX> 710 Session status: running
>> server_nxnode_echo: NX> 1002 Commit
>> session_status 20CBF3A6F2150BD48DAE1DCFA5A5AFF8 Running
>> NX> 105 server_nxnode_echo: NX> 1006 Session status: running
>> bye
>> Bye
>> NX> 999 Bye
>> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot
>> set SESSION_LOG_CLEAN=0 in node.conf and investigate "/users/
>> prakash/.nx/F-C- 
>> bmiclusterlogin1-1000-20CBF3A6F2150BD48DAE1DCFA5A5AFF8/
>> session". You might also want to try: ssh -X myserver; /usr/bin/ 
>> nxnode
>> --agent to test the basic functionality. Session log follows:
>>
>> NXAGENT - Version 2.1.0
>>
>> Copyright (C) 2001, 2006 NoMachine.
>> See http://www.nomachine.com/ for more information.
>>
>> Info: Agent running with pid '28100'.
>> Session: Starting session at 'Fri Mar 28 11:20:27 2008'.
>> Loop: WARNING! Ignoring unknown option 'menu' with value '1'.
>> Warning: Ignoring unknown option 'menu' with value '1'.
>> Info: Proxy running in server mode with pid '28100'.
>> Info: Waiting for connection from '127.0.0.1' on port '5000'.
>> Info: Accepted connection from '127.0.0.1' with port '40716'.
>> Info: Connection with remote proxy established.
>> Warning: Connected to remote NXPROXY version 3.1.0 with local version
>> 2.1.0.
>> Warning: Consider checking http://www.nomachine.com/ for updates.
>> Info: Synchronizing local and remote caches.
>> Info: Handshaking with remote proxy completed.
>> Info: Using modem link parameters 256/24/1/0.
>> Info: Using agent parameters 5000/50/0/0.
>> Info: Using cache parameters 4/4194304/16384KB/16384KB.
>> Info: Using image streaming parameters 50/128/1024KB/1024/128.
>> Info: Using image cache parameters 1/1/65536KB.
>> Info: Using pack method '16m-jpeg-3' with session 'unix-kde'.
>> Info: Using ZLIB data compression 6/6/32.
>> Info: Using ZLIB stream compression 9/9.
>> Info: Using cache file '/users/prakash/.nx/cache-unix-kde/C-
>> BA5203502584696383BBB7441F996DF0'.
>> Info: Listening for SMB connections on port '4000'.
>> Error: Connection with remote peer broken.
>> Error: Please check the state of your network and retry.
>>
>> Fatal server error:
>> Error: Unable to open display 'nx/nx,options=/users/prakash/.nx/C-
>> bmiclusterlogin1-1000-20CBF3A6F2150BD48DAE1DCFA5A5AFF8/options:1000'.
>>
>> xrdb: Connection reset by peer
>> xrdb: Can't open display ':1000'
>> NX> 1006 Session status: closed
>> server_nxnode_echo: NX> 596 Session startup failed.
>>
>> #####################################################################################################################
>>
>> Clien-side logs:
>>
>> errors:
>>
>> Loop: WARNING! Connected to remote version 2.1.0 with local version
>> 3.1.0.
>> Loop: PANIC! Call to bind failed for font TCP port 11000. Error is 48
>> 'Address already in use'.
>>
>> options:
>>
>> nx/
>> nx
>> ,cookie
>> =
>> a1a8a8e356423cc3e42037ca4eb50569
>> ,shmem
>> =
>> 1
>> ,shpix
>> =
>> 1
>> ,font
>> =
>> 1
>> ,samba
>> =
>> 445
>> ,encryption
>> =
>> 1
>> ,session
>> =
>> session
>> ,id=bmiclusterlogin1-1000-20CBF3A6F2150BD48DAE1DCFA5A5AFF8,display=:
>> 0:1000
>>
>> stats:
>>
>> session:
>>
>>
>> NXPROXY - Version 3.1.0
>>
>> Copyright (C) 2001, 2007 NoMachine.
>> See http://www.nomachine.com/ for more information.
>>
>> Info: Proxy running in client mode with pid '8720'.
>> Session: Starting session at 'Fri Mar 28 11:20:17 2008'.
>> Warning: Connected to remote version 2.1.0 with local version 3.1.0.
>> Info: Connection with remote proxy completed.
>> Error: Call to bind failed for font TCP port 11000. Error is 48
>> 'Address already in use'.
>> Session: Session terminated at 'Fri Mar 28 11:20:17 2008'.
>>
>> Any help greatly appreciated.
>>
>> Thanks,
>> Prakash
>> ________________________________________________________________
>>     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 at kde.org
>>      https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
> ________________________________________________________________
>     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 at kde.org
>      https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________




More information about the FreeNX-kNX mailing list