Some users report that Outlook does not always auto-detect when to use
HTTPS (Outlook Anywhere) and when to use TCP/IP (MAPI RPC). In the
dialog box Microsoft Exchange Proxy Settings, the default setting is
selected:

* On slow networks, connect using HTTP first, then connect using
TCP/IP.

Some times when these users are disconnected from the corporate
network, they report that Outlook freezes until they change the
Microsoft Exchange Proxy Settings to:

* On fast networks, connect using HTTP first, then connect using
TCP/IP

Then Outlook Anywhere works.
According to my knowledge (and experience), Outlook is coded with some
logic to cycle between the two connection types. If both fail,
Outlook takes a deep breath and then tries the two protocols again.
This is also stated he
http://www.eggheadcafe.com/conversat...did=3249 0414

These users of course find it inconvenient to reconfigure Outlook this
way when they are outside the corporate network, and to revert the
settings when they are back from their travel.
Have others experienced this problem as well? Is this a known problem?
Are there some workarounds?

The clients are Outlook 2007 SP1 and SP2 with Exchange 2007 SP1 Rollup
6 on Windows 2008 SP1. A split-brain DNS is used: mail.mydomain.com
resolves to an internal private IP address and an external public IP
address.

Best regards, Jon-Alfred

The logic behind slow/fast is based on what connection type you have. For
example, a wireless connection or better will always be treated as FAST.
Dialup access I have is a joke because I can't get anything better than 26.4
and that is usually treated as SLOW. Have no clue what a true 56Kbps
connection would be treated as.

Is it safe for us to assume in your split-brain DNS scheme that your domain
joined workstations can't resolve the internal IP address from a public
location?

"Jon-Alfred Smith" wrote in message
...
Some users report that Outlook does not always auto-detect when to use
HTTPS (Outlook Anywhere) and when to use TCP/IP (MAPI RPC). In the
dialog box Microsoft Exchange Proxy Settings, the default setting is
selected:

* On slow networks, connect using HTTP first, then connect using
TCP/IP.

Some times when these users are disconnected from the corporate
network, they report that Outlook freezes until they change the
Microsoft Exchange Proxy Settings to:

* On fast networks, connect using HTTP first, then connect using
TCP/IP

Then Outlook Anywhere works.
According to my knowledge (and experience), Outlook is coded with some
logic to cycle between the two connection types. If both fail,
Outlook takes a deep breath and then tries the two protocols again.
This is also stated he
http://www.eggheadcafe.com/conversat...did=3249 0414

These users of course find it inconvenient to reconfigure Outlook this
way when they are outside the corporate network, and to revert the
settings when they are back from their travel.
Have others experienced this problem as well? Is this a known problem?
Are there some workarounds?

The clients are Outlook 2007 SP1 and SP2 with Exchange 2007 SP1 Rollup
6 on Windows 2008 SP1. A split-brain DNS is used: mail.mydomain.com
resolves to an internal private IP address and an external public IP
address.

Best regards, Jon-Alfred