Solved

Hi all,I have disabled VoIP inspection, but the problem persist.The pbx is within the network like all ip phones.The STUN server on the pbx is enabled. The calls work beyond 30 seconds only without the STUN server and with the pbx published by the VIPs. Do you have any suggestion? Thanks in advanceac

Hello everyone! I got a problem with a FortiWLC-50D running on firmware 8.0 SR1-2 at the moment. When I am logged in the webinterface I get pop-ups for credentials pretty often (definitly not idle timeout). Sometimes the credentials are accepted and I can go on. Sometimes the prompt just disapeers after entering the credentials and appears again after some seconds. My hope is that this is just a problem with the firmware so I tried to update to a newer one.Updating via the web interface leads to the problem stated above all the time and nothing happens. Updates via the cli returns the following: FN-WLC(15)# upgrade controller 8.2-7MR-1This will overwrite all existing system images. Are you sure [y|n]? yPackage security check failed - image  not installed.-If the target release package is touched as root mode manually,  you need to obtain a signed version and try again.ERROR: Please change wrong configurations and then upgrade again, it will exit...Dia

Hello, We have a requirement to create a simple IPSec VPN to another customer who is also using a Fortigate firewall at their end. However, due to a conflict of subnets in our environment, I need to destination NAT their subnet before it hits the IPSec VPN.  Is this even possible? I was of the view that the remote end would have to NAT their subnet that conflicts with our environment and provide us with a new subnet that we can use to route over IPSec VPN. However, the remote end customer is adamant that this should be done at our end. So in other words, I need to do a DNAT before the traffic hits the IPSec VPN tunnel from our end. Can someone please help with this? Thanks.

Hi, I have the following scenario:Site A: 10.149.3.0/27Site B: 192.168.0.0/24Site C:  172.31.10.140/20Site A and Site C must cummunicate.FG is located in site B.On FG in sTie B Site to site VPN A<->B and B<->C is configured.Site to site VPN A-B uses NAT with following configuration: External IP Range172.31.254.9 - 172.31.254.14Internal IP Range192.168.0.1 - 192.168.0.254 Can please assist how to make A<->C communication. Thank you!

Hi All, While trying to import the firewall to FortiManager, getting an error "Data not exist"  while retrieving configuration. FortiManager Version:5.4.2 GAFortiGate firewall: v5.2.4,build688 (GA) Please refer the screenshot attached. Please help me on this. Regards,Sridhar 

Hello, I have configured our Fortigate to authenticate our ssl-vpn users with Azure AD. I've configured the enterprise app within Azure AD and configured the SAML user within the Fortigate. I have no issues when I login the web-mode. However when I try to connect with the Forticlient I receive a blank sceen after passing the authentication. After a while I receive the following error "Login page did not respond within time limit." The second time i press SAML Authentication the forticlient connects within seconds. I reckon one of the URL's might be different for tunnel-mode / web-mode. Did anyone manage to find a solution for this issue?

I have a Cisco Catalyst 4500 core switch, and various cisco access switches. There are a number of VLANs configured on the 4500 and each vlan has its own vlan interface with ip address configured which it is the default gateway of the PCs in the subnet.   Ip-routing is enabled on the 4500 which allows traffic on the various VLANs to be routed back and forth. The internet gateway on the switch is an IP on the Fortigate (10.1.0.90). I cant ping 10.1.0.90 on any of the VLANs except the VLAN the gateway was a member of. Once I dumped a PC onto the VLAN 10.1.x.x, I was able to ping that address with no problem. It looks like a 802.1Q issues. I ran some debugging commands on the Fortigate and the 4500. I setup a running ping from my pc on another VLAN  to ping the address on the 10.1.x.x VLAN. The packet is arriving but as you can see, has issues. From the Fortigate: id=13 trace_id=286 func=resolve_ip_tuple_fast line=4299 msg="vd-root received a packet(proto=1, 10.1.20.3:1-

I have just been told by support that the newer models of Fortigate 80F-PoE and 81F-PoE etc. are NOT going to get the latest firmware's till January. We will be stuck on 6.2.6 till then. For a security company this is embarrassing.

Hi,I'm looking for a command to check interface connection speed in CLI? thanks

