[FreeNX-kNX] kNX behind a firewall (only port 22 open) unusable?
Gian Filippo Pinzari
pinzari at nomachine.com
Fri Feb 18 23:43:35 UTC 2005
Fabian Franz wrote:
> though its stating there that its listen=port, while nxclient does not use
> this but just accept=127.0.0.1.
Do you mean nxserver here?
On the server the port is implicit, as it matches the NX proxy
port at the offset corresponding to the display.
On the client the port is chosen dinamically, so nxproxy needs to
know where the connection is going to be forwarded. I've just run
a session and this is the content of 'option' file on the client:
cookie=**********************************,root=C:\DOCUME~1\GIANFI~1\NX73F8~1,keybd=6000,\
session=XP-on-TestDrive,id=test00-1037-2EAC6D7546F2A4BFA3DD0095AD82F059,listen=1906:1037
There is a FR to add the 'accept' options to data passed to nxcomp
by nxclient. This, anyway, doesn't make much a difference. At the
moment nxcomp only binds to the 127.0.0.1 interface on the client
side.
/Gian Filippo.
More information about the FreeNX-kNX
mailing list