The network consists of 1 windows server 2003 r2 and windows server 2008 standard edition domain controllers.
Recently, moved all the fsmo roles from the 2003 to the 2008 server. I plan of adding a new server 2008 domain controller so that I can get rid of the 2003 server due to hardware issue and support from Microsoft which will end 2015.
Of late, have been getting numerous Event ID 27 and source KDC errors on the windows server 2003 r2 which states: While processing a TGS request for the target server krbtgt/amanua.net, the account PC22$@amanua.net did not have a suitable key for generating a Kerberos ticket (The missing key has an ID of 8 )The requested etypes were 18. The accounts available etypes were 23 -133 -128 3 1.
Users and computers are being authenticated by any one of the servers and they can use the network resources but need to fix this problem.Any idea and if I go ahead and add the new server 2008 and configure it as a domain controller before decommissioning the server 2003 but do not fix those errors on the server 2003 what may be the issue.
Recently, moved all the fsmo roles from the 2003 to the 2008 server. I plan of adding a new server 2008 domain controller so that I can get rid of the 2003 server due to hardware issue and support from Microsoft which will end 2015.
Of late, have been getting numerous Event ID 27 and source KDC errors on the windows server 2003 r2 which states: While processing a TGS request for the target server krbtgt/amanua.net, the account PC22$@amanua.net did not have a suitable key for generating a Kerberos ticket (The missing key has an ID of 8 )The requested etypes were 18. The accounts available etypes were 23 -133 -128 3 1.
Users and computers are being authenticated by any one of the servers and they can use the network resources but need to fix this problem.Any idea and if I go ahead and add the new server 2008 and configure it as a domain controller before decommissioning the server 2003 but do not fix those errors on the server 2003 what may be the issue.
