Right, drastic… but according to
your error log the one machine is dated in 10/28/05 while the other is more
current 4/11/06. This is the only reason I suggested it. I
had a DC get a power spike 2 weekends ago (silly surge / battery backup’s
didn’t help) and it blew the BIOs so when it rebooted it was in 04. This
stopped allowing the other sites and DC’s to authenticate to it. The only resolution I was able to find was
1 start over (more drastic then 2) or 2 netdom. Once netdom was ran, everything was happy again. Just my 0010 bits From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Kern Time is correct on both DC's. I don't think I should reset the password on a DC? That seems a little drastic... Thanks On 4/24/06, Active
Directory <[EMAIL PROTECTED]>
wrote: Try resetting the machine account password using NETDOM it
must be run from the local machine can't be done remotely. Make sure your date / time are correct on both servers. Looks
like PDCFSMO is not set to the correct date. This causes issues with Kerb
authentication. HTH,
CONFIDENTIALITY NOTICE: The information contained in this message, and in any
attached files, may constitute confidential information which belongs only to
the person to whom it is addressed. This information is intended only for the
use of the individual or entity in which it was sent. If you are not the
intended recipient of this information, you are hereby notified that any disclosure,
copying, distribution, or taking of any action in reliance on this information
is strictly prohibited. If you have received this email in error, please
immediately notify us at the number listed above and permanently delete this
message. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Tom Kern I keep
getting this error logged in the system log of my PDC FSMO- The
source server casuing the issue is another DC in the same domain(Win2k3 FFL) Event
Type: Warning For more
information, see Help and This is
the error logged on the offending Event
Type: Warning The
failure code from authentication protocol Kerberos was "The attempted
logon is invalid. This is
either due to a bad username or authentication information. For more
information, see Help and http://go.microsoft.com/fwlink/events.asp
. I checked
Eventid but nothing really applies. Does
anyone know what the issue could be? Thanks
|
- RE: [ActiveDir] Lsasrv error Active Directory
- Re: [ActiveDir] Lsasrv error Tom Kern