dilbert1680
asked on
Network problems resolving names across domain
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.
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.
ASKER
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
If the replication fails. you could be facing a issue with the connection
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hey,
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.
Chris