Can't connect to domain

Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or, because your computer account was not found. Please try again later. If this message contines to appear, contact your system administrator for assistance.

Check the network connection and ping the Domain Controller. If both of those are working, Log on as a local administrator, remove the computer from the domain and change the computer name. Restart, then re-add to the domain.

This is usually a DNS issue. Log on as a local administrator, check the network settings, make sure that the SBS server is also the only DNS server (static if need be, but preferrably given by DHCP) and you should see this issue resolve.

If the problem was caused because of incorrect information given by a DHCP server, update the DHCP scope information to give out proper info.

get the PCs name from the logon screen (click the drop down box next to 'log on to' and ping it from the server.
if no response its a network connection error
If it works Id check active directory and locate the computer's account to check it isnt disabled or deleted.

you may need to get the local admin password so you can readd it to the domain.

Generally when a computer cannot join the domain using http://connect (SBS 2008 & 2011) or http://SBSname/connectcomputer (SBS 2003) it is due to inability to correctly resolve the name of the domain controller in a timely fashion. Below is a list of common reasons for the connect wizards to fail. In an SBS domain the server should be the DHCP server, and if so, items 2 and 3 below should be automatically set through DHCP. However if addressing is statically assigned or you are using a router you may need to make changes. Items 2 and 3 are also basic networking requirements of a Windows Domain, not just important for joining the domain.

1. If there is more than 1 network adapter installed , wired or wireless, disable all but 1, preferably wired, until after joined to the domain
2. Make sure, using IPconfig /all, that the client's DNS points ONLY to your internal DNS servers, in this case the SBS. Do not allow a router or ISP to be added as an alternate.
3. IPconfig /all should also show next to “Connection-specific DNS Suffix” your internal domain suffix (MyDomain.local). If not you need to add the domain suffix to the client machine. To do so insert it in the "DNS suffix for this connection" box under the DNS tab of the NIC's advanced TCP/IP IPv4 properties
4. If there are any 3rd party firewalls or security suites installed, disable them until joined to the domain
5. If still failing add the connect web site to the “trusted” sites list in Internet Explorer under Internet options / security
6. On a few occasions Bluetooth accessories such as keyboards and mice have been known to interfere with the connect wizards. If necessary temporarily replace these with wired devices until domain joined.

My point about the SP and reinstalling is 3 hours later it's working (assuming an average operating system rebuild is around this time, if you have a known good image far less time) and I'm including adding applications back. Just a thought, a part of troubleshooting is knowing the time constraints spending endless hours trying to find the problem. I respect you trying to find a solution but time is of an essence as well. Just my thoughts. If you want to eliminate the NIC throw a card in the PCI real quick, will take 10 minutes. The reason I don't see it being DNS is because you mentioned other computers are not affected, it appears to be an isolated incident in my opinion.

It sounds like a DNS issue. When the network is available it tries to contact the DC but cannot.
My notes were referencing not being able to join the domain. Sorry I assumed that with the title "cannot connect to the domain". However #'s 2, 3, & 4 still apply.

Meet the world's only “Transparent Cloud™” from Superb Internet Corporation. Now, you can experience firsthand a cloud platform that consistently outperforms Amazon Web Services (AWS), IBM’s Softlayer, and Microsoft’s Azure when it comes to CPU and …

If you're not part of the solution, you're part of the problem.
Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet. Use PRTG Network Monitor as one of the building blocks, to detect unusual…

Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail. The methods are covered in more detail in o…

This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg).
If you're looking for how to monitor bandwidth using netflow or packet s…