Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Jul 2020 11:35:38 -0400
From:      D'Arcy Cain <>
Subject:   Running XDM remotely
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
Content-Type: multipart/mixed; boundary="mrMjgphC1IBAlQGD02LZUERWVP6UYfRJk"

Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

I think that I have followed all of the instructions but it still isn't
working.  I commented out "DisplayManager.requestPort:     0" in xdm-conf=
and added "CHOOSER BROADCAST" to Xaccess.  After restarting xdm I expecte=
to see the system listening on port 177 but it isn't.  Is there another s=
that I am missing?

Once I do have it working I also need to access it through a NAT gateway.=

Do I just have to redirect port 177 for TCP and UDP or are there other po=
that need to be forwarded?

Also, once I have this running, what kind of thin clients are available? =
there anything that can run on Windows or do I need to create a FreeBSD o=
Linux thin client?


D'Arcy J.M. Cain <>         |  Democracy is three wolves                |  and a sheep voting on
+1 416 788 2246     (DoD#0082)    (eNTP)   |  what's for dinner.
IM:, VoIP:

Disclaimer: By sending an email to ANY of my addresses you
are agreeing that:

1.  I am by definition, "the intended recipient".
2.  All information in the email is mine to do with as I see
    fit and make such financial profit, political mileage, or
    good joke as it lends itself to. In particular, I may quote
    it where I please.
3.  I may take the contents as representing the views of
    your company if I so wish.
4.  This overrides any disclaimer or statement of
    confidentiality that may be included or implied in
    your message.


Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"




Want to link to this message? Use this URL: <>