Hi Dave-
Here's a quick reference that may help:
0x7 (KRB_ERR_S_PRINCIPAL_UNKNOWN) "Server not found in Kerberos database"
-------------------------------------------------------------------------
The KDC could not translate the server principal name from the
KDC request into an account in the Active Directory. Generally,
verifying
whether the server account exists and has propagated to the domain
controller
that generated the error. Checking Active Directory replication may
provides an
indication of why the error occurred. Also if the server is not at least
Windows 2000, there will not be any service principal names registered
because
that server is not capable of authenticating with Kerberos. In this
case, this
error can be ignored because the client will then switch to NTLM for
authentication.
So, first thought is: is there an user account for this machine in AD, and
is it present on every domain controller?
--
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Dave said:
I am receiving the above error even though the machine is in fact in our
AD and I could manage the machine via AD from the Ad server. The machine
has 2 IP addresses. It is a replacement SQL server, so upon set-up it was
using IP address 10.10.1.99. When the migration was ready, the orginal SQL
server was shut down and the IP address from it was assigned to the new
serevr in addition to the .99 address. The server is referenced by the .71,
the orginal SQL server's address in all programs. Any help in resolving
this would be of great appreciation. The new SQL server has 2 files in DNS,
1 for each IP.
