cifs is the host SPN and shall be computername with and without DNS-suffix, but without the port number.
Use 'setspn -R <servername>' to re-register HOST-SPN.
Main Topics
Browse All TopicsI have a new web application that has been set up on a new Windows 2003 server that was provided to us. Currently the client is trying to authenticate with Kerberos but cannot. In the event viewer the on the hosting server the error 0x7 KDC_ERR_S_PRINCIPAL_UNKNOW
Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 3
Date: 12/2/2008
Time: 10:26:50 AM
User: N/A
Computer: OHCLEIIS102C
Description: A Kerberos Error Message was received: on logon session
Client Time: Server Time: 15:26:50.0000 12/2/2008 Z
Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOW
Extended Error:
Client Realm:
Client Name:
Server Realm: CORP.NTL-CITY.NET
Server Name: cifs/OHCLECFI1017
Target Name: cifs/OHCLECFI1017@CORP.NTL
Error Text:
File: 9
Line: ae0
Error Data is in record data.
Everything I have read seems to indicate that I have incorrect spns registered or that I am missing an spn.Currently I the application lives at the following url: http://Ohcleiis102c.corp.n
setspn -l corpdmn\secm03c yields the following
HTTP/ohcleiis102c
Host/Ohcleiis102c.corp.ntl
Host/ohcleiis102c:81
HTTP/Ohcleiis102c.corp.ntl
NCC/Ohcleiis102c.corp.ntl-
HTTP/ohcleiis102c:81
NCC/ohcleiis102c:81
Where I am uncertain is to where do the spns need to be registered and how do I detrermine this. Any help or direction would be greatly appreciated.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: jazzcatonePosted on 2008-12-02 at 14:10:16ID: 23081401
Update: The developers and myself decided to put the application on the default port 80. We then deleted all of the mentioned spn entries. We then re registered spns, so upon doing a setspn -a corpdmn\secm03c it now looks like this:
-city.net city.net
.net. The client is now able to authenticate ! I have done lots and lots of reading on Kerberos and SPNs. I have to say I am not sure as to whether I understand why it did not work before while running on port 81 as long as we had spns registered there.(or if they would even need to be registered there!) If anybody can shed some light on this it would be greatly appreciated.
HTTP/ohcleiis102c
HTTP/Ohcleiis102c.corp.ntl
NCC/ohcleiis102c
NCC/Ohcleiis102c.corp.ntl-
and the application lives at Ohcleiis102c.corp.ntl-city