The kerberos client received a KRB_AP_ERR_MODIFIED error from the server

Event Type:&#9;Error
Event Source:&#9;Kerberos
Event Category:&#9;None
Event ID:&#9;4
Date:&#9;&#9;9/13/2010
Time:&#9;&#9;7:31:25 PM
User:&#9;&#9;N/A
Computer:&#9;DC1
Description:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server MRKMU11$. The target name used was cifs/MHE122.dpcs.org. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (DPCS.ORG), and the client realm. Please contact your system administrator.

I've seen this issue if the computer account doesn't have permissions to change its own DNS record. Then the computer changes IP (DHCP), and the old record stays. You should delete the bad DNS record (let it replicate the deletion to other DNS servers), then go to the CMD prompt on MHE122 and run IPCONFIG /REGISTERDNS

So this seems to be across the board, and thus effecting all pcs in the domain. A ping by name returns one ip address, a ping with a -a on the ip then returns a second name. I will verify this by going through each pc and ip address shortly.

Event Type: Warning
Event Source: DhcpServer
Event Category: None
Event ID: 1056
Date: 10/13/2010
Time: 5:00:05 PM
User: N/A
Computer: XXX
Description:
The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. This is not a recommended security configuration. Credentials for Dynamic DNS registrations may be configured using the command line "netsh dhcp server set dnscredentials" or via the DHCP Administrative tool.

How to Use the Netsh.exe Tool
NOTE: The Netsh.exe tool completes successfully only after you receive a "Command Successfully Completed" message.
To set the user account that the DHCP Server service uses for DNS registrations, use the following command:
netsh dhcp server set dnscredentials user name domain name password
Note that if you use an asterisk (*) in place of the password variable, you are prompted to type a password.

NOTE: You must restart the DHCP Server service for these changes to take effect.
To delete the user account that the DHCP Server service uses for DNS registrations, use the following command:
netsh dhcp server delete dnscredentials dhcpfullforce
NOTE: You must restart the DHCP Server service for these changes to take effect.
To show the user account that the DHCP Server service uses for DNS registrations, use the following command:
netsh dhcp server show dnscredentials

When I show the credentials it is blank since I have deleted it using the delete dnscredentials dhcpfullforce

In reading down the ms support page it says:

How to Configure the DHCP Server Service to Impersonate an Account

* DHCP Server service starts and an impersonation account is configured.
If impersonation is successful, the impersonation account is used for all further DNS registrations. If impersonation is unsuccessful, the DHCP server logs the following Event ID in the System Event log and does not perform any DNS registrations (ignores DHCP Option 81):
Event Type: Error
Event Source: DHCP server name
Event Category: None
Event ID: 1002
Date: 5/31/2000
Time: 3:21:47 PM
User: N/A
Computer: computer name
Description: The DHCP service failed to initialize its global parameters.
The following error occurred: Logon failure: unknown user name or bad password.
Data: 0000: 2e 05 00 00
* DHCP Server service starts and impersonation account is not configured.

If the DHCP Server service is not running on a DC, the DHCP Server service uses local computer credentials to perform secure Dynamic DNS update. If the DHCP Server service is running on a DC, the service logs the following Event ID in the System Event log and the DHCP Server Service uses local computer credentials to perform secure DDNS update:
Event Type: Warning
Event Source: DHCP server name
Event Category: None
Event ID: 1002
Date: 5/31/2000
Time: 3:57:13 PM
User: N/A
Computer: computer name
Description: The DHCP service failed to initialize its global parameters. The following error occurred: %%0
Data: 0000: 00 00 00 00

But I do not see any of this in the logs, thus I assume that I must do something in addition or readd the account back assuming the commands are in the wrong order or is the dns credentials for dhcp now supposed to be blank?

Our Group Policy work started with Small Business Server in 2000. Microsoft gave us an excellent OU and GPO model in subsequent SBS editions that utilized WMI filters, OU linking, and VBS scripts. These are some of experiences plus our spending a lo…

This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller.
Log onto the new domain controller with a user account t…