08-19-2010 07:34 AM - edited 03-11-2019 11:28 AM
i all,
I have installed Cisco asa 5505 as our company's firewall, and from that day people with mobile devices started complainign that email is not working properly anymore. When i checked the server log i can see errors loged:
"The average of the most recent [200] heartbeat intervals used by clients is less than or equal to [540]. Make sure that your firewall configuration is set to work correctly with Exchange ActiveSync and direct push technology. Specifically, make sure that your firewall is configured so that requests to Exchange ActiveSync do not expire before they have the opportunity to be processed. For more information about how to configure firewall settings when using Exchange ActiveSync, see Microsoft Knowledge Base article 905013, "Enterprise Firewall Configuration for Exchange ActiveSync Direct Push Technology" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=905013)."
So it is quite clear that cisco is terminating 443 sessions to early.
I am after spending 3hours on google, but cant find a simple answer how to increase 443(https) timeout value on cisco asa 5505 firewall?
Getting frustrated here. So is there a simple command u use to change timeout value for protocol 443 through firewall ?
In ASDM i van find timeout values but they are not related to https? am i right?
Thanks in advance !
Linas
08-19-2010 07:50 AM
Hello,
Please try the following:
Please try the following:
access-list Exchange permit tcp any host
access-list Exchange permit tcp any host
class-map Exchange
match access-list Exchange
exit
policy-map global_policy
class Exchange
timeout
exit
Service-policy global_policy global
You can replace the
timeout.
Hope this helps.
Regards,
NT
For some reasons, if the message was sent from email client, the forum is truncating the response. Edited by: Nagaraja Thanthry
08-19-2010 01:06 PM
when i get to here:
policy-map global_policy
class Exchange
>>>> timeout
i have no option to type in value:
ciscoasa(config-pmap-c)# timeout ?
configure mode commands/options:
conn Configure idle time after which a TCP connection state
will be closed, default is 1:00:00
h225 Configure idle time after which an H.225 signaling
conn will be closed, default is 1:00:00
h323 Configure idle time after which an H.323 control
connection will be closed, default is 0:05:00
half-closed Configure idle time after which a TCP half-closed
connection will be freed, default is 0:10:00
icmp Configure idle timeout for ICMP, default is 0:00:02
mgcp Configure idle time after which an MGCP media
connection will be closed, default is 0:05:00
mgcp-pat Configure the time after which an MGCP PAT Xlate will
be removed, default is 0:05:00
sip Configure idle time after which a SIP control
connection will be closed, default is 0:30:00
sip-disconnect Configure idle timeout after which SIP session is
deleted if 200 OK is not received for a CANCEL or BYE
message, default s 0:02:00
sip-invite Configure idle time after which pinholes for
PROVISIONAL responsesand media xlates will be closed,
default is 0:03:00
sip-provisional-media Configure idle time after which a SIP provisional
Media connection will be closed, default is 0:02:00
sip_media Configure idle time after which a SIP Media connection
will be closed, default is 0:02:00
sunrpc Configure idle time after which a SUNRPC slot will be
closed, default is 0:10:00
uauth Configure idle time after which an authentication will
no longer be cached and the user will need to
re-authenticate on their connection, default is
0:05:00. The default uauth timer is absolute.
udp Configure idle time after which general UDP states
will be closed, default is 0:02:00, This timer does
not apply to DNS or SUNRPC
xlate Configure idle time after which a dynamic address will
be returned to the free pool, default is 3:00:00
ciscoasa(config-pmap-c)# timeout policy-map global_policy
08-19-2010 01:18 PM
Hello,
It should have been "timeout conn ". My bad. "Conn" parameter applies
to all TCP connections. The class-map we configured (with the access-lists)
will apply it to the specific traffic in question.
Hope this helps.
Regards,
NT
08-23-2010 06:36 AM
Hm, still reporting timeout on server :/
08-23-2010 08:15 AM
Hi,
Have you tried the class-map and policy-map commands as well? If so, what vlaue have you given for the timeout?
If it's still giving the same error, then i would suggest you to get the logs from the ASA when you notice the timeout occuring. That way we can see what the reason is for the connection timing out.
Regards,
Prapanch
08-19-2010 08:04 AM
Hi,
Take a look at the below link:
In the class map you can specify "htttps" traffic and then specify a timeout vlaue as the action under the policy-map class configuration:
set connection timeout idle hh:mm:ss
If you specify a value of "0", then the connections never timeout.Let me knwo if this helps.
Regards,
Prapanch
08-19-2010 01:09 PM
Hi Prapanch,
sorry i am not that good iin cisco so i am having a bit of difficult to understand the way you are trying to get this done, could you explain me more in detail please i would appreciate. as al this "class" thing is new to me when i was learning cisco we had simpler ways of doing things, i dont remember any class things going on.
I would really appreciate if you could tell me how do i tell router to increase time outs on https traffic only.
Thanks in advance both of you !
Linas
08-19-2010 07:14 PM
Hey Linas,
Basically your configuration will go somethng like this:
access-list HTTPS permit tcp any any eq 443
class-map HTTPS
match access-list HTTPS
policy-map global_policy
class HTTPS
set connection timeout tcp hh:mm:ss
The value you specify in hh:mm:ss will depend on the duration you want. if you set it to 0, then the connection never times out.
regards,
Prapanch
07-21-2013 11:40 PM
Hi Linas,
Did the above suggestion from Prapanch did finally work for you??
I am having the similar issue and need to confirm that.....i am also concerned will this change affect other https based applications?? also could not find the default connection timeout value for https:
the firewall does show default for tcp as 1 hour and i was expecting that https would be part of it.....
if you can come back to me fairly soon that would be highly appreciated as i need to get this resolved ASAP.
thanks in advance!
Regards,
mohit
10-14-2013 08:38 AM
Did this help? I am also seeing similar issues on my windows phone.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide