Thanks to all who answered my questions regarding the KUser application. I think we have "solved" the issue. This is what we found out: After searching links provided on the subject of NIS, looking in the rc.config file and also checking /etc/passwd and /etc/group, we found no indication that NIS was running on the system at all. We checked the rc.config in YAST2 just to make sure, and even checked YAST1. It would seem that the application (for some reason) is looking for this service to run, even when it isn't supposed to. Anyway, finally my brain got into gear and I checked the SuSE Linux Support site (should have done that first I guess :-) I searched "KDE2 User Manager failing" and the result was satisfying in a weird way. It told us that there is "an error in the user manager of KDE2" and that the solution was to "use YaST1 to manage your users". This is what we had thought in the first place, but wanted to check it out anyway. The knowledgebase article reference is mjb_kuser_71. So- we will now be using YaST1 (which isn't that bad anyway). Again, thanks to all who helped :-) Paul