Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 3 subscribers
  • Views 2254 views
  • Users 0 members are here
Options
Suggested
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

ASG220 8.309 Port 443, DNAT to other internal web server

kalleyne
Good day.

We are using an old ASG220 appliance. We would like to forward port 443 to an internal server.

The documentation describes the process of moving the User Portal to another port (e.g., 1443). We tried this and also disabled the User Portal. We also disabled SSL VPN. However, the DNAT rule that we created still does not appear to work.

Please, we would like some solid suggestions on how we should proceed.

Any suggestions?

Thanks.

Keri


This thread was automatically locked due to age.
Parents
  • 0
    Having the "SW vm test guest" bound to the Internal interface was the reason for your routing problem.

    Normally, in a situation like this, I would have left all of the other standard port 443 settings as is.  On the 'Additional Addresses' tab, I would have created an Additional Address (for examplle) named "SW Server" with IP 72.X.Y.86/32.  In the DNAT, the 'Traffic Destination' would have been "External [SW Server] (Address)" and, since it was unchanged, I would have left 'Destination Service' empty.

    Cheers - Bob
Reply
  • 0
    Having the "SW vm test guest" bound to the Internal interface was the reason for your routing problem.

    Normally, in a situation like this, I would have left all of the other standard port 443 settings as is.  On the 'Additional Addresses' tab, I would have created an Additional Address (for examplle) named "SW Server" with IP 72.X.Y.86/32.  In the DNAT, the 'Traffic Destination' would have been "External [SW Server] (Address)" and, since it was unchanged, I would have left 'Destination Service' empty.

    Cheers - Bob
Children
No Data