please see my previous post for history of what the problem is and what suggestions were from August 2011...thanks update: over the weekend I patched all our servers to prevent recent Microsoft RDP security exploit restarted the servers today it happened again. dc would not respond correctly to outook client on xp pro pc. ran wire shark found same problem as before listed above further expansion of the packet that contained the error showed the following: unknown type: 0x0007 target item type: Client Time (0x0007) Target item length: 8 target item Content: ???? this was a conversation from pc to offending domain controller i did some research on techs having problems with outlook 2007 connecting to exchange 2003: found one talking about changing security settings on client to ntlm instead of negoiation --- did this no help same error ran day light savings fix on xp pro & restarted === no help same error started and stopped time service on xp pro pc and dc and checked event logs to verify == no help compared time on xp pro pc and dc == were off by seconds, which was basically the time it took me to refresh screen soooooo... since this continued on at least 12 to 24 pcs thru out the entire school district did the only thing I could find to make it work for my clients: demoted problem dc and removed completely from domain and destroyed it. not the real answer, but at least it allowed outlook to work. the last time this happened was when I started this threadBrian P Collins

Hi Could you Provide the previous link Cheers Zi Feng Zi Feng TechNet Community Support

Zi Feng, it is under the same title in the forum and under my name. I just started a new thread and added PART 2 to the name. I thought that would be better than rewriting everything that was previously posted from 8/2011. thanks for taking time to read this and offer some insight. BrianBrian P Collins

Brian, As I read the post, I understand that the issue was resolved after demoting the problem DC. Am not an AD expert, but if you would like to investiagte or have some more questions, I can have my friends from AD team look at it. If the issue has not resurfaced and no work is needed, let me know, so i can close this topic thread. Thanks Santhosh

Santosh, I would welcome any help with this. I am baffled why this happens and have not found any solution. Thanks for your time and willingness to assist. BrianBrian P Collins