Question about Microsoft Windows Server Standard 2003 for PC

5 Answers

Windows cannot connect domain either domain controller is down or otherwise unavailable or because your computer was not found

Posted by on

  • Anonymous Mar 24, 2009

    when i try to log on my computer i get that message" windows cannot connect domain either domain controller is down or"

×

5 Answers

  • Level 1:

    An expert who has achieved level 1.

    Governor:

    An expert whose answer got voted for 20 times.

    Corporal:

    An expert that has over 10 points.

    Mayor:

    An expert whose answer got voted for 2 times.

  • Contributor
  • 9 Answers

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.

Posted on Jan 16, 2009

  • sanjay kumar jha Jan 17, 2011

    thanks sir
    its working .
    now i can login on my computer by using server account.
    thanks

×

  • Level 1:

    An expert who has achieved level 1.

    Mayor:

    An expert whose answer got voted for 2 times.

  • Contributor
  • 1 Answer

Try to ping DC Computer ip, if it ping then restart your Computer and try Again
if it does not ping then check with Internal Settings

Posted on Dec 18, 2008

  • Level 3:

    An expert who has achieved level 3 by getting 1000 points

    MVP:

    An expert that got 5 achievements.

    Master:

    An expert who has achieved Level 3.

    Sergeant:

    An expert that has over 500 points.

  • Microsoft Master
  • 158 Answers

This is usually becauseof the DNS configuration at the client computer.

Posted on Mar 12, 2015

  • Level 1:

    An expert who has achieved level 1.

  • Contributor
  • 1 Answer

Sometimes, after extended periods of time when a computer which is a member of an Active Directory domain was taken offline and then brought online, or when some sort of cloning or imaging method or even a virtualization software snapshot mechanism was used on a domain member, you may get an error similar to this
http://www.techyv.com/questions/domain-computers

Posted on Feb 23, 2013

  • Level 1:

    An expert who has achieved level 1.

  • Contributor
  • 1 Answer

Sanjay Limbu's solution worked for me. In active directory, under computers... the computer name was disabled and had a big red X on it. Right click and enable this computer... bam, the user could log back in. You do not have to remove the PC from the domain or the user from the active directory list.

Posted on Feb 01, 2012

1 Suggested Answer

  • 10 Answers

SOURCE: I am unable to login our domain user account.

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.

Posted on Jan 28, 2009

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

Thank you for the last one. know i want to set up mu 3laptops on the windows server 2008 r2 standered and use the server as a domain and the laptops as well like a domain.


first you need to setup the roles in the server, go to the manage server console, ( can be found as a shortcut in the taskbar or under start menu ) then open the console and go to add roles.

1 - add active directory

2 - in the process it will ask you to install the DNS server role ( do it )

3 - after installing the role in the CMD command prompt type DCPROMO

4 - the DC controller installation and setup will beging ( do not do anything during this proccess )

5 - when asked by DC setup to choose what type of domain functionality level do the following

1 - windows 2003 ( this is for compatibility for windows server running 2003 and XP machines )

2 - Windows Server 2008 ( at this point nothing lower than XP can be added to the DC of course domain functionalities will increase - Only other 2008 server domain controller can be added and cluster migration from server 2003 to 2008 is not supported. )

3 - Windows Server 2008 R2 ( at this point only machines running Vista and 7 can be added to domain - windows xp is no longer supported. All the functionalities of the domain controller are available)

keep in mind once you promote the domain controller to a higher level it can't be brouht to a lower level.

once active directory is installed restart you server and the you should be able to add the clients pc or laptos to the DC example

- right click over my computer icon
- click on properties
- computer name
- change the computer from workgroup to domain
- type your FQDN ( fully qualified domain name) example: mynetwork.local or mysite.com
- apply changes and restart
- your computer will be part of the domain next time system boots up.

Mar 01, 2011 | Operating Systems

2 Answers

Cause of user profile not loading


The question is:

What causes a user profile not to be loaded in Windows domain based network?

the answer is:
there are probably 3 broad reasons for this,
1. the user corrupted their profile somehow, such as shutting down without logging off (hard power off)
2. the connection to the domain was lost ungracefully, and offline information was not copied entirely, causing a mismatch of some encrypted profile data, (effectingly corrupting again) and preventing the logon.
3. an unknown event took place between the last time the user sucessfully logged on, and this time where the profile is now not loading. this could be hardware related (faulty Hard disk), RAM parity errors( bad memory), a change to the user profile SID details on the domain controller or other domain change.

Usually the cause is not so much a problem, unless it consistantly reoccurs.

Fixing it however, in XP is fairly easy.
with an account with domain admin rights, just navigate to the UNC path "\\computername\c$\documents and settings" - note the name of the folder/user affected, and just .old their profile folder.
example, username is Philip. - you see in their c:\documents and settings\ folder the folder called Philip, rename it to philip.old or something else.

You have to ensure this is done while the user is logged off, as files in this folder will be in use otherwise. potentially useful to reboot the computer before navigating to the profile folder.

Jul 11, 2010 | Microsoft Windows XP Professional

1 Answer

Client login problem.


it is because you have been infected by viruses,....try to sacan you pc with effective anti-virus..

Feb 06, 2010 | Microsoft Windows Server Standard 2003 for...

1 Answer

Domain controller is down or otherwise unavailable.


Hiii

Ok after assiging a workgroup to the domain, plz make sure u gpupdate ur system , certain times it does take 60mins for changes to take effect.

Regards.

Sep 08, 2009 | Microsoft Windows Server Standard 2003 for...

4 Answers

I dont know what is domain


A Microsoft Windows Active Directory Domain is a directory service for a computer network. Think of it like a phonebook for all your companies computers, users, and printers to name a few. Active Directory provides a central authentication point for all users/computers in the building and controls network policies. This makes network management for multiple computers and users MUCH easier.

For more information, see Microsoft's Official Active Directory site.

Mar 07, 2009 | Microsoft Windows Server Standard 2003 for...

1 Answer

I am unable to login our domain user account.


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.

Jan 28, 2009 | Microsoft Windows Server Standard 2003 for...

1 Answer

Active directory


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.

Jul 09, 2008 | Microsoft Windows Server Standard 2003 for...

Not finding what you are looking for?
Microsoft Windows Server Standard 2003 for PC Logo

39,971 people viewed this question

Ask a Question

Usually answered in minutes!

Top Microsoft Operating Systems Experts

Brian Sullivan
Brian Sullivan

Level 3 Expert

27725 Answers

Scott Fryer

Level 2 Expert

80 Answers

Alex Krenvalk

Level 2 Expert

401 Answers

Are you a Microsoft Operating System Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...