Hello everyone, I ampreparing forthe upgrade ofExchange 2000 server to Exchange 2003; I would bedoingan in-place upgrade. As part of the prep process, I ran the DcDiag and NetDiag tools to make sure there are no issues, but I am getting a FATAL Kerberos error whenI run the NetDiag tool. The error output line says: [FATAL] Kerberos does not have a ticket for SERVERNAME$. I ran NetDiag with /v (verbose) and the server seems to have cached Kerberos credentials which get renewed automaially. I have looked on the web briefly about this issue, but havent found anythingpointing staright to the problem, except afew articles: Microsoft KB870692: You receive a "Kerberos does not have a ticket" error message when you run Netdiag.exe on a Windows Server 2003-based member server in a Windows 2000-based domain Microsoft KB244474 : How to force Kerberos to use TCP instead of UDP in Windows Server 2003, in Windows XP, and in Windows 2000 TechRepublic article : Fix Exchange 2003 Netdiag/Kerberos glitch Facts about the domain and Exchange: - 3 domain controllers;ALL on Windows 2003, butdomain is running in "Windows 2000 native" mode (I think the previous network admin tried raising domain functional level to Windows 2003 native, but facedsome problem.. so went back to Windows 2000 native). - The Exchange server is a member server running Exchange 2000 Service Pack 3 (with post-SP3 rollup update) on Windows 2000 SP4. * Has anyone come across a similar problem before!? What can I do to fix this Kerberos error in the NetDiag tool. Someone suggested removing the server from the domain and attaching it back (with Exchange installed as it is)!Will that mess up Exchange!? * What does the /fix switch in NetDiag do!? Would that help? Any suggestions/ideas are whole-heartedly welcome! Thanks a lot in advance! Cheers, Vinay.