Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Exchange Connection Issues


  • Please log in to reply
No replies to this topic

#1 wmcdon7160

wmcdon7160

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:05:21 PM

Posted 28 September 2007 - 05:51 PM

Office "A" and Office "B" are connected via Cisco PIX Firewalls.

Office "A" used to login to a domain in Office "B"

Office "B" also hosts the exchange server for Office "A"

Office "A" decided to get their own Domain Controller and now logs in to a local domain, but still requires access to the exchange server in Office "B"

Office "A" uses Windows XP Pro clients to connect to a local Server 2003 DC that has the following installed and configured: (with very little configuration beyond the default wizards):
-Active Directory
-DHCP
-DNS
-File Server
-Remote Access and Routing

When configuring Outlook 2003 on the clients in Office "A", it connects to the exchange server in Office "B" and resolves the name for the proper account just fine. (seems slow, but that may not be part of the issue)

The Exchange accounts in Office "A" are not using Cached mode

The clients in Office "A" only use the windows firewall

The problem is that when Office "A" opens Outlook, it is slow to completely open, then a message balloon pops up from the system tray that says, "Outlook is trying to retrieve data from the Microsoft Exchange Server: <Exchange server name>

The error message isn't regular, but it does pop up quite often.

Is there a setting that I'm missing on the server in Office "A" that is somehow restricting a wide open communication from Office "A" to Office "B"?

The problem didn't occur until I switched all the computers in Office "A" to the new local domain.

~Mod Edit: Topic moved to more appropriate forum~ TMacK

Edited by TMacK, 30 September 2007 - 12:22 AM.


BC AdBot (Login to Remove)

 


m



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users