[Ltsp-discuss] Stangeness with new GDM/XMCP sessions

[Patrick P. <pru...@gm...>]

I am replacing an older LTSP machine that was running Fedora 6 32bit and
working flawlessly with a new IBM x3620 running Centos 5.5. Since we are not
Pxebooting we arent using the chroot'd LTSP environment so i went to
Centos5.5 from Fedora 13 because i was having to many issues with a number
of things. All the clients are older Neoware thin clients connecting via
XDMCP
GDM is the display Manager , Gnome is the desktop

However wondering if anyone might have any ideas on the issues i have
experienced here

Samba/AD integration is functional properly with users being able to login
Home directories are mounted over a NFS mount to a samba server

When a local linux account logs into the XDMCP session everything is
prefectly fine

When an AD user logs into XDMCP session they get errors popping up on the
screen about unable to save configuration for gecko or something along those
lines .
The /var/log/messages shows the following

ltsp-01 gconfd (aduserid-14735): Failed to get lock for daemon, exiting:
Failed to lock '/tmp/gconfd-aduserid/lock/ior': probably another process has
the lock, or your operating system has NFS file locking misconfigured
(Resource temporarily unavailable)

Any ideas on what might cause this and how to resolve ??