Hi there. Hoping someone can point me in a direction to try to determine why users, including myself, when we're using laptops wirelessly, and connect to the LAN via SonicWALL Global VPN; map drives; open Outlook; etc.. we get these random, varying delays in sending emails. Example from a few minutes ago with my own laptop here: - Windows 7 Pro, 64 bit OS, connected wirelessly (no firewall or anything) and I enable a VPN to the LAN to get to my share drives and to be able to access email via Outlook 2010 - Can connect to Exchange server 2010 on Server 08 R2 PowerEdge R510 and pull down email - Type an email and send, it says it's sending, sits in Outbox for up to 15 minutes.. towards an hour .. nothing in the SonicWALL VPN client log on my laptop. It eventually sends fine.. but obviously it's very annoying and my CFO is not happy and has been bugging me to find out why this is happening lately. Nothing much has changed domain-wise.. We run a very old Pro 2040 SonicWALL device for the main office here, which I'm planning to upgrade soon... Is there somewhere on the Exchange server I can research? I'm admittedly not an Exchange guru .. so bear with me :) (Side note: LAN connected outlook/exchange sends fine/instantly like normal.) Thanks Jeff

Are you using Outlook Anywhere or Outlook? If Outlook Anywhere try adjusting the keep alives on the CAS servers. Set to a low value like 120 seconds. Create the key if it doesnt exist. Configuring Computers for RPC over HTTP HKLM\Software\Policies\Microsoft\Windows NT\Rpc\MinimumConnectionTimeout DWORD. When present, specifies the minimum connection timeout used by the client and RPC Proxy, in seconds. The actual timeout used is the lower of this value and the IIS idle connection timeout. If zero, or the key is not present, the IIS idle connection timeout is used. Used only in RPC over HTTP v2. When changes are made to this value on the RPC Proxy, IIS must be restarted for the change to take effect.

Hi and thanks for the reply! This is using Office Professional and Outlook 2010 client, with a VPN connection to the company exchange server. The web access (/owa at the end) does not have these issues sending like we are seeing with Outlook/VPN/Exchange Jeff

Hi and thanks for the reply! This is using Office Professional and Outlook 2010 client, with a VPN connection to the company exchange server. The web access (/owa at the end) does not have these issues sending like we are seeing with Outlook/VPN/Exchange Jeff Right, but what mode is Outlook in when using wireless? Outlook Anywhere (RPC over HTTPS)? If so, you can try that suggest

Eh ... err.. Obviously I'm no Exchange guru here... but if I go into Control Panel -> Mail -> Account settings for my exchange server connection it's set the same if I'm cabled into the LAN at my desk, or if I'm wirelessly connected with VPN enabled. There's no difference within Outlook settings to diferentiate between someone connected wirelessly or on the LAN that we adjust anywhere. That would probably explain why Outlook doesn't work without the VPN client enabled when users are wirelessly connected on work laptops and they defer to Outlook web client access via IE 8/9. Hopefully this answered your question - if not maybe dumb up for me where to tell how I'm connecting wirelessly? ;x Jeff

Eh ... err.. Obviously I'm no Exchange guru here... but if I go into Control Panel -> Mail -> Account settings for my exchange server connection it's set the same if I'm cabled into the LAN at my desk, or if I'm wirelessly connected with VPN enabled. There's no difference within Outlook settings to diferentiate between someone connected wirelessly or on the LAN that we adjust anywhere. That would probably explain why Outlook doesn't work without the VPN client enabled when users are wirelessly connected on work laptops and they defer to Outlook web client access via IE 8/9. Hopefully this answered your question - if not maybe dumb up for me where to tell how I'm connecting wirelessly? ;x Jeff When the issue is happening, check the connection status in Outlook per: How to View Established Connections in Outlook If it says HTTPS then its using Outlook Anywhere

When the issue is happening, check the connection status in Outlook per: How to View Established Connections in Outlook If it says HTTPS then its using Outlook Anywhere Ok, under the Conn column it's saying TCP/IP not HTTPS. Jeff

When the issue is happening, check the connection status in Outlook per: How to View Established Connections in Outlook If it says HTTPS then its using Outlook Anywhere Ok, under the Conn column it's saying TCP/IP not HTTPS. Jeff Are you in online or cache mode? Cache mode is preferred - and if remote , Outlook ANywhere shold kick in - assuming its enabled on the Exchange Side.

Hiya Yeah everyone is set to Cached mode on their end user machines. So do I need to enable something on the Exchange server side then? Will that negate the need for a VPN connection to talk to the server then if it gets enabled? (How does it authenticate like that if so?) Jeff

Cripes... this looks involved.. .. http://technet.microsoft.com/en-us/library/bb123542

Cripes... this looks involved.. .. http://technet.microsoft.com/en-us/library/bb123542 Its not. If its not already enabled, then enabling it will allow for remote Outlook users to connect on port 443 rather than via MAPI - and without requiring an additional VPN tunnel. http://technet.microsoft.com/en-us/library/bb123741.aspx

Hi Jeff, I am suspecting it is caused by low network speed of your VPN, and I'd suggest you contact your network IT guys for a upgrade or adjust. You may also contact your Exchange administrative to enable Outlook Anywhere for a better performance in client side. Fiona Liao TechNet Community Support