Cannot log into domain

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • raaman rai
    New Member
    • Oct 2007
    • 114

    Cannot log into domain

    i configured active directory in my server (windows server 2003) and tried one of the client to log into the domain. But surprisingly i cannot log into the machine using the domain. I get the message "The system cannot log you now because the domain OFFICE is not available".

    Infact i was able to create users and assign to groups and then allow the client to join the domain. But still then i get this problem for which i dont have any ideas.

    So what does it mean? how should i make the domain available.
  • AmberJain
    Recognized Expert Contributor
    • Jan 2008
    • 922

    #2
    Originally posted by raaman rai
    i configured active directory in my server (windows server 2003) and tried one of the client to log into the domain. But surprisingly i cannot log into the machine using the domain. I get the message "The system cannot log you now because the domain OFFICE is not available".

    Infact i was able to create users and assign to groups and then allow the client to join the domain. But still then i get this problem for which i dont have any ideas.

    So what does it mean? how should i make the domain available.
    I Don't know much about this but this Microsoft's page may help you-->

    Microsoft HELP PAGE

    Even searching google will provide you with many of the links. Click link below for more information--->

    LINK
    _______________ _______________ _______________ _______________ _____
    HOPE THIS HELPS.......... ..

    ==============
    =AmbrNewlearner =
    ==============

    Comment

    • ry54770
      New Member
      • Jan 2008
      • 3

      #3
      how many clients are experiencing this problem?

      i have come across this issue before, i work with a very large network so sparatically i encounter this exact issue.

      the resolution usually involves simply removing the client from the domain then re-adding it. i know it is not the most technical solution but i have almost 95% success rate by using this option.

      hope the info helps...

      Comment

      • jg007
        Contributor
        • Mar 2008
        • 283

        #4
        there are so many questions it is pretty hard to diagnose somenthing like this with out looking at how your domain, dns and dhcp etc are all set up.

        can you log on locally and then ping the server by name by IP?

        when you connected the w/s to the domain how did you do it and did it give any errors at all, also do the w/s or server logs show any errors at any point?

        Comment

        Working...