M
Mitch4949
Exchange 2000 and Outlook 2000, 2002 and 2003. We recently separated a
portion of our office onto a different subnet, and their Outlook clients are
now separated from the Exchange server by a firewall. The firewall currently
(for troubleshooting purposes) has no rules restricting traffic between the
subnets. We find that on the remote subnet, when Outlook is left open and
inactive, after a time "send/receive" doesn't work anymore. The firewall
logs show that the attempted connection is using an established connection
that the firewall has broken, most likely due to a one-hour timeout on TCP
connections. In the interim, it appears that new mail has been received by
the client, but that doesn't seem to affect this timeout.
I don't want to change the firewall config, so is there anything I can do on
the client to prevent this timeout from happening?
I thought of going into "Remote Mail" and scheduling a connection every,
say, 15 minutes...would this do the trick?
Thanks very much.
Mitch
portion of our office onto a different subnet, and their Outlook clients are
now separated from the Exchange server by a firewall. The firewall currently
(for troubleshooting purposes) has no rules restricting traffic between the
subnets. We find that on the remote subnet, when Outlook is left open and
inactive, after a time "send/receive" doesn't work anymore. The firewall
logs show that the attempted connection is using an established connection
that the firewall has broken, most likely due to a one-hour timeout on TCP
connections. In the interim, it appears that new mail has been received by
the client, but that doesn't seem to affect this timeout.
I don't want to change the firewall config, so is there anything I can do on
the client to prevent this timeout from happening?
I thought of going into "Remote Mail" and scheduling a connection every,
say, 15 minutes...would this do the trick?
Thanks very much.
Mitch