So here is the dilemma, which i honestly have been on for the past month, and can't seem to track down the issue. It hasn't been just me either, there was a support case from Microsoft created, and they can't seem to figure this out either, so if i get no replies here i understand why. (open to suggestions)
The issue is that the Domain logon server itself is disappearing, which in a high load environment i would understand and think this is likely an issue with over utilization.. The environment here is 34 people, and at any given time there is only 20 - 25 in the office. But, for whatever reason, i am getting clients disconnecting from the domain controller. I had created a Domain policy to try to force the systems to wait for the network, thinking this would at minimal point out if this is a network issue, or a server issue.. But the Policy setting doesn't seem to make a difference.. (Wait for network and require domain controller to log into the PC)
The DC is a 2k8 server x64 running 64GB of DDR2 Registered memory
It has 2 8 core Xenon processors
It is a Raid6 with SSD's that do 6GBPS
The server is fully patched, all drivers NIC and all have been updated, there is no NIC teaming.
The server is rebooted 4 times a year, once every 3 months.
The network is a Gigabit network using Cat6 and Juniper hardware
There is no internal firewalls and the servers do not run an AV.
The Desktops are all windows 7 X64 and vary as to hardware, with the worst being Core2's and the best being I7's.
Memory varies from 4GB - 16GB
Hard disks are all at least 250Gb and SATA 7200RPM
All the windows 7 machines are updated weekly with WSUS
All the 7 machines have an AV installed, all the same, all have the Firewall turned off and network discovery turned on.
They were all clean builds never using ghost or any cloning.
I haven't been able to track down where the issue is coming from, has anyone else seen this issue?