Skip to main content
krishna_konduri
krishna_konduri
New Member
July 23, 2012
Question

Unable to ping

  • July 23, 2012
  • 9 replies
  • 18045 views
Hi, I am unable to ping any of the public Ip from the Fortigate CLI. That is the reason it is showing license information as unreachable. Please help me in resolving the issue. Thanks in advance..

    9 replies

    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    July 23, 2012
    Hi, welcome to the forums. Do you have set up a default route? Look in ' Router' >' Static' >' Static Route' and if not, add the route ' 0.0.0.0/0' , with your ISP' s gateway address and the WAN interface in use.
    krishna_konduri
    krishna_konduriAuthor
    New Member
    July 23, 2012
    Hi Ede, Default route is already there and inside hosts are able to reach internet.
    rwpatterson
    rwpatterson
    New Member
    July 23, 2012
    Can you not reach by IP or by DNS name? What firmware version?
    krishna_konduri
    krishna_konduriAuthor
    New Member
    July 23, 2012
    I tried using IP and DNS name. Both are unsuccessful. Version i am using is : FG200B-4.00-build324
    Gareth
    Gareth
    New Member
    July 23, 2012
    Do you have DNS set up? Can you exec ping 8.8.8.8? Wouldn' t recommend leaving it at that, but if you don' t know your local ISP DNS, set your DNS server to 8.8.8.8 and see what you can get to from there.
    rwpatterson
    rwpatterson
    New Member
    July 23, 2012
    From the command line try:
      FGT # exec traceroute 8.8.8.8
    This will show you the path that the FGT is using to try to reach the Internet and where it stops.
    krishna_konduri
    krishna_konduriAuthor
    New Member
    July 23, 2012
    I Tried it, but unable to ping. Output is below. execute traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 32 hops max, 72 byte packets 1 * * * 2 * * * 3 * * * 4 * execute ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes --- 8.8.8.8 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss
    krishna_konduri
    krishna_konduriAuthor
    New Member
    July 23, 2012
    One more thing i observed is i am unable to ping the default gateway also. But i am connecting to the firewall from outside network. i don' t know why i am unable to ping the default gateway also... :(
    rwpatterson
    rwpatterson
    New Member
    July 23, 2012
    From the CLI, 
    FGT # exec ping-options view-settings
    Make sure everything looks right. The below is the default:
      Ping Options:  	Repeat Count: 5  	Data Size: 56  	Timeout: 2  	Interval: 1  	TTL: 64  	TOS: 0  	DF bit: unset  	Source Address: auto  	Pattern:   	Pattern Size in Bytes: 0  	Validate Reply: no
    Matty28
    Matty28
    New Member
    July 24, 2012
    Hi Are you running Vdom' s by any chance?
    Wenlong_Qin_FTNT
    Staff
    Wenlong_Qin_FTNT
    Staff
    July 27, 2012
    You should be able to ping default gateway from the CLI. If not, you may have wrong default gateway setting. If you can ping default gateway from the CLI, please make sure your firewall setting had enabled NAT.
    lhou_FTNT
    Staff
    lhou_FTNT
    Staff
    July 31, 2012
    I guess it is the mgmt VDom issue. Your mgmt must be set to another VDom. It is common on 100D because old builds by default set the mgmt-Vdom to a internal VDom. You only need set back the mgmt-Vdom to root to solve this problem
    Terms & ConditionsAccessibility statement