Hi all, Running v6.2 firmware and not able to perform a simple port
forward to an HTTPS server internally, something odd in the Fortinet
logic or is it a known issue? Trying to access an internal HTTPS server
from outside, I've setup a NAT (Virtual I...
Let me spell out the difference for you. Workaround: Changing internal
web server port to allow access remotely OR changing SSLVPN/Admin port
on Fortigate Fix: Fortigate allows port 445 (any free external port)
externally on it's own IP to an interna...
I'm well aware that 445 is not used by Fortigate hence the reason to
select it. It is however used internally on 443 and I suspect it's not
able to NAT correctly internally to a different IP when using 443. David
provided a workaround, this is not a ...
I understand that but as it's a simple NAT there isn't any need to post
the config, I wanted to ask around to see if it's a known issue. It
doesn't seem like it is so i'll push this to Fortinet support team.
