KDE-Forum.org

I use in a small lab network NIS authentication method with home directories exported by NFS from a file server. All other desktop enviroments (gnome, wmaker, icewm, etc.), except kde, work fine. When I try logging and using kde enviroment, the system freezes. Do you have any ideas why?
Thanks!

Sorry for the vague description of the problem.
Exactly:
-I have an application server (because some applications are installed only on that server), a file server and some PCs.
-The application server exports by NIS (ypserv) usernames and passwords in the network and the file server shares by NFS a directory with users home files.
-On every station in the network I have a NIS client (ypbind) and I mount the directory shared by the file server in the local /home directory. Also, on every station I use X11 with gdm for login.
-In the gdm login window, if I choose whatever display manager (gnome, wmaker, etc.), excepting kde, everything works well.
-In the gdm login window, if I choose KDE, after login ksplash runs a quite long time and after that I have nothing on the screen, except the background image, and I can do nothing with the computer.
-The .xsession-errors files is:


/etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/X11/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "student"
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /etc/X11/xdm/Xsession KDE
startkde: Starting up...
ksplash: WARNING: KGenericFactory: instance requested but no instance name or about data passed to the constructor!
kbuildsycoca running...
DCOP Cleaning up dead connections.

I observed the problem is between KDE and NFS and, finally, I managed to solve it removing from the script /usr/bin/startkde the lines

KDE_FULL_SESSION=true
export KDE_FULL_SESSION

I am no expert in KDE, can anyone to explain me why was this the solution to my problem?
I know that, if KDE_FULL_SESSION=true, some supplementary programs (or scripts) are invoqued at the start of KDE. I suppose the problem is between those programs (scripts) and KDE.