"The Network Path Was Not Found" (joining domain)

Discussion in 'Windows Server' started by hozzie, Jul 3, 2009.

  1. hozzie

    hozzie Guest

    I recently had to complete a dcpromo /forceremoval for one of our remote
    sites local Domain Controller.

    At the same time I completed a metadata cleanup for that server. Both
    completed successfully.

    I'm now trying to re-join the machine to the domain, but constantly receive
    error message "The Network Path Was Not Found". As it stands, the machine is
    stuck in a workgroup.

    All DNS settings are correct. I've changed the server name and also made a
    number of changes, but still experience the problem.

    No messages are logged in event viewer.

    Has anyone else came across this issue? I'm thinking the best option would
    be to backup the data and re-build the machine completely.

    Any ideas on how this could be resolved.

    Many Thanks
    hozzie, Jul 3, 2009
    1. Advertisements

  2. Hello hozzie,

    Did you also cleanup all DNS zones from the old one and AD sites and services?
    Please post an unedited ipconfig /all from the new installed machine and
    a running DC/DNS server. Is the exisitng DC also GC and having all the FSMO

    Best regards

    Meinolf Weber
    Meinolf Weber [MVP-DS], Jul 3, 2009
    1. Advertisements

  3. hozzie

    hozzie Guest

    Many thanks for your response.

    Yes, I removed all DNS entries relating to the old server and also AD sites
    and services.

    Problem server has not yet been re-built - only forcefully removed AD and
    now in workgroup. DNS was also removed.

    Server had been running, but unfortunately was disconnected from network for
    3 months due to organisation trying to find a new office and no permanent
    internet. I know it's ridiculous and not ideal, but they work on an island
    and are very small. Replication issues and tombstoned period meant I needed
    to force removal and cleanup.

    There's 40 + DCs and most GCs for specific sites across country. The
    problem server was mainly DC and GC, with local filestore.

    I've completed metadata cleanup in the past, but in those cases it was a new
    server build.

    I'm also using a different server name.

    I'll post IPCONFIG later from work.
    hozzie, Jul 4, 2009
  4. hozzie

    hozzie Guest

    I'm a little reluctant to post ipconfig on web.

    The primary DNS suffix and DNS suffix search list are correct, as well as
    DNS servers and WINS.

    I can ping the FQDN and receive a response from domain controller. I can
    also ping the host name of several domain controllers.

    However, when I attempt to connect to shares on server using \\servername i
    receive the following error message:

    "No network provider accepted the given network path"

    The computer browser and workstation services.

    This is obviously linked to the reasons behind "the network path not found"
    when connecting machine to domain.

    I'm thinking the best option is to backup data and rebuild the server from
    hozzie, Jul 6, 2009
  5. Hello hozzie,

    hopefully you use the private ip ranges 10.x.x.x 172.x.x.x or 192.168.x.x,
    this ones are NOT accessible from the internet so you can post them without
    any problem. For server names and domain names, change them, but keep the
    same format like myserver.mydomain.com or mydomain.com or mydomain.

    Best regards

    Meinolf Weber
    Meinolf Weber [MVP-DS], Jul 6, 2009
  6. hozzie

    hozzie Guest

    Yes, we use the 10.X range.

    hozzie, Jul 6, 2009
  7. If you are using private IP ranges, you can safely post ipconfig information in a public forum. Feel free to change the internal domain name, but keep the format of the domain name, such as if your domain name is 'example.net,' you can change it to 'domain.net' in order to mask your actual domain name for security.

    Usually when we ask for configuration information for multiple DCs, it is to help us understand AD's infrastructure configuration in relation to the DNS entries in the config, if it is the server itself as a DNS server, the loopback, if an ISP's is set, if the router is set as a DNS address, search suffixes, Primary DNS suffixes, whether NetBIOS is enabled, multihoming, single label names, and much more. You would be surprised about the slew of information a simple ipconfig /all provides us in the diagnostic process.


    This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

    Please reply back to the newsgroup/forum to benefit from collaboration among responding engineers, as well as to help others benefit from your resolution.

    Ace Fekay, MCT, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging
    Microsoft Certified Trainer


    For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
    Ace Fekay [Microsoft Certified Trainer], Jul 6, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.