Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Ross
New Contributor

FortiWiFi 80CM connected to FortiAP 223B (Wireless devices unable to ping other wireless devices)

Hello all, We are currently using a FortiWiFi 80CM router which is connected via Ethernet to a FortiAP 223B wireless access point. We are trying to set it up so that a device (Windows machine) on the wireless 223B AP connection can connect to a wireless printer on the same 223B AP connection. There seems to be no communication happening between the devices on the same wireless network. The devices are unable to ping each other when both on the wireless FortiAP 223B access point. As part of our troubleshooting we eliminated the 223B AP and connected the wireless printer and the device communicating with it (Windows 8.1 machine) to the wireless AP on the 80CM router. Everything worked great, devices were able to ping and communicate with each other. We have tried various things such as creating policies on the 80CM router which include: 223B-Wireless -> 223B-Wireless with all services enabled. My questions are: How do you enable the 223B AP to allow devices on the same wireless network to communicate with each other? Has anybody else had a problem similar to this? Please let me know if I am missing any information regarding configuration and such. Any help would be greatly appreciated! Thank you
6 REPLIES 6
Dave_Hall
Honored Contributor

Confirm that " intra-vap-privacy" under the vap profile is not enable. It should be listed in the GUI (currently not in front of a fgt device to confirm exact location).

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
Ross
New Contributor

Hi Dave, Are you referring to the Block Intra-SSID Traffic setting? If so, the setting appears to be set to off. Thanks
Dave_Hall
Honored Contributor

Could be the same/similar setting under firmware 5.x.

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
yzhang_FTNT
Staff
Staff

Try FOS 5.2 build 603 or later. FAP 5.0 build 76 or later. Please note these builds are not GA builds, and may contain other bugs. You can try to see if they can solve the issue you are facing.
Ross
New Contributor

Thanks to Dave Hall and yzhang for the helpful insight! I believe the problem to be the firmware (though I have not tested this theory). It seems as though we may have to use an older version on our FortiAP which we will try when there are no users on our network. I will try to keep this forum updated with our progress. Also, for anyone looking for more troubleshooting info refer to this forum: http://community.spiceworks.com/topic/469082-fortigate-fg300-no-wifi-communication
Ross
New Contributor

I am happy to say the problem has been fixed! The issue did end up being the firmware. We were lucky enough to have a second FortiAP 223B which still had the original firmware from around 2012 on it. All we did was plug it in and now all is well. For anybody else having this issue, the FortiAP 223B does not seem to allow firmware downgrades (at least I don' t know of anyway of doing it). We have informed Fortinet of this issue and hopefully they will take it into consideration when creating the next firmware update. Cheers
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors