Windows Server

glennw · Guest

When I run Netdiags this is the error I get. Document 870692 talks about
this but I'm running this on a Windows 2000 server in a 2003 domain trying to
get ready to do an in-place upgrade on my Exchange server. I need to move
forward but haven't because I haven't found a solution or a document that
says this is an OK error don't worry about it. The only document says MS
knows there's a problem but no fix. Any suggestions? Is this only a
cosmetic error or something I need to fix before upgrading my exchange server
to 2003. Thanks.

This is the error I get. Now again this is a Windows 2000 server in a 2003
domain not the other way around as MS says happens in their document.

Kerberos test. . . . . . . . . . . : Failed
[FATAL] Kerberos does not have a ticket for oth-mail$

Here is what Microsoft's TID says:

This problem occurs because Netdiag.exe searches only for the
host/domain_name kind of Kerberos ticket. Netdiag.exe does not search for the
computer_name$ kind of Kerberos ticket.

STATUS
Microsoft has confirmed that this is a problem in Netdiag.exe.

MORE INFORMATION
The Kerberos protocol lets you send private information across an otherwise
open network. Kerberos tickets are unique keys that are assigned to users and
computers when they log on to a network. A Kerberos ticket includes all the
user credentials or computer credentials in an encrypted format. These
credentials are used to identify a specific user or a specific computer on a
network for access to Kerberos services. The following list describes the two
types of Kerberos tickets:

Steven L Umbach · Guest

I have seen that error when running netdiag and everything worked fine as
long as everything else in netdiag looks good and there are no major
problems found in the logs seen via Event Viewer. So I tend to believe it
can be ignored. If it is a real problem your install would fail. To be safe
it would make sense to have an image backup of the server made just before
the upgrade and a current System State backup of a domain controller "just
in case" to have a rollback option. You may also want to post in an Exchange
newsgroup. --- Steve

Roger Abell [MVP] · Guest

As I read that it is an error of netdiag, not of the underlying tested
support. Have you tried that latest public netdiag, likely from
W2k3 Sp1 ?

glennw · Guest

I ran the Netdiags from SP4 tools not W2k3 tools

	Windows Server Forum Index -> Security	All times are GMT
Page 1 of 1