Hi All, I've been using samba 2.2.8a running on RedHat 9 as a PDC for almost a year by now. Everything works great even though it required some time to configure everything properly. Our company decided to move to Active Directory running on Win2003 server.... I want to leave Samba as our file server, so I plan to use Samba 3.0.4 as a domain member server. I got one problem, though :-( It is said in the John Terpstra's book, that it is required to use kerberos 1.3. x to get Samba talking to Active Directory properly. RedHat 9 comes with kerberos version 1.2.7 and there's no way to remove/ reinstall/upgrade it via RPM without breaking dependencies. Actually, if you use -nodeps switch to install, let's say, kerberos 1.3.1, it will crash you system. The only way I see is to install kerberos from sources (tarballs). However, I don't know what will happen to the system, if I install a tarball over existing rpm installation. As far as I know, that's highly not recommended. Is there anybody who had managed to install Kerveros 1.3.x on Redhat 8/9 and proved it worked properly? I would really appreciate if you give me some clue how to do that. Thanks a lot. Andrey.
Hello, I had the same problem as you and it took me a while to figure it out exactly. I’ve now a RHL9 server running with Samba 3.0.4 as a domain member of a W2k3 realm. Actually I updated Kerberos to version 1.3.1-7 on my RHL9 server to achieve this; otherwise samba can’t verify the incoming ticket. You are right; if you install the Kerberos 1.3.1 rpm’s with --force --nodeps, it will break the dependencies, but this is the only way to do it. After the update of the krb5 packages the “libcom_err.so.3” dependency of other packages (example: httpd-2.0.40-21) is broken. A TEMPORARY workaround is to change to the /lib directory and make the following symbolic link: “ln -fs libcom_err.so.2.0 libcom_err.so.3” (This restores the libcom_err.so.3 dependency of other packages after the krb5 update.) Now you can see if Samba 3.0.4 is working properly in a W2k3 realm. What you should do afterwards is to recompile all the packages (on the machine with the Kerberos 1.3.1 rpm’s installed) that had a dependency with the old Kerberos packages and install those new recompiled packages. Now all the packages (that had a dependency with the old Kerberos packages) have a new dependency to Kerberos 1.3.1. After that you can remove the symbolic link with “libcom_err.so.3”. This cost me several headaches too… ;-) Regards, Alex. _________________________________________________________________ Talk with your online friends with MSN Messenger http://messenger.msn.nl/