We help IT Professionals succeed at work.

Network problems resolving names across domain

Medium Priority
Last Modified: 2013-12-05
We have a problem from our main office to remote offices.  We have one dc at the main office and another dc at one other remote office.  All of this just occurred recently.  Also, we have been upgrading the firm on all of our switches but I'm not sure if it's related or not.

From the main office dc, we cannot map to shares on the remote servers.  We can ping by name and ip.  Dcdiag, gpresult both pass from both dcs.

We have to map the users at the remote offices using IP addresses.  All users are able to login and get all email from the exchange server located at the main office.  However, it's not letting them change their passwords.

We tried demoting the dc at the main office and got a "Network Path not found" error message.

The main office dc Appl Event log is showing the following error:  Source Userenv, Event ID 1000, "The Group Policy client-side extension Scripts was passed flags (17) and returned a failure status code of (1231)."

We have checked and tested DNS.  We are not exacting sure what is going on and appreciate any suggestions.
Watch Question

Chris DentPowerShell Developer
Top Expert 2010



Presumably all clients and servers on your network only refer to the internal DNS services in TCP/IP configuration? It's a basic question, but an important one.

If that doesn't get us anywhere, can you have a look at:

nslookup yourdomainname.com

I'd expect to see a response that includes the IP addresses for the domain controllers and nothing else.



Yes, all we have only refer to internal DNS and nslook did show just the dc's.  

Does replication work between the two DC's? I am asking because i suspect a connection issue between the two DC's. try to use the SUpport Tools , replmon tool to run the replication manually. Then check the error.

If the replication fails. you could be facing a issue with the connection
We found the problem, but I am not sure why it happened. I went into services on the 2 dc's that weren't acting right and found the TCP\IP NetBios Helper service stopped. The setting was on manual. I started the service and was able to get at group policy, map to another subnet, all the good stuff I couldn't. The working dc was set the same way, but its service was still started. I do not know why it was stopped. I rebooted one dc when still set to manual, and the problem returned. I now have them set to auto. Since all the settings I have seen for this service are on manual, any clues as to why mine are not starting?

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.