Outlook 2003, XP, over IPSec VPN

[Mike]

Can ping the mail server by name, but not able to resolve
mailbox name in the properties of the profile.
Combination is XP (SP1 w/ all critical updates), Outlook
2003 (w/ all updates), and an IPSec VPN, and a back-end
Exchange 2000 mail server. I can connect and
authenticate using OWA thru the VPN w/o a problem. Also,
have a Win2K Pro laptop w/ Outlook 2000 over the same
IPSec VPN that works fine.

Appears to be a problem with the XP/Outlook 2003 combo.
This KB is close, but I'm not using a UPN... rather I'm
trying to authenticate using Domain\username.

http://support.microsoft.com/default.aspx?scid=kb;en-
us;830355&Product=winxp

 

[JDTHREE [MVP]]

Did you ever find anything out about this? I'm dealing with the same
types of issues. Mine, however, already have the profile set up -
that was done on the local network. It's when they try to remote in
over a VPN that it takes 2 to 3 minutes to actually get mail to
transfer, even though they can immediately do things like map drives
to the exchange server, ping it by netbios name, FQDN, IP, anything.
I can even manage my computer and connect to the exchange server to do
administrative tasks like services, event viewer, etc... So it's not a
connectivity or permissions issue - I can do absolutely everything
over the VPN immediately - EXCEPT email. That always delays on the
initial attempt for 2 to 3 minutes. After that, it's immediate as
expected. Very frustrating, as it only happens on XP with 2003
outlook. I have a "pre-office" image of this tablet pc, and if I
install office 2000 or 2002 on it, works just fine. Re-image the
tablet, put 2003 on it, and viola, lag at initial connection.

Haven't gotten any answers on it yet from anywhere, and this problem
is the delay in my being able to move my company from Office 2000 to
Office 2003.

john.