This issue is fixed. There was a single Exchange 2003 server configured for
rpc/http. Using the same certificates/configurations, we added a front end
server and it started working as expected.

There is a major bug in there somewhere -- either in the Exchange side that
correctly supports XP but will not suport Vista/Office 2007 or on the client
side that has different rules/behaviors from Outlook 2003.

Should be transparent which client is connecting to Exchange and it appears
that is is not.


"Diane Poremsky [MVP]" wrote:

Do you have it using the option for fast networks and slow networks to
connect using https then tcp/ip when connected? Try changing those settings
and see if it works - I know Ol2007 works as you expect because its working
for me inside the network - both mail and directory are https.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:



"bellster007007" wrote in message
...
Existing enviornment Exchange 2003 with XP -- office 2003 -- all working
correctly.

Problem:

Inside the network, no firewalls invovled.
Clean install of Vista, Clean install of Office 2007 Beta 2 -- no errors
reported.
Create a new profile, configure it for RPC/HTTP and it seems to work.

Go into the connections tab however, and it shows different.
There are three directory connections all showing HTTPS
The mail connection always shows TCP/IP no matter what I do. When taking
it
outside of the firewall, the directory connections are HTTPS, but the mail
connection is never made.