XWin/xdmcp fails after PC domain change

[Greg Dotts]

Igor, thanks for this info.

I posted the solution a little earlier this evening and based on your 
comments now makes perfect sense.

I allow dynamic updates to my internal DNS records (silly for two PC's, 
but whats a geek to do) and it turned out the DNS suffix entry was 
removed from my desktop PC during all the rearranging.

This translates into xwin/xdmcp referencing an old DNS record and 
refusing to connect.  It's usually the simple stuff isn't it???

Thanks again


Igor Pechtchanski wrote:
>> On Thu, 13 Jan 2005, Greg Dotts wrote:
>>I could sure use some help solving a problem with my Cygwin/X (on MS XP Pro
>>SP1 -> Fedora 2 xdmcp connection.
>>
>>[snip]
>>
> XDMCP is very sensitive to DNS changes.  Make sure that when the server
> does a reverse DNS lookup on the IP, it gets the same FQDN as supplied by
> your Cygwin machine.  Check /var/log/messages on the server.  Do you have
> a stale /etc/hosts entry, perhaps?
> 
> See <http://en.tldp.org/HOWTO/XDMCP-HOWTO/> and
> <http://cygwin.com/ml/cygwin-xfree/2004-04/msg00329.html>.
> HTH,
> 	Igor

-- 
GDD
a.k.a. Greg Dotts

If quitters never win, and winners never quit,
what fool came up with, "Quit while you're ahead"?