Window cannot connect to domain either because domain is down or

It is really works. More ways and tips you will find in passage about Windows server password reset ways and tips.

Hello,

Windows home versions of the operating system can not connect to domain servers, you have to be running the Windows 7 pro to connect to a domain controller. The modules from Windows 7 are not included in the home version of the software.

As it is not specified here that you are facing problem with Windows login password or domain password so, I request you to share about it too. According to me if you are trying to connect (or already connected) your laptop to any network then you need domain username and password. You can get it from the network administrator. On the other hand if you are facing problem with windows login password then you can reset it by using Windows password recovery software or by some other tricks (I can tell you if you are interested).

Forgot Windows XP password? check out this solution, Windows XP Password Reset.

even if you mistakenly joined a domain you can still log in through your existing id and password.
Once your press CTRL+ALT+DEL, you will see a login window with three fields namely: user id, password and Domain.
In the log in screen use the drop-down menu in front of Domain (which shows your new domain- most likey MSHome) and choose 'this computer'. After this, enter your old/existing user id and password and hit enter.
Please proceed to your system settings and change your domain back to Workgroup. Restart PC.

Yes, all Windows Servers have the option to install DNS.

Set up a second Windows server and configure it to be a secondary server for your DNS domains on you current server.

Add the second DNS server's IP address to the secondary DNS field to your DHCP scope options and to all computers with static IP configuration so they will use it when your primary DNS is unavailable.

Don't underestimate Window's built-in Help and Support. It will help you install DNS and configure it.

Good luck.

Hello,

This is usually a computer trust issue, if the computer was previously used to logon to the network and has been rebuilt or had in problems it can have trust issues. First way would be to change the computer name and add the DNS Prefix for your domain. ex desktop.abc.com to desktop1.abc.com. when prompted it is best to use the domain admin or equivalent to make the change and then reboot.

First reboot once your PC and if that does not work then:
when you login with your local admin account are you able to ping the DC? Also, check the IP settings to make sure they are correct. Are you using DHCP or are you static? If you are able to ping the DC adn IP settings are correct, is the computer name in Active directory? Also if the computer name is in active directory, is it disabled? If you check all these things and you are still having issues, drop the computer from the domain, rename it and create the new name in Active Directory and then add the computer back to the Domain. Somewhere along the line of following these steps, you should get the computer back inline. If other computers are able to connect to the domain then it is definitly an issue with this computer name or a setting on this computer.

Thanks
Note: do not forget to rate the answer.

The resolution and workaround to solve the error is as below.

1. Login to the Windows 2003 domain controller, and delete the computer account object from the Active Directory by using Microsoft Management Console (MMC) which you can always access from “Manage Your Server”.
2. Log-in to the PC workstation as local administrator. If you cannot logon as local administrator, try to unplug the network cable and logon to the computer by using a domain administrator user that used to logon on the PC before, by using cached logon credentials feature.
3. Go to Control Panel, then click on System icon, then go to Computer Name tab.
4. Unjoin the computer from the domain by clicking on “Change”. You should see that Domain button is now selected. Remember your domain name in the text box. Select (Click) on “Workgroup” to remove the computer from the domain, and put any workgroup name in the text box (e.g. workgroup).
5. Click OK to exit.
6. Restart the computer (optional)
7. Go back to the Control Panel, launch System properties and then go to Computer Name tab, and click on “Change”.
8. Rejoin the domain by uncheck the Workgroup button and select (check) Domain button, and put in the domain name noted above into the text box.
9. Click OK to exit.
10. Reboot the PC.

This should solve the unable to logon to domain error, without changing or losing the user profiles on AD.

An application directory partition is represented by a domainDNS object with an instanceType attribute value of DS_INSTANCETYPE_IS_NC_HEAD combined with DS_INSTANCETYPE_NC_IS_WRITEABLE. This domainDNS object represents the application directory partition root (NC head), and is named similar to a regular domain partition, for example, "DC=dynamicdata,DC=fabrikam,DC=com", which corresponds to a DNS name of "dynamicdata.fabrikam.com". An application directory partition can, therefore, be instantiated anywhere a domain partition can be instantiated. There is no NetBIOS name associated with an application directory partition.

It is possible to nest application directory partitions, that is, an application directory partition can have child application directory partitions. Searches with subtree scope rooted at an application directory partition head will generate continuation references to the child application directory partitions.

An application directory partition replica can only be created on a domain controller that is running on Windows Server 2003 and later and only while the Domain-Naming FSMO role is held by a Windows Server 2003 and later domain controller. In a mixed forest that has both Windows Server 2003 domain controllers and down-level domain controllers (Windows 2000 domain controllers or Windows NT 4.0 primary domain controllers), an attempt to create an application directory partition replica on a down-level domain controller will fail.

An application directory partition also has a corresponding crossRef object in the Partitions container of the configuration partition. The crossRef can be pre-created manually before creating the domainDNS object. The pre-created crossRef object must have the attribute values shown in the following table or the partition creation will fail. If the crossRef object does not exist, the Active Directory server will create one when the application directory partition is created.