Most likely your IT people have SSL required on the Exchange server. If OWA
is enabled (most likely) then in theory, Entourage should be able to connect
to the server if the IT people have done their job right. We have
experienced some of the "not connected" problems and they went away once the
System people enabled SSL for the backend servers and applied certificates
to them as well.
You can try using a unix-command to watch the traffic from your Mac by
opening a Terminal window and typing the command:
sudo tcpdump src your_ip_address
replace your_ip_address with the actual one in listed in the Network
Preferences.
Start up Entourage and watch lines appear in the Terminal window listing the
TCP/IP traffic going from your computer. If there is a SSL problem, you
will see a line periodically for each shared calendar in Entourage that
lists the host address of your backend server and "https:". Normally you
should see a ton of lines listing the backend server host address if the
connection is opened. Instead you will see only a few among the many other
lines. Entourage seems to try every minute or so to establish the
connections and will fail if the backend server it is trying to connect to
is not set up to respond to SSL and has a certificate. If you have two
shared accounts then you will two connection attempts fairly close together
as Entourage "talks". Unfortunately, though I can now see the accounts, I
now get a "certificate warning". Clicking OK still grants access to the
data.
Another test to see if the backend server will listen to SSL properly is to
go into a browser and try:
https://backend-server.domain.com/public
I am prompted for my UserID and password and then I see the empty public
folder we have. Prior to Systems putting on SSL and the certificate, I
would receive the error dialog - "no such server".
Other things that are critical is the DNS must include the domain of the
Exchange server in the Search domain. If it does not, you can manually type
the domain into the Network Pane in Systems Preferences. This was necessary
for me. Delegated access relies on this because it uses only
partially-qualified name. Finally, you need to have "Use SSL for WebDAV"
checked in the Advanced pane of the Tools/Accounts/Edit window.
Sorry if this is both too technical and not enough
Bill