As of yesterday we are seeing this on sites that have enabled HSTS, in my example Wikipedia is one of these sites.  Browser is preventing the end user from continuing because it thinks the site has been compromised like a man-in-the-middle attack. Here is what Firefox says and it always mentions our FG100F cert and I've checked and it has not expired yet.  I'm new to using the FortiGate so any help would be appreciated. Thanks,Glen

Hi, Who can say me, what is the latest firmware update for Fortigate 60 ? And where can i download that without contract registration ? Thanks a lot for your reply.

See this here on FortiOS 6.4.7 with SSL inspection enabled since yesterday. 30. Sept 2021.Likely a server misconfiguration. More details in my post here: https://forum.fortinet.com/FindPost/199137 

Hi,  I've tried in Firefox and chrome to use the search function in on these forums but when I type in 'vlan' and click search a drop  down of results appears for a split second and disappears.Paul

Hi,When you have an LACP aggregated link and/or VLAN interfaces in a fortigate at what "level" are you supposed to set the MTU? On our different generations of switches I have seen different behavior and I don't know which applies to Fortigate. I have seen:- Jumbo frames are set per vlan- Jumbo frames are set per port (on the port level and not the lag level) The FortiOS system interfaces table contains items for each port, vlan and lag so where am I supposed to set the mtu? Thanks!

Dear All,  Is there any way to use dnat without a vip? I have the following situation:clients pc  --- fortigate ---- other device ---  192.168.5.5                                                                 |_  192.168.6.6I would like to achieve:a) - A client with ip 10.10.10.10 if want to go to dst:192.168.5.5 then it dnat-ed to dst:192.168.6.6.b) -while other clients if want to go to dst:192.168.5.5 then no-nat-ed, so dst:192.168.5.5 is unchanged and simply forward to the dst. My problem is that the 'external ip' is not on fortigate, and when I create a DNAT & Virtual IP with:External IP address/range : 192.168.5.5Mapped IP address/range : 192.168.6.6Optional filter / Source address : 10.10.10.10Then a) seems to work, there is dnat-ed outgoing packets and replies, but b) doe

Can someone explain why these and other phenomenon happens after an upgrade to 5.x from 4.x? 1. User clicks on this link within an email http://www.icmc.usp.br/~mcmonard/public/laptec2002.pdf The firewall running 5.4.4 blocks this link under the WAF as a "known exploit" If I shut that off, the link passes. My question. Is this a false positive because ever since upgrading the WAF has been blocking a shitload of content. 2. User receives a daily digest (http://feedproxy.google.com/~r/TheHackersNews/~3/Y7H5FF7-MYU/browser-camera-microphone.html?_m=3n%2e009a%2e1504%2epr0ao08ohs%2ewbq) that was fine before the upgrade but now is blocked. Many other inconspicuous sites are getting blocked as well under "generic attacks". The only way for these sites to work is to turn this off. I never had to before. Why now? Should I wipe it clean and start fresh?

Hi Guys,My company has three branch offices in different locations. We have Fortigate 100F at our main office. I wanted to create a site-to-site VPN between my main branch and one other location. My main branch has a Public IP but my other branch doesn't. Someone told me that we can create site to site VPN tunnel with one public IP and one dynamic IP too. I am not too sure, so anyone can please confirm whether this is possible? Thank you a lot in advance.

We are in a (painful and lengthy) transition from FortiOS 5.6 to 6. Next step in the upgrade path is from 5.6.11 tot 6.0.10. Yes, I know, we are 3 years behind... But for us this upgrade to a major version, feels like a giant milestone. We currently use Forticlient 6.0.3.0155 for VPN (Windows only). In the release notes for 6.0.10 on page 12 it says:FortiOS 6.0.10 greatly increases the interoperability between other Fortinet products. This includes: FortiAnalyzer 6.0.8 FortiClient EMS 6.0.8 FortiClient 6.0.9 FortiAP 5.4.4 and later FortiSwitch 3.6.9 and later Upgrade the firmware of each product in the correct order. This maintains network connectivity without the need to use manual steps. On page 16 it says:If you are using FortiClient only for IPsec VPN or SSL VPN, FortiClient version 5.6.0 and later are supported. We only use Forticlient for VPN, not endpoint checking. Will it work ? Or do we have to upgrade Forticlient first ?

