Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Kerberos Problems on Win 2003 Member Servers

Posted on 2003-10-22
8
Medium Priority
?
9,069 Views
Last Modified: 2007-12-19
We have a Windows 2000 AD domain, and have started to upgrade some of the member servers to Windows Server 2003.  We currently have 4 member servers running Win Server 2003 standard.  
 
On one of those, I am preparing to install Exchange Server 2003, and one of the prerequisites is to run netdiag to verify everything is working ok on the network.  When I ran the netdiag tool, it reported a FATAL Kerberos error:
 
[FATAL]  Kerberos does not have a ticket for "host/memberserver.domain"
 
I did some looking around, and found all of the Windows 2003 member servers are experiencing the same problem.  Our Windows 2000 member servers seem fine.  When I look in the security log on the domain controller , there are all kinds of errors being logged as follows:
 
Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 677
Date:  10/20/2003
Time:  12:02:04 PM
User:  NT AUTHORITY\SYSTEM
Computer:  "DOMAIN CONTROLLER NAME"
Description:
Service Ticket Request Failed:
  User Name:
  User Domain:
  Service Name:
  Ticket Options: 0x40830000
  Failure Code: 0xE
  Client Address: "MEMBER SERVER IP ADDRESS"

I enabled kerberos logging on a couple of the member servers, and they are recording system events that look as follows:
 
Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 3
Date:  10/20/2003
Time:  12:12:55 PM
User:  N/A
Computer: "MEMBER SERVER NAME"
Description:
A Kerberos Error Message was received:
         on logon session
 Client Time:
 Server Time: 16:12:55.0000 10/20/2003 Z
 Error Code: 0xe KDC_ERR_ETYPE_NOTSUPP
 Extended Error:
 Client Realm:
 Client Name:
 Server Realm: DOMAIN NAME
 Server Name: krbtgt/"DOMAIN NAME"
 Target Name: host/MEMBER SERVER.DOMAIN@DOMAIN
 Error Text:
 File: 9
 Line: ab8
 Error Data is in record data.
 
0xE is an error code for "kerberos encryption type not supported".  I have looked high and low on the net, and found other reports of similar problems, but no solution for the problem.  It appears to be some kind of glitch between Windows 2003 member servers, and Windows 2000 Domain controllers.  Everything seems to be working OK, but I am hesitant to proceed with the Exchange 2003 setup until this is resolved.  
 
Anyone??
 
Chris Smout
0
Comment
Question by:csmout
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
  • +1
8 Comments
 
LVL 51

Expert Comment

by:Netman66
ID: 9618462
Here is more on that:

0xE (KDC_ERR_ETYPE_NOTSUPP) "KDC has no support for the encryption type"

The client tried to use an encryption type that the KDC does not support, for any of the following reasons:

The client's account does not have a key of the appropriate encryption type.
The KDC (cross-realm trust) account does not have a key of the appropriate encryption type.
The requested server account does not have a key of the appropriate encryption type.
The type may not be recognized at all, for example, if a new type is introduced. This happens most frequently with MIT compatibility, where an account may not yet have an MIT compatible key. Generally, a password change must occur for the MIT-compatible key to be available.


Try right-clicking the computer account in AD for the suspect server and selecting Reset Account.

If that doesn't work, use NETDOM to reset account.

http://support.microsoft.com/default.aspx?scid=kb;[LN];325850

These may also help:

http://support.microsoft.com/default.aspx?scid=kb;[LN];232179

Now, with respect to Exchange 2003 - doesn't it require Active Directory?  Which likely means that it needs to run on a DC.

Advise.




0
 
LVL 51

Expert Comment

by:Netman66
ID: 9618505
Hmmm...found something else.

Open the Local Security Settings on the 2003 server (from Administrative Tools).

Expand Local Policies>Security Options.

Find this: Domain Member: Digitally Encrypt  or Sign secure channel data (always) and disable it.

If you want to know more about what that setting does, right-click it and select Help.

Hope this helps too!

0
 

Author Comment

by:csmout
ID: 9723581
I opened a ticket with Microsoft on the issue, and the problem turns out to be an issue between 2000 DC's and 2003 member servers.   Here is an exceprt from the Microsoft email:

As I mentioned in my previous email, Windows 2003 introduces support for constrained delegation which by leveraging the S4U2Proxy extension to Kerberos. The Kerberos client on a Windows 2003 server will regularly (every 15 minutes by default) check the KDC to see if it supports S4U. Windows 2000 does not support S4U and will instead log a Security Audit event. I discussed the event with the development team and confirmed that it will NOT impact the upgrade to Exchange 2003

The end result was that they sent me a hotfix to install on the DC to stop the errors from being recorded in the security log every couple of minutes.  

Chris
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 9754115
PAQed, with points refunded (500)

Computer101
E-E Admin
0
 

Expert Comment

by:mpedigo1
ID: 10056710
Microsoft will not provide the hotfix without a KB#  and claim they don't have a hotfix.  They want me to open an incident.  Does anybody have the KB#?

Thanks,

Mike
0
 

Author Comment

by:csmout
ID: 10061907
The number I was given was Q824905, but I can't pull that up on Microsoft's support site.
0
 

Expert Comment

by:mpedigo1
ID: 10089290
Thank you for the info...it helped MS find the info....They said there will be a page on the MS website soon regarding this issue.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is in response to a question (http://www.experts-exchange.com/Networking/Network_Management/Network_Analysis/Q_28230497.html) here at Experts Exchange. The Original Poster (OP) requires a utility that will accept a list of IP addresses …
Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question