The only things I can think of at this point is that "mail.domain" resolves
to something unexpected when on the domain and dsl connection. When you are
on either connection and perform a nslookup -q=A mail.domain, do you get the
IP address you expected to see?

I would also check IIS configuration. For example, does the RPC/HTTP proxy
server only accept connections from specific IP address(es)?


"Brad M" wrote in message
...
Hi neo,

Confirming Config

Exchange Profile/General tab
When Starting Automatically detect connection state, timeout 30seconds

Exchange Profile/Advanced
Use Cached Mode

Exchange Profile/Security
Kerberos/NTLM Password Authentication

Exchange Profile/Connection
Connect using my LAN
Connect to my Exchange mailbox using HTTP

Exchange Proxy Settings
URL mail.domain (same name internal and external)
On fast networks connect using HTTP first, then...
On slow networks connect using HTTP first, then...

Basic Authentication

TESTING RESULTS - the laptop was disconnected from each network type,
connected to the new network and restarted between each test

On the domain ethernet
Outlook launched with /rpcdiag,
Outlook prompts for domain credentials (for the exchange server) which
were
entered and accepted OK
Connection status shows ---'s for a little while then eventually outlook
connects TCP/IP (what happened to HTTPS?)

On CDMA Broadband USB device
Outlook launched with /rpcdiag
Outlook prompts for domain credentials (for the exchange server) which
were
entered and accepted OK
Connection status shows ---'s briefly then outlook connects HTTPS

On DSL Broadband modem (which has NAT/DHCP)
Outlook launched with /rpcdiag
Outlook prompts for domain credentials (for the exchange server) which
were
entered and accepted OK
Connection status shows ---'s (there is no interface name present)
Clicking "reconnect" has no effect

thanks again
Brad



"neo [mvp outlook]" wrote:

If you start Outlook with the /rpcdiag switch, does it show Outlook
cycling
thru both connection types?