Outlook and Checkpoint SecuRemote

  • Thread starter Thread starter David
  • Start date Start date
D

David

We have a problem with Outlook 2003 not being able to
Send and Retrieve while connected on a Checkpoint
SecuRemote r56 VPN connection.

The routine goes as follows:

* Open Checkpoint SecuRemote client and log onto the VPN
* Open Outlook
* Windows requests domain username and password
* Outlook opens, but in lower right corner, reports
trying to connect.
* When sending and retrieving, error code 0x8004011D is
reported.


I can ping the server by the ip address, servername and
fully qualified domain name.

This worked on the machines last week, and other than
recent MS updates to Windows and Office 2003 SP1, there
have been no updates installed.

What is happening here? How can we fix this? Any help
will be gratefully received.

Many thanks
 
Try changing Outlook 2003's authentication type in the account settings from
Kerberos/NTLM to just NTLM. (Outlook 2003 is the first version to be able
to use Kerberos and has been known to cause issues with other VPN clients.)
 
I have gone into the settings and changed this, but it
still cannot connect.

It asks you to log into the server Exchange sits on, but
does not send/retrieve.

However, at the point you try, we do see some TCP/IP
traffic reported on Service 135, Source 2039, target port
1212.

Does this mean anything?

Many thanks.

Try changing Outlook 2003's authentication type in the account settings from
Kerberos/NTLM to just NTLM. (Outlook 2003 is the first version to be able
to use Kerberos and has been known to cause issues with
Click to expand...
other VPN clients.)
 
Not really. Does the site use WINS/NetBIOS at all? Is WINS name resolution
working okay? You also might want to state if this is an Exchange 5.5 or
Exchange 2000/2003 shop since the Outlook 2003 client needs to establish
connection to the GCs when working against Exchange 2000/2003. Starting
Outlook 2003 with the /rpcdiag command line switch might help you see this.
 
I am having the same issue with a different brand of firewall/VPN server and
Exchange 2003 with Outlook 2003 but the behavior is the same. Here is what I
have found:

1. Changing between Kerberos & NTLM authentication in Outlook makes no
difference
2. The client (Windows XP domain member) works fine when connected to the
LAN but not when connected through PPTP VPN, even though it can ping the
Exchange server (which is also the DC and GC/DNS/WINS server) by IP, FQDN,
and NetBIOS name, so DNS, WINS, & connectivity are NOT the problem
3. Microsoft published a KB article 824123 that addresses this exact issue
but according to a contact at Microsoft the article has been "archived" and
is no longer available to the public and has no other article to supercede
it. Check out http://www.it-faq.pl/mskb/824/123.HTM - it is a foreign web
site that published the first half of this missing KB article on how to fix
this exact problem but unfortunately they cut off the solution part.

Anything that anyone can come up with would be appreciated.
 
Back
Top