We have dot1x on all the of our Xp computers (SP 3)I have several computers that seems to have problem logging into the domain every morning when it boots up. It will say "Domain not available". However, if we let the computer sit for about 5 minutes the user will eventually log in.We don't know what the exact cause is, been trying all the different solutions. Anyone got any idea?

Examine the event logs to be sure, but I think has to do with the order that services get loaded.Tcpip, dns client, rpc, netlogon and several other drivers and services have to be up and running before users can authenticate over the network. Take a look athttp://support.microsoft.com/kb/193888to find out how to delay loading specific services.Also, there are several Group Policy settings that affect this process. One that comes to mind has to do with whether domain computers will cache logons, but there are other settings. Cached logons allow users to logon to the computer by relying on the authentication of their previous logon.If it appears to be a Group Policy issue, the Group Policy Forum might be a better place to pose the question.Good Luck

I can try that out. Does anyone know the Windows logon process with 802.1x enabled? (for a computer that's on the domain)

Um... Seems like it's still having some issues... Other suggestions or does anyone else experience the same problem?

Hi, Since IEEE 802.1X wired client must perform an authentication prior to being able to use its switch port, I suspect that the authentication had not been completed while you tried to logon the system. Therefore, you encountered the error "Domain not available". Here are some more information about IEEE 802.1x: IEEE 802.1X Wired Authentication http://technet.microsoft.com/en-us/magazine/cc194418.aspx Troubleshooting Windows Vista Secure 802.3 Wired Connections http://technet.microsoft.com/en-us/library/cc749352.aspx#BKMK_Sectn3_Wird For further assistance, I suggest that you post it in the Networking related forum or Windows XP SP3 forum. The support professionals there are more experienced and better resource for this kind of issues. Windows XP Service Pack 3 (SP3) http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=2010&SiteID=17 Platform Networking http://social.technet.microsoft.com/Forums/en-US/winserverPN/threads/ Hope the information is helpful.

Found out there's a 1200 block out timer. in event log id Network authentication attempts have been temporarily suspended on this network adapter. Network Adapter: Broadcom NetXtreme 57xx Gigabit Controller - Packet Scheduler Miniport Interface GUID: 9219d220-ec6f-4380-8cdd-ea711fa843bf Reason Code: 327685 Length of block timer (seconds): 1200 How do I shorten the timer?Thanks!Thomson.

Hi, For the Networking-related question, please post it in the Networking forum. The Networking guys are better resource for assistance. Thank you for your understanding.