Unable to join 2003 R2 Domain Controller

Home Forums Server Operating Systems Windows Server 2000 / 2003 / 2003 R2 Unable to join 2003 R2 Domain Controller

This topic contains 10 replies, has 7 voices, and was last updated by  scolombo 6 months ago.

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #167515

    Ping between DC and Computers are OK. But \192.168.0.** not working , \ComputerName working. what is the possible Reason.Also AD machines not showing in Entire Network section


    Ossian
    Moderator
    #191975

    Try joining the domain by FQDN (dc.domain.com) rather than just NetBIOS name


    biggles77
    Spectator
    #214403

    Try this.

    [ATTACH=JSON]{“data-align”:”none”,”data-size”:”medium”,”data-attachmentid”:516858}[/ATTACH]


    articwolf77
    Member
    #392006

    Already try this …but error is “Network Path Not found”. Please find the attached screenshot #4 post.


    biggles77
    Spectator
    #214405

    But did you add the domain suffix as per step 3 in my attached image? Post #4 gives no indication that you clicked the MORE button and added it. It only shows the Domain Name in the Computer Name/Domain Changes window.


    articwolf77
    Member
    #392007

    Yes Sir, Please see the full computer name section. After adding DNS suffix, Computer Name Changes to ComputerName.domain name.com. But Could not authenticate with domain.


    biggles77
    Spectator
    #214409

    Are you able to create a DC in a Virtual Machine using a new server operating system? Server 2003 R2 is now a very old operating system and is really past it’s use by date.

    Have a read of this thread, if you already haven’t, and see if you can resolve your issue with help from it. https://www.petri.com/forums/forum/microsoft-networking-services/active-directory/516638-computers-cannot-connect-to-my-domain-server-anymore


    articwolf77
    Member
    #392008

    It was not a virtual machine, suddenly it happens for last 2 weeks. Before that everything was ok..

    Blood
    Blood
    Moderator
    #337380
    asarbadhikari;n516871 wrote:
    Yes Sir, Please see the full computer name section. After adding DNS suffix, Computer Name Changes to ComputerName.domain name.com. But Could not authenticate with domain.

    Your image does not show what Biggles was asking about. The computer name does not include the domain name. Your image shows ‘stsite-103’ not ‘stsite-103.dataserver.geotechkol.com’


    scolombo
    Member
    #392040

    hello,

    I think you’ll find the key may lie here:

    [WARNING] The DNS entries for this DC are not registered correctly on DNS server ‘68.94.156.1’. Please wait for 30 minutes for DNS server replication.

    Is that your public ISP DNS server? If so, then this is the wrong DNS server to be using.

    There should be a DNS server somewhere in your AD (It’s usually on your Domain Controller if you only have one)
    The Domain Controller should have its DNS pointing to itself
    The client machines should have their DNS pointing to the IP address of your internal DNS server (e.g. your domain controller)
    Your ISP’s DNS server will not be used inside a normal AD network. UC BrowserSHAREitMX Player


    wullieb1
    Moderator
    #245768

    Please post an ipconfig /all from both the client and a DC

    Do you have DNS configured correctly?

    What changes were made 2 weeks ago to the system??

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.