[FreeNX-kNX] kNX behind a firewall (only port 22 open) unusable?

Fabian Franz FabianFranz at gmx.de
Fri Feb 18 23:35:08 UTC 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Samstag, 19. Februar 2005 00:43 schrieb Gian Filippo Pinzari:
> 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?

No. Sorry, I read the wrong options file while checking ... :-/

> cookie=**********************************,root=C:\DOCUME~1\GIANFI~1\NX73F8~
>1,keybd=6000,\
> session=XP-on-TestDrive,id=test00-1037-2EAC6D7546F2A4BFA3DD0095AD82F059,lis
>ten=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.

Yes, you are right sorry.

cu

Fabian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCFnuuI0lSH7CXz7MRAqKyAJ4yrujIWbtNKUlffxA1rueHEwEApACbBYYm
5+sm4GkUlEqDW2Xd37TwQxU=
=XbeR
-----END PGP SIGNATURE-----




More information about the FreeNX-kNX mailing list