<div dir="ltr"><div class="gmail_quote">On Sun, Oct 12, 2008 at 10:08 PM, Yan Seiner <span dir="ltr"><<a href="mailto:yan@seiner.com">yan@seiner.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">Yan Seiner wrote:<br>
> r<br>
> Damn, I used to have an old laptop that I had this set up on...<br>
><br>
> Read up on the GDM docs. There is a setting in gdm.conf that tells it<br>
> to only act as an XDMCP server and not start a local X session at all.<br>
><br>
> Then you can use any other gdm login to remotely connect. Again, you<br>
> may have to enable the menu option in that machine's gdm.conf<br>
><br>
> It's really simple if you find the settings - one or two lines on each<br>
> machine IIRC.<br>
><br>
><br>
</div>OK, on my debian lenny system, add<br>
<br>
[xdmcp]<br>
Enable=true<br>
<br>
to gdm.conf on the server. Restart gdm.<br>
<br>
I don't know how you disable the local X session.<br>
<br>
On the client, there is a "Connect using XDMCP" under "Actions" (I'm<br>
translating here so it may not be the exact wording) at the gdm login.<br>
<br>
It should locate the server via broadcasts. If the server is firewalled,<br>
you'll have to allow UDP 177 IIRC.<br>
<div><div></div><div class="Wj3C7c"><br>
--Yan<br>
_______________________________________________</div></div></blockquote><div><br></div><div>Thanks, I got XDMCP to work last night. Once I found the gdm.conf file it was no problem.</div><div><br></div><div>-Ryan</div></div>
</div>