[FreeNX-kNX] Windows NX client fails with Error 112 port bind for font error

[torrr com]

Hi, I am not really sure that I understand, but here is a suggestion
anyway, hope it helps:)

In the NX client -> configure > Advanced > Enable SSL encryption of all traffic
Check this checkbox.

Check it on the local network, and then from a remote site.
 If it doesn't work, check that your SSH works from a local/remote PCs.

On 4/20/07, Jack Tanner <ihok at hotmail.com> wrote:
> Michael Bloxham wrote:
> > This was asked before back in November of 2006:
> >
> >>Whenever I have one NX client and I try to make a new connection I get the error below:
> >>Error: Call to bind failed for font TCP port 11000. Error is 112 'Address already in use'.
> >>When I try another connection to machine on the local network, I don't get such errors
> >>What could be the problem, I am using the Windows NX client with freenx on fedora
> >
> > I did not see a response, and I too am getting this error when opening a second NX session.
> > The NX client is trying to listen on port 11000 for font server connections, but it can't do
> > this for a 2nd session.
> >
> > Are concurrent NX sessions (to different hosts even) not supported?
>
> I asked a question about this a couple of weeks ago, but noone's
> responded. Concurrent sessions used to work! Are they working for anyone
> today?
>
> ________________________________________________________________
>      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
> ________________________________________________________________
>