Hi All,Cannot figure this one out.. neither can the Fortigate TAC it seems.FG 500E in HA running 6.0.9users on LAN doing MS teams and/or skype video calls complaining about bad quality from the remote party inbound. however remote party can see LAN users fine and quality is good. so it appears only inbound video quality affected from outside of the company network. we have done and tried the following to date> We checked the external and internal interface but no errors or drops observed > We created a traffic shaper but no improvement > We disabled any security profiles in the policy but no improvement > We created a DoS policy for outgoing traffic for the internal interface and there was a slight improvement but not much.> we put a laptop in ISP router it works 100%.> we put this same laptop on a dedicated port on FW problem appears.> deleted and disabled SIP (made some difference but not enough) However Zoom works 100% (not allowed anymore due to se

Hi all.  I'm in a new company just starting up and have borrowed a Fortigate 600D which I'm currently setting up at home on my internal lan. The fortigate has taken a 192.168.0.77 address on my network and I am able to access that from a wireless PC on my home network.  Effectively outside my network.I'm made a softwareswitch (IP 10.0.1.1) of a range of ports in order to have multiple distributed switches be connected to the same VLAN configuration.  I've made half a dozen VLANs and one of those is for managing network devices (VLAN50 10.0.50.1)  That VLAN works fine on the distributed switches as when I connect a computer to an untagged port for VLAN50 it gets an IP 10.0.50.10 and it can also access the internet. My problem is that I want this computer to be able to manage the fortigate on 10.0.1.1 and although I've put a policy in to allow traffic from VLAN50 to the SoftwareSwitch I am unable to open the management GUI.  I can ping 10.0.1.1 but I ca

Hello all,I have a faulty VPN configuration on an IPsec connection between a Fortigate and a Sophos XG to which I cannot find a solution. I have connected several subnets via the VPN: Fortigate: xx.xx.11.0/24xx.xx.6.0/24XG: xx.xx.100.0/24xx.xx.2.0/24xx.xx.0.0/26The connection is established and also works. However, an error is displayed on the Fortigate. The SAs between the firewalls are displayed with the following notation UP: Source: xx.xx.11.0-xx.xx.11.255 Destination: xx.xx.100.0-xx.xx.100.255, xx.xx.2.0-xx.xx.2.255, xx.xx.0.0-xx.xx.0.62 ....The same SAs are displayed with a different notation than DOWN: Source: xx.xx.11.0/255.255.255.0 Destination: xx.xx.10.0/255.255.255.0, xx.xx.2.0/255.255.255.0,xx.xx.0.0/255.255.255.192On the Sophos XG, all SAs are displayed UP.Does anyone have an idea how I can eliminate this error? This permanently reports a faulty VPN tunnel to our monitoring system. Best regards Felix

Hello,        I would like to resolve internal hostnames on my network, and I read on this Forums that it would suffice to set your internal DNS as the primary DNS server on the Fortigate unit in network configuration. BUT, I would also like to have the Fortigate be the first DNS uplink for my internal DNS server, so I could use Fortiguard DNS servers to monitor and block bad hosts (malware, C&C, etc) out there. So, what would be the recommended practice to having both internal hostnames correctly resolved AND funnel all DNS traffic through Fortinet DNS service (assuming there actually is a way to do this)? PLAN B: is there a way to pre-load all my internal hostnames (a la \windows\system32\drivers\etc\hosts) on my Fortigate unit? Is there an editable HOSTS file of some sort? 

Hi all! We have a working SSL VPN that lets outside users access our internal LAN. But I want to restrict access to specific local addresse. Ie I dont want any VPN users to access 192.168.0.20.How do I block a specific local IP?

Dear all, Do you know how to disable "save password" on Fortinet VPN client ?  I would appreciate your help on this matter. Best regards, Miguel Laruccia   

Hello, In the standalone Fortiswitch, we can configure the following VLAN settings in a port: Native VLAN, Allowed VLAN list and Untagged VLAN list. This configuration is available only in the standalone switch; when the switch is managed by a FortiGate, the only settings available are the Native VLAN and the Allowed VLAN list. Can somebody explain to me why should someone need to set the Untagged VLAN list? It seems to me that the Native VLAN alone should be sufficient. What additional functionality does the Untagged VLAN list provides to the port consifuration, that is not covered by the Native VLAN? Thanks