Kerberos on Connected to Directory System

I have an ODM + 4 replicas. I just want to add a Tiger Server connected for a home directory server for Macs and PCs. So I do the whole thing with Directory Access and restart the server. When rebooted, and logged in, I see in Server Admin that Open Directory is not running — that's fine. It's got the little green light out and the three items — LDAP server, Password Server, and Kerberos all are "Stopped." I have done this before and can have users login, etc. and not know the difference between a replica and connected to directory system. The thing is — I want to know — why are those things (LDAP, Password Server, and Kerberos) all off? I cannot Kerberize them. I tried this article here https://www.afp548.com/article.php?story=20060724104018616 and reading the manual carefully but no dice. It seems that this feature is broken...and has been...what am I missing? I'll do a replica if that's the recommend way. It's always worked and those features always seem to get lit up with replicas but WHY OH WHY does it always have to be this way? I hope this is fixed in Leopard Server because it's really shaky to me. Log files tell me that it could not add a principal, but it always says this. I hate mucking around with my ODM — I need it to work.