Hello,
For a few weeks now we have been stuck on a problem with kerberos errors randomly showing up on boot up of our Windows 7 clients. We have concluded that these random errors show up far more often on wireless notebooks, and for some reason more often on some than on others.
I have done wireshark captures of a notebook when it is working and when it is not working.
As you can see, in the top image (you will have to zoom in on the page in your browser), when it is working it shows that it connects with no kerberos error and it connects to the dns name of the server, in this case DC1.domain.ca and downloads the policy.
When it is not working it will give the kerberos error, and then try to connect to the hostname of the server \\dc1\ipc$ and it will fail to read the group policy.
I have done a lot of research and I know about resetting the domain controller computer account, checking the SPN's, and verifying that the the secure trust rerelationships good between the servers, checking for duplicate DNS entries, etc.
The problem I have is why is it so random. All of the posts online talk about these problems and the solutions, but they never mention that it is completely random. I can reboot this laptop 5 times and it will work perfect, but then it won't work 3 times in a row, then it goes back to working again.
Am I completely off track in trying to fix errors on the DC's and I should be looking at a hardware issue or a driver problem on the client side?
One other note is that when you get a kerberos error on boot up, if you wait up to 30 seconds, the client will try the connection again and it will succeed with the connection just as it is in the working one. This is great, but most users have already tried logging in within 30 seconds and the GP's have then already failed.
Thanks,
Dan.