[6963] in Kerberos
changing a CNS V4 setup to a new network
daemon@ATHENA.MIT.EDU (sysop@omega.megahits.com)
Wed Mar 27 14:48:59 1996
Date: Wed, 27 Mar 1996 14:15:05 -0500
To: kerberos@MIT.EDU
From: sysop@omega.megahits.com
Cc: nate@millcomm.com
We recently began the process of converting our entire ISP over to a T1 and
a completely new set of IP addresses. This process included a linux box on
which we had CNS V4 running without any problems, authenticating modem
access requests via xyplex terminal servers at 2 different frame relay
locations. After having numerous difficulties converting the actual linux
box itself to recognize and use the new network, (many of which STILL
haven't been resolved), we started to try to change over our kerberos setup
as well. After editing all the configuration files I could think of,
replacing megahits.com with megahits.net and whatnot, I rebooted the box. It
failed to start kerberos properly. I modified a few more settings, and now I
have it to the point where a 'kdb_init' runs successfully. However, when I
run 'kerberos' after 'kdb_init' I get the following error message
(reproduced here in its entirety for completeness' sake):
--
Kerberos server starting
Sleep forever on error
Log file is /usr/kerberos/database/kerberos.log
Current Kerberos master key version is 1.
Master key entered.
Current Kerberos master key version is 1
Local realm: MEGAHITS.NET
Ticket granting ticket service unknown
--
I assume there are still some settings which I have not yet changed over
from the megahits.com setup. Or perhaps it has something to do with the fact
that when I reboot I seem to lose all the new settings that I have entered
into the linux box with the route and ifconfig commands. Anyway, the bottom
line is that any help would be greatly appreciated, as we are in a bit of a
pinch here... as long as this ISN'T working, we have customers in 2 major
calling areas of the state that are unable to use the service they are
paying for.
Regards,
Lou Rinaldi
Omega Solutions, Inc.
