As a GroupWise administrator I am often confronted with the problem, that the default GW client port tcp 1677 is filtered on most firewalls. So when mobile users try to access GW from different locations outside of the corporate firewall they can't and complain. It would be great to have some kind of feature that allows GW clients behind a firewall to connect to the corporate server over tcp443/https. Https is a wildly spread standard port, over which GW clients could connect from any location to the corporate GW server. Changing simply the standard 1677 port to 443 is not a complete solution as GW protocol can not be proxied. I mean that organizations, ISPs often use proxy servers so clients don't have direct access to the Internet but over a proxy server (squid, iis, etc.). The other problem is that GW protocol is not http, so firewalls with protocol filtering enabled simply block it even if it is on port 443. Another problem is that organizations with many POs can't afford to buy IP addresses for every PO server to make it accessible over internet. All in all a common access point for every PO server over internet encapsulated in https would solve these problems.

by: Gellért H. | over a year ago | Windows Client