B
Bill
we have an exchange organization that spans multiple cities, and each of
those cities has exchange servers. We have a routing situation with a newly
acquired company which is prohibiting network access to our San Diego site.
Some users in Atlanta are trying to connect to the public folder store, as is
evident by viewing the connection status for their 2003 outlook client. Of
course they can't connect to San Diego. Why doesn't outlook try to go to
another exchange server for the public folders, like the local one in
Atlanta? Does anyone know how or why the client chooses its server? His
mailbox is on the local Atlanta exchange server. I'm in another city, and my
outlook chooses both San Diego and Dallas, but not the local exchange server
here. Each location has DNS servers, and the exchange servers have DNS
entries.
thank you,
those cities has exchange servers. We have a routing situation with a newly
acquired company which is prohibiting network access to our San Diego site.
Some users in Atlanta are trying to connect to the public folder store, as is
evident by viewing the connection status for their 2003 outlook client. Of
course they can't connect to San Diego. Why doesn't outlook try to go to
another exchange server for the public folders, like the local one in
Atlanta? Does anyone know how or why the client chooses its server? His
mailbox is on the local Atlanta exchange server. I'm in another city, and my
outlook chooses both San Diego and Dallas, but not the local exchange server
here. Each location has DNS servers, and the exchange servers have DNS
entries.
thank you,