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

Change SSL VPN Port

Is it possible to change the SSL VPN Port for Remote Access??

... and for the User Portal, too?



This thread was automatically locked due to age.
Parents
  • well it's great that's its available for 17.1 GA release but the latest release I have access to is SFOS 17.0.8 MR-8. Does that mean people with home licenses get deprived out of this feature?

  • Steve,

    if you have a valid license, e.g. a home license, you can use the most current SFOS release.

    At the moment SF 17.1 is not released yet via up-to-date server, but you should find 17.1 in your mySophos portal.

     

    Best regards,

    Holger

  • As i can see is it possible to use a RANGE for ssl VPN. Is it possible to use a variety of ports by separating them trough comma or something else?

  • vitali wagner said:

    Is it possible to use a variety of ports by separating them trough comma or something else?

     

    No! There is globaly only one single TCP or UDP-port configurable.
  • Some modifications regarding this topic have been done on newly released XG17.1.0 GA.

  • OK, thank you for your replay. now i have a problem that i need to change the port, then i have update the SSL VPN config file on EACH Client? How to fix that whitout big effort?

    Is it impossible to use for example 2 Ports for SSL VPN?

    Can i use a redirection rule so i can use old vpn clients who will be redirected to a new port?

  • Why don't you just try this by youself, as you have this setup allready running?

    If you want to change the port, each OVPN File on each client has to be modified (or the Config Files have to be rolled out completely new). 

    The Effort hardly depends on your rollout Mechanism (if you use a Software Distribution System, it's less effort than doing it by hand).

  • HuberChristian said:

    Why don't you just try this by youself, as you have this setup allready running?

    If you want to change the port, each OVPN File on each client has to be modified (or the Config Files have to be rolled out completely new). 

    The Effort hardly depends on your rollout Mechanism (if you use a Software Distribution System, it's less effort than doing it by hand).

     

    Thanks for you reply. We have many users working from outside, so its hard to find a time window to try out the configuration with the port change and so on.

    But actually i suppose there are a lot of companies facing the same problem. Why is there no recommendations from sophos for this kind of conflict.

    We use SDS but how should i rollout the confiuration ? when its personalisate for each user. i cant use their credentials to get a new config from portal because of our IT Policies. Is there another way to do that?

     

Reply
  • HuberChristian said:

    Why don't you just try this by youself, as you have this setup allready running?

    If you want to change the port, each OVPN File on each client has to be modified (or the Config Files have to be rolled out completely new). 

    The Effort hardly depends on your rollout Mechanism (if you use a Software Distribution System, it's less effort than doing it by hand).

     

    Thanks for you reply. We have many users working from outside, so its hard to find a time window to try out the configuration with the port change and so on.

    But actually i suppose there are a lot of companies facing the same problem. Why is there no recommendations from sophos for this kind of conflict.

    We use SDS but how should i rollout the confiuration ? when its personalisate for each user. i cant use their credentials to get a new config from portal because of our IT Policies. Is there another way to do that?

     

Children