Outlook 2003 doesn't work over a VPN connection

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I I am having a bizarre problem with the Outlook 2003 client on my laptop.
My Outlook 2003 client works great when I am in the office and physically
connected to the work network.

When I am home, I use a Cisco VPN client over my SBC Yahoo DSL connection to
access my work network. I can access all the network resources on my work
network over the VPN connection, but the Outlook 2003 client cannot connect
to the Exchange Server over the VPN connection. The bizarre thing is that
the client can connect to the server about 10% of the time. Even when it
connects, sometimes the status says "Connected" and "Waiting to update
folders", but it stays that way for ever without downloading any messages. I
can ping the Exchange server and also access my email using a web browser,
but the client for some reason is not able to connect to the server. I used
to have Outlook XP before on my older laptop and even now I can connect to
the same exchange server using the older laptop with Outlook 2002 without any
problems.

I have Service Pack 2 installed, but I tried without it and it didn't make
any difference.

And, there are others at my work place that have Outlook 2003 that don't
seem to have this problem.

I even went to the extent of wiping out everything on my laptop and
reimaging it. I then loaded just Office 2003 and the VPN client. Even then
I am seeing the same results.

Has anybody else seen similar issues with Outlook 2003?

Thanks!
 
All,

I'm having the exact same problem, but not with Cisco VPN, but with the
generic MS VPN. Switching Cached Exchange mode on or off does not help.
It just keeps connecting and disconnecting.

Client is connecting through a peer-to-peer wireless connection using
Internet Connection Sharing.

Client is on SP2 and the only other weird thing I have (and maybe they
are related) is that for some reason the client browser cannot display
any websites that are using the same domain suffix within the LAN ip
segment. And this happens ONLY when the client connects through this
ICS.

No problems at all with regular LAN (wired) connection. So it seems
like it's more ICS related.....

Marcelio
 
Back
Top