1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Problem re-joining a WinXP computer to a Win2k Server domain

Discussion in 'Windows Server System' started by aperry, 2005/04/14.

Thread Status:
Not open for further replies.
  1. 2005/04/14
    aperry

    aperry Inactive Thread Starter

    Joined:
    2005/04/14
    Messages:
    1
    Likes Received:
    0
    I did a complete reinstall of XP Pro and tried to rejoin the domain and got the messege "A domain controller for the domain genisysnet could not be contacted. ". What do I need to do to fix this problem?

    Thanks,
    Anthony
     
  2. 2005/04/14
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Welcome to the forum. I split your post from the original thread since it will get better attention this way. With tech forums, it's almost always better to open a new thread for any new problem.

    Are you using DHCP for address assignment on the domain? If so, is the XP box getting an address assigned as it should?
     
    Newt,
    #2

  3. to hide this advert.

  4. 2005/04/14
    Scott Smith

    Scott Smith Inactive Alumni

    Joined:
    2002/01/12
    Messages:
    1,950
    Likes Received:
    4
    When you did the re-install did you name the computer the same this is was previously?
    That could be a problem..
     
  5. 2005/04/14
    Andyl

    Andyl Inactive

    Joined:
    2005/04/13
    Messages:
    5
    Likes Received:
    0
    it looks like an address problem. Can you ping the domain by using the domain name?
     
  6. 2005/04/15
    eannatone

    eannatone Inactive

    Joined:
    2004/12/16
    Messages:
    209
    Likes Received:
    1
    i had this porblem too, try to hard code the dns maybe. i forge6t what i did to fix it but it can be fixed, watch out for firewalls, windows, mcaffe, norton.
     
  7. 2005/04/22
    swandog30

    swandog30 Inactive

    Joined:
    2005/04/19
    Messages:
    3
    Likes Received:
    0
    We have had this type of problem as well. Turned out to be that for whatever reason the DNS information wasnt being saved correctly. For example, we have two DNS servers listed, with the first hosting the records for our AD domain, and everything else coming from the second. XP was trying to do a lookup for the AD domain records from the second DNS and not the first, which led to the cannot connect errors.

    What fixed it was simply removing the first DNS server, closing network properties, going back in and re-add the DNS server back to the top of the list. Then everything was fine. Must force it to rewrite the DNS information, but just correctly. Its a weird one.
     
  8. 2005/04/27
    Unitas99007

    Unitas99007 Inactive

    Joined:
    2005/04/27
    Messages:
    3
    Likes Received:
    0
    I have had this problem before as well. Sometimes if you do a reinstall of the OS on a box, and delete the previously named entry in Active directory, it won't let you log into the domain because the AD thinks its the same box. Try logging in as local admin, setting the box to some workgroup that doesnt exist, then rejoin the domain. Also check AD to see if it is in the right OU.
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.