Pt 2 Pt T1 connectivity issues at secondary location with Active Directory/Network shares

We have 2 locations.  A and B.  They are connected via a Pt 2 Pt T1 line.  Half of that is voice, the second half  data.  I have approx 25 users at location B.  We are using Adtran Netvanta 3205's on each end.

Location A is running Windows 2000 server and has approx 60 users.  Location A houses the exchange server/domain controller.  Location A is on a 111.111.120.x IP config (DHCP).  Location B is on a 111.111.121.x IP schema (DHCP).  A secondary company on location B's network is still static so they can reach their server.

We are unable to see computers from location A when browsing my network places at location B.  Also, network shares don't always function properly and it almost seems as though active directory or some global policies always carry over to B either.  I also have some issues with bandwith or so it seems.  some users when trying to open an email with an attachment takes excessivly longer than it should.  Or just trying to access a network share takes longer than i would think it should.  

I was wondering if I need to add some lookup zones on the DNS server or if there was anything someone may know which could be causing my issues.  Adtran has reviewed the config and i am confident that they are correct.

I am actually about to roll out another Pt 2 Pt T1 between the 2 sites and plan on seperating the 2 companies.  the new pt 2 pt will be only data for one company.  the other company will use the 1/2 T and share with the voice.  I plan on putting the PC's on the new T as DHCP so I am just hoping someone has an idea what may be causing my issues.

Who is Participating?
I really don't think you've got a DNS issue, from the description.  With a single domain, you'll only have one lookup zone (forward and reverse, although reverse is not absolutely required).  And with a single DNS server, assuming your DNS is AD integrated, there's really nothing to configure.  If you add another DNS server as a secondary server for your zone, it will house the same zone info, but if you AD integrate that one as well, the zone info is populated automatically.

Having said that, it won't hurt to check the contents of you existing lookup zone(s).  If you've got machines missing, or incorrect addresses, you do have a problem, and will need to address that in addition to the network browsing issue. . .
First, browse lists like My Network Places are a NetBios function, and are broadcast dependant.  Unless you're intentionally forwarding broadcasts between your networks, that won't work.  

For general AD performance issues, if you've only got one domain controller, and it's at one end of the T1, that's most probably the cause of your issues.  Just about everything related to network shares, Group policies, and Exchange (2000 or later, at least, which I'm assuming in your case) depends on access to a domain controller to read the Active Directory.  If your T-1 is heavily loaded, that AD traffic will be a problem, both by contributing to the overall network load, which slows other things down, and by experiencing the delays, etc., which will cause all sorts of issues with about everything you mentioned. . . .

I'd probably recommend installing a second DC at your second site, so it can handle all of the directory access traffic for that site, which won't have to cross the T-1, then.  The server to server replication between the DC's ought to be less network intensive, and is definitely more delay resistant. . . .  And the cost of one additional server (at least one - I'd really recommend having two at your main site for redundancy) will be substantially less than the cost of an additional T-1.
akafitiAuthor Commented:
I understand what this says and I will attempt this in the near future.  besides adding a domain controller to the other location, do you think there is anything else I can do to help?  again, most things we are able to do.  just sometimes things decide not to work.  do i need to do anything with reverse or forward lookup zones?

The pt 2 pt T line is actually very inexpensive as the locations are literally 1/2 mile apart from each other.  and anticiapting additional traffic with images going back and forth as we attempt to go paperless.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.