• State Not Answered
  • Replies replies
    12
  • Subscribers subscribers
    15
  • Views views
    364
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using a alternative port for a GMS client

MigrationDeletedUser
Hi,
I know this question is not directly GMS, but I have been searching Google and Apple without finding the answer.
I want to have GroupWise web access on default port 443 - and I would like to use GMS to get mail and calendar on iOS clients.

So I will make a NAT rule in the firewall translating an alternative port to my GMS server on port 443.
Can this alternative port be configured in an iOS mail account (Exchange type)?
Parents
  • 0
    Yes - I know.
    That is why I will only use the alternative port from client to firewall and then redirect in the firewall to standard 443.
    So my question is on the client side.
    Regards.
  • 0 in reply to MigrationDeletedUser
    In article <clausbc.6hyzgn@no-mx.forums.novell.com>, Clausbc wrote:
    > That is why I will only use the alternative port from client to firewall
    > and then redirect in the firewall to standard 443.
    >
    Just to be sure we are all on the same wavelength.
    Is your GMS running on its own instance of SLES, separate from WebAccess,
    but you have only the one public IPv4 address to work with?


    Andy of
    KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0 in reply to Andy Konecny
    konecnya;2327224 wrote:
    In article <clausbc.6hyzgn@no-mx.forums.novell.com>, Clausbc wrote:
    > That is why I will only use the alternative port from client to firewall
    > and then redirect in the firewall to standard 443.
    >
    Just to be sure we are all on the same wavelength.
    Is your GMS running on its own instance of SLES, separate from WebAccess,
    but you have only the one public IPv4 address to work with?


    Andy of
    KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!


    Yes, that is the exact situation.
  • 0 in reply to MigrationDeletedUser
    clausbc wrote:

    > > Just to be sure we are all on the same wavelength.
    > > Is your GMS running on its own instance of SLES, separate from
    > > WebAccess,
    > > but you have only the one public IPv4 address to work with?
    >
    > Yes, that is the exact situation.

    As others have pointed out, depending on the device you may or may not
    be able to specify an alternate point. I know your question is
    regarding iOS, but even then, there's always the possibility that an
    iOS update could break this even if today iOS allows specifying an
    alternate port.

    If anything I would keep GMS on standard 443 because of device
    limitations and then use an alternate port for WebAccess. You can
    always specify the port in a URL in a browser. That would be much
    safer.

    --
    Your world is on the move. http://www.novell.com/mobility/
    BrainShare 2014 is coming. http://www.novell.com/brainshare/
  • 0 in reply to MigrationDeletedUser
    In article <clausbc.6i05lb@no-mx.forums.novell.com>, Clausbc wrote:
    > konecnya;2327224 Wrote:
    > >...
    > > But you have only the one public IPv4 address to work with?
    >
    > Yes, that is the exact situation.
    >
    Instead of doing PAT at the firewall, just do straight NAT and set your
    GMS or Webaccess to the port you are using so that it is the same port for
    client as well as what GMS or Webaccess is using. Also make sure it isn't
    a common port or too high up, 1443 is a commonly picked one for those of
    you in your situation.

    If it is still a problem, it would be worth capturing the packets of the
    attempts coming in, either at the firewall level and/or on your GMS or
    Webaccess server.


    Sorry for the delay, August got weirdly busy for me and I've finally got
    the time

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

Reply
  • 0 in reply to MigrationDeletedUser
    In article <clausbc.6i05lb@no-mx.forums.novell.com>, Clausbc wrote:
    > konecnya;2327224 Wrote:
    > >...
    > > But you have only the one public IPv4 address to work with?
    >
    > Yes, that is the exact situation.
    >
    Instead of doing PAT at the firewall, just do straight NAT and set your
    GMS or Webaccess to the port you are using so that it is the same port for
    client as well as what GMS or Webaccess is using. Also make sure it isn't
    a common port or too high up, 1443 is a commonly picked one for those of
    you in your situation.

    If it is still a problem, it would be worth capturing the packets of the
    attempts coming in, either at the firewall level and/or on your GMS or
    Webaccess server.


    Sorry for the delay, August got weirdly busy for me and I've finally got
    the time

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.