DNS, AD, DC issues at remote sites

We have four subnets on our network:

192.9.100.x (Main)
192.168.4.x (Remote)
192.168.6.x (Remote)
192.168.8.x (Remote)

At those three locations DNS doesn't seem to propagate.  Also, domain controllers can't be contacted other than initial log in.  For example, I'm trying to share a user's printer so others in that office can print to it but it doesn't "see" any of the other users.  In the network mmc I should see ALL machines on network.  I only see the ones on that specific subnet.  What could be causing this.  Everything works as it should on the main subnet.
Josh HindSystems AdminAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Amanda O'ConnorIT ManagerCommented:
What networking equipment exists between main site and remote sites? Can you ping the 192.9.100.x network from remote locations?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Josh HindSystems AdminAuthor Commented:
There is some proprietary equipment from TW that handles the circuits.  One router and switch per location.  Yes, 192.9.100.x can be pinged from remote locations.
Amanda O'ConnorIT ManagerCommented:
Ok, so I'm not sure if this will help... but, we have a main site, and 6 remote locations each on it's own subnet. We have a firewall at each site that we direct the traffic to our Primary Domain Controller for DNS. I wonder if the TW equipment or your router is configured to direct the traffic.. or can you figure out where it's looking to for the DNS services... if anywhere.
Josh HindSystems AdminAuthor Commented:
Yea the traffic isn't being passed to those remote sides.  I guess I can ask TW if they know anything about this.  We can't be the only ones having this problem.

Another thing, we have to add these machines to our domain at our main office.  If we try at the remote offices it says a DC can't be reached.  But it allows users to authenticate because they sign in every morning obviously.
Amanda O'ConnorIT ManagerCommented:
The credentials are cached, so the aren't technically authenticating. Your sites aren't getting DNS information because it can't contact the DC. TW maybe able to alter the equipment for that routing, or you may need to put in a firewall or equivalent equipment to direct traffic to main site for DNS.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.