Entourage2008 doesn't connect to MS Exchange when connected through CiscoVPN

[Fanatic]

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: intel
Email Client: Exchange

Hello,

I recently transferred from WindowsXP to OS-X 10.5, and bought Office-X, with Entourage 2008. It was easy to setup and get working with MS Exchange when I am connected to my corporate LAN. However, when I VPN from my home account, I can't Send/Receive All. In my folder tree beside my work email address (that is exchange) I see the words in brackets (Not connected).

There doesn't seem to be anything available to me to debug or diagnose the problem. No Error messages available.

I'm using the Cisco Systems VPN Client Version 4.9.01 (0100) for Mac OS X.

I'm still able to use all my other corporate applications as if I was connected on the LAN, for example my Oracle Calendar application, and browse our Intranet, and browse network directories. Entourage just doesn't connect to the Exchange Server.

When I use my old computer, with Office 2007 and the Windows version (it is Java) of the same Cisco VPN software, I can use Oracle Calendar, Browse the Intranet, Browse network directories AND download my email to MS Exchange.

This tells me that there is simply something wrong with Entourage2008 connecting to the Server. But I have no way of debugging the problem.

Please help!! I work from home 75% of the time so have to have email access.

 

[Corentin Cras-Méneur]

I recently transferred from WindowsXP to OS-X 10.5, and bought Office-X,
with Entourage 2008. It was easy to setup and get working with MS
Exchange when I am connected to my corporate LAN. However, when I VPN
from my home account, I can't Send/Receive All. In my folder tree beside
my work email address (that is exchange) I see the words in brackets
(Not connected).

Are your DNS server and domain suffixes setup properly for that??
You could try replacing the address to the server by it's IP address or
use a full name (server.domain.com) instead of a short name (server) for
instance.

Corentin

 

[Fanatic]

Thanks for the quick response.

I'm not sure what you mean by "domain suffixes" don't you mean DNS, i.e. the domain name server IP address is setup?

Why would other applications be able to resolve DNS, but not Entourage2008?

Where would I replace the "address to the server" by it's I address or Full Name)?

Thanks in advance!

 

[Corentin Cras-Méneur]

Thanks for the quick response.

I'm not sure what you mean by "domain suffixes" don't you mean DNS, i.e.
the domain name server IP address is setup?

It's for an issue frequently seen on corporate networks.
When you are on your Network, using your local DNS, instead of entering
the full qualified name of the server (server.domain.com), you can just
enter the short version of it (server) and the DNS server redirects you
properly.
Most people don't switch over to the "work" DNS when they connect
through VPN, so this redirection fails.
One solution is to use the full name (but it might fail too if it hasn't
been officially registered adn taken in consideration with all DNS
servers). The other is to use the IP instead.

Why would other applications be able to resolve DNS, but not
Entourage2008?

Entourage is not doing antyhing in this regard. It's just using the
network resources at its disposal.

Where would I replace the "address to the server" by it's I address or
Full Name)?

In Tools:Account:your Exchange account:Server address.

Try the full name, and if it doesn't work, try the local IP.

Corentin

 

[Fanatic]

Putting in the full server name solved the problem.

Thanks!

 

[Corentin Cras-Méneur]

Putting in the full server name solved the problem.

Thanks!

I'm glad it worked
Thanks for letting us know it did the trick. I'm sure it'll help othr
people in the same situation,

Corentin