The kerberos subsystem encountered a PAC verification failure

[Paul]

Hi,
I have 2 XP Pro computers (that I know of) on my Win2k
network that are coming up with the error in event log:

Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 7
Date: 9/12/2003
Time: 9:33:13 AM
User: N/A
Computer: S10700
Description:
The kerberos subsystem encountered a PAC verification
failure. This indicates that the PAC from the client
S10700$ in realm <my domain> had a PAC which failed to
verify or was modified. Contact your system
administrator.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 92 01 00 c0 ’..À


Does anyone know what this might mean, and how I can fix
it? As a result, these computers are now no longer
receiving Group Policies, which is quite an issue.

I Appreciate any help I can get...

Thanks.

 

[Roger Abell]

Are the machines all in time-sync to within 5 or fewer
minutes ?

--
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4) MCDBA
Hi,
I have 2 XP Pro computers (that I know of) on my Win2k
network that are coming up with the error in event log:

Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 7
Date: 9/12/2003
Time: 9:33:13 AM
User: N/A
Computer: S10700
Description:
The kerberos subsystem encountered a PAC verification
failure. This indicates that the PAC from the client
S10700$ in realm <my domain> had a PAC which failed to
verify or was modified. Contact your system
administrator.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 92 01 00 c0 ’..À


Does anyone know what this might mean, and how I can fix
it? As a result, these computers are now no longer
receiving Group Policies, which is quite an issue.

I Appreciate any help I can get...

Thanks.

 

[Paul]

Yes, All of the machines are synchronising their time
with one of our DC's. As a trial, I ran Sysprep on one
of the computers (and chose to regenerate SID's). I also
deleted, and then recreated the Computer account from
AD. After running Mini-setup and rejoining to the domain
etc, the problem has been solved.
I don't know that this is the best solution if this was
to happen to all of our computers though.
Although I have a workaround, any suggestions as to what
may have caused this would certainly be welcomed.

 

[IBTerry [MSFT]]

Hello,

Is this machine behind a firewall? I worked an issue similiar to this and
it was resolved by opening some firewall ports...
Or do you have any personal firewall type software directly on the machine?

IBTerry [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.