Thanks in advance for any comments or assistance provided.
We recently added a new facility. The subnet of our primary facility is 192.168.0.0/22. This new facility is 192.168.4.0/22. This new facility is actually a relocation of a facility which had a subnet of 192.168.8.0/22. We did not have any issues between 0.0/22 and 8.0/22, but we are experiencing issues between 0.0/22 and 4.0/22. Here are a few scenarios that detail the issues we face:
1. Users from 4.0/22 connect through RDP to terminal servers at 0.0/22. The terminal sessions frequently disconnect for a split second then immediately re-establish connection.
2. Users from 4.0/22 have an Exchange mailbox located at 4.0/22. If they are laptop users and travel to the 0.0/22 facility (15 miles apart), Outlook will not establish connection to their mailbox without first pinging the mail server located at 4.0/22.
3. As an admin, I frequently use RDP to connect with servers located across facilities. I am mostly based at 0.0/22 and cannot use RDP to connect to a server located at 4.0/22 without pinging that server first.
There are a couple of other issues, but I anticipate resolution of these issues will result in resolution of others.
We are a Microsoft shop, so we use Windows Server 2003 and Microsoft Active Directory as our backbone. We have asked our ISP to confirm that all routes are configured appropriately and they have confirmed. We have also asked them to test connectivity between facilities (we have an MPLS setup) and they have again confirmed that there are no issues.
We have domain controllers located at each location, and we have internal DNS and DHCP servers. Replication does not appear to be an issue at this time.
If I've left out any pertinent information, please let me know and I'll be sure to supply it.
I'm at my wits end with this and I'm not sure where to go from here. Thoughts? Suggestions? Drinks?