connecting to KDM using XDMCP?

[Clive Mayo]

Having the same problem "XDM: too many 
retransmissions", done the edits to xdm-config and Xaccess.
 
Checked "netstat -ua" and its not showing xdmcp 
running.
How do you configure xdmcp?
 
Running Windows NT and Linux 2.2.14 
SusE.
 
Xaccess
xdm-config

-------------- next part --------------
# $XConsortium: Xaccess,v 1.5 91/08/26 11:52:51 rws Exp $
#
# Access control file for XDMCP connections
#
# NOTE: In order to use this feature the resource
#       DisplayManager.requestPort in xdm-config
#       should be commented out to enable XDMCP.
#
# To control Direct and Broadcast access:
#
#	pattern
#
# To control Indirect queries:
#
# 	pattern		list of hostnames and/or macros ...
#
# To use the chooser:
#
#	pattern		CHOOSER BROADCAST
#
# or
#
#	pattern		CHOOSER list of hostnames and/or macros ...
#
# To define macros:
#
#       %name		list of hosts ...
#
# The first form tells xdm which displays to respond to itself.
# The second form tells xdm to forward indirect queries from hosts matching
# the specified pattern to the indicated list of hosts.
# The third form tells xdm to handle indirect queries using the chooser;
# the chooser is directed to send its own queries out via the broadcast
# address and display the results on the terminal.
# The fourth form is similar to the third, except instead of using the
# broadcast address, it sends DirectQuerys to each of the hosts in the list
#
# In all cases, xdm uses the first entry which matches the terminal;
# for IndirectQuery messages only entries with right hand sides can
# match, for Direct and Broadcast Query messages, only entries without
# right hand sides can match.
#

*					#any host can get a login window

#
# To hardwire a specific terminal to a specific host, you can
# leave the terminal sending indirect queries to this host, and
# use an entry of the form:
#

#terminal-a	host-a


#
# The nicest way to run the chooser is to just ask it to broadcast
# requests to the network - that way new hosts show up automatically.
# Sometimes, however, the chooser can't figure out how to broadcast,
# so this may not work in all environments.
#

*		CHOOSER BROADCAST	#any indirect host can get a chooser

#
# If you'd prefer to configure the set of hosts each terminal sees,
# then just uncomment these lines (and comment the CHOOSER line above)
# and edit the %hostlist line as appropriate
#

#%hostlist	host-a host-b

#*		CHOOSER %hostlist	#
-------------- next part --------------
!
! xdm-config:	Configuration of the xdm
!
DisplayManager.errorLogFile:	/var/log/xdm.errors
DisplayManager.pidFile:		/var/run/xdm.pid
DisplayManager.authDir:		/var/lib/xdm
DisplayManager.keyFile:		/etc/X11/xdm/xdm-keys
DisplayManager.servers:		/etc/X11/xdm/Xservers
DisplayManager.accessFile:	/etc/X11/xdm/Xaccess
DisplayManager.willing:		su nobody -c /etc/X11/xdm/Xwilling
!
! ATTENTION: `authName' should be in general MIT-MAGIC-COOKIE-1
! For XDM-AUTHENTICATION-1 which is default for xterminals see
! manual page of xdm and the manual coming with the xterminal.
!
DisplayManager.*.authName:	MIT-MAGIC-COOKIE-1
DisplayManager.*.authComplain:	false
!
! All displays should use authorization, but we cannot be sure
! X terminals will be configured that way, so by default
! use authorization only for local displays :0, :1, etc.
!
DisplayManager._0.authorize:	true
DisplayManager._1.authorize:	true
!
! The scripts handling the setup, the startup, the session its self,
! and the reset of an X session.
!
DisplayManager.*.setup:		/etc/X11/xdm/Xsetup
DisplayManager.*.chooser:	/etc/X11/xdm/RunChooser
DisplayManager.*.startup:	/etc/X11/xdm/Xstartup
DisplayManager.*.session:	/etc/X11/xdm/Xsession
DisplayManager.*.reset:		/etc/X11/xdm/Xreset
!
DisplayManager._0.terminateServer:	true
!
DisplayManager*resources:	/etc/X11/xdm/Xresources
DisplayManager.*.terminateServer:	false
!
! SECURITY: do not listen for XDMCP or Chooser requests
! Comment out this line if you want to manage X terminals with xdm
!
! DisplayManager.requestPort:	0