I am pulling my hair out here. We changed ISP' s so i setup the NEW IP
scheme on the WAN2 of the 100A of our remote office. I kept the WAN1
link enabled until we were satisfied with the new setup. The new ISP
link is live and working great with all t...
Not sure how to explain this so pls see attached jpeg screenshot.
Although fully connected, we don' t see any activity in the GUI under
Unit operations for INT1 OR in the Traffic History graph (shows no
activity!). Not pressing but wanted to find out...
This an odd one... We just deployed a Forti 80CM in one of our offices
and all the interfaces seem to be fine BUT the WLAN. I had to downgrade
the firmware from 4.0 to 3.0 MR7P9 and restore a config backup from a
60. The link status on WIFI is grayed...
Hello, Not sure where to put this type of request since i do not see a
dedicated area for Fortigate models but we are up for renewal on all of
our 12 Fortinets (1-110c and a mix of 100A, 100, 60' s) We are thinking
of replacing the 100' s and backup ...
Hell All, I hope I can clearly explain this. I have about 10 VPN tunnels
going and active from our Corporate Fotigate 110C (3.0 MR7) without any
major issues. All the policies are set from the Corp LAN on PORT1 e.g.
192.168.10.0/24. I have few more i...
Thanks RWpat! By taking the previous WAN IP info on WAN1 completely out
and replacing it with with zeros' .....tracert is sane again. It also
fixed another routing issue we were having. Is this a bug? As always,
thanks!
yup...did a reboot on both but still shows the previous WAN address????
What is odd is that we have literally disconnected the line to the old
ISP router.
Hello fellas, I followed the English PDF and setup the Iphone 4 (4.2)
and also the Fortigate 110C with 4.0 MR1P6... I have made sure i check
all the settings on both configurations and assured that they match the
instructions but when i start up the ...
" Also, make sure that the far end sites know how to route back to
192.168.25.0/24" So first I smacked myself for about 3 mins...and then
went ahead and added the static route on the external fortinet BACK to
192.168.25.0/24 at Corp... AND IT WORKED!...
ORIGINAL: SecureLayers-Eric To debug this do the following via the CLI
on both ends diag sniffer packet any ' icmp and host '
4 you will see packets (ping/tracert) from and to interfaces and this
will explain the issue. bob: the routing metrics / dis...
