23 Apr 2011 @ 2:54 PM
I’ve found some errors on the event log of a cluster node.
The error said : “A Kerberos Error Message was received” and in the description field was the following: ”on logon session”.
The error said : “A Kerberos Error Message was received” and in the description field was the following: ”on logon session”.
When searching the internet you will probably find many possible causes and solutions. In my case, the following worked.
Solution 1:
The time on the cluster nodes was out-of-sync.
To verify this, execute the following command on all nodes and compare the output:
w32tm /stripchart /computer:timesource1 /dataonly
If there is a difference between the outputs, then execute this command on all nodes to re-synchronize the time:
w32tm /resync /computer:timesource1 /rediscover
Although this solved most errors, it did not solve all.
After some investigation I found that the following solution solved them.
After some investigation I found that the following solution solved them.
Solution 2:
Set the following registry entry:
Set the following registry entry:
Key: HKLM\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters
Registry Value: LogLevel
Value Type: REG_DWORD
Value Data: 0
Registry Value: LogLevel
Value Type: REG_DWORD
Value Data: 0
Note: Changing the value from “1” to “0” will disable the kerberos logging.
04 Apr 2011 @ 11:50 AM
We experienced the following error on a server: “The session setup for computer DBSERVER1 failed because the security database does not contain a trust account “DBSERVER1” referenced by the specified computer”.
And now howto solve this.
And now howto solve this.
Solution 1:
Goto Active Directory Users and Computers and delete the device account and re-add it again. After that, goto the device and change its domain membership to a workgroup membership. Next, reboot the device and re-join the domain.
Goto Active Directory Users and Computers and delete the device account and re-add it again. After that, goto the device and change its domain membership to a workgroup membership. Next, reboot the device and re-join the domain.
Solutions 2:
On a domain controller, use the following command to reset the computer account:
NETDOM.exe RESET DBSERVER1 /domain:Contoso /UserO:Administrator /PasswordO:*
On a domain controller, use the following command to reset the computer account:
NETDOM.exe RESET DBSERVER1 /domain:Contoso /UserO:Administrator /PasswordO:*
Previous Entries
Categories
Tag Cloud
Blog RSS
Comments RSS
Last 50 Posts
Back
Void 
Life 
Earth 
Wind 
Water 
Fire