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

[Michael Bloxham]

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?





__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20070417/d1e7f21a/attachment.html>