Skip to main content
A
Anonymous_User
Contributor
November 25, 2004
Question

No ping/http/https/ssh via WAN

  • November 25, 2004
  • 2 replies
  • 2357 views
Hi: When I activate ping/http/https/ssh via WAN to admin the Fortigate I have no access this way, obviously is the WAN port used. Any idea?

    2 replies

    A
    Anonymous_UserAuthor
    Contributor
    November 25, 2004
    Fortigate model -> Firmware -> Build Number -> Any Trusted hosts configured ??? Whats the public ip of fortigate ?
    A
    Anonymous_UserAuthor
    Contributor
    November 25, 2004
    Do you have set correct IP for Trusted hosts under System -> Admin ?
    A
    Anonymous_UserAuthor
    Contributor
    November 26, 2004
    Fortigate model -> FG-60 Firmware -> Fortigate-60 2.80,build292,041117 Build Number -> Fortigate-60 2.80,build292,041117 Any Trusted hosts configured ??? 0.0.0.0/0 Whats the public ip of fortigate ? wan1 200.67.122.229/255.255.255.255 I can not access from internal to WAN1 and from internet to WAN1
    A
    Anonymous_UserAuthor
    Contributor
    November 26, 2004
    Again I assume you have HTTPS (I would never use HTTP for this purpose) enabled under System - Network - Interface and therefore you see wan1 with Access HTTPS (also HTTPS on Interface internal I assume) Secondly you have under System - Admin a user with Trusted hosts 0.0.0.0/0 (as you wrote). You are using the same user to connect to the internal interface to administrate your FortiGate 60 - correct? Then you never tried something with IP/MAC binding? If so that' s fine. If all the above is true, then it should be possible to connect from a computer attached to the internal interface to the FortiGate 60 using https://200.67.122.229/ in a browser. If this is not working, then I have no idea what could be wrong. Currently I' m using MR5 and not like you MR6, but probably today I will upgrade a FortiGate 60. I hope your problem is not related with MR6, otherwise I will know this soon!
    Terms & ConditionsAccessibility statement