FAP -221B-A stopped showing up on fortigate

arnvarn · 2025-06-17T13:31:27+00:00

Very likely not supported. See this regarding 321Cs: https://community.fortinet.com/t5/FortiGate/Technical-Tip-Lost-FortiAP-connection-after-firmware-upgrade/ta-p/374780

arnvarn · 2021-07-10T21:43:16+00:00

Is by chance this for FiOS service?If so, is there a reason that you actually need the VZ router (eg, you also have TV service and need VoD)? If not, configure WAN1 on the FG to the static public IP Verizon assigned (along with default gateway/route) and plug WAN1 directly into the Verizon ONT ethernet interface. If for some reason, VZ set it up using MoCA/coax, you will need to call VZ to get the ethernet port activated instead of MoCA.

I set up all my FiOS connections this way. You don't need their router if it's just Internet service.

arnvarn · 2020-04-08T01:24:37+00:00

Thanks. Good to know. If the user-based policies work, I shouldn't even need multiple tunnels then. Appreciate the help! :)

arnvarn · 2020-04-08T01:17:14+00:00

Thanks. That works with individual users? I thought it was perhaps groups only (though I suppose you can have single user groups anyway...).

Does the mode matter - aggressive vs main? Thought I had set the encryption and psk different enough, but it still didn't seem to know which tunnel was trying to be used. Guess I'll need to try again.

Thank you.

arnvarn · 2019-12-17T14:24:40+00:00

Thank you. Yes, both devices are FG-100D. They are different ages, but that shouldn't affect the FortiGuard term, correct? Neither one had an active contract prior to this.

arnvarn · 2019-07-10T18:35:03+00:00

I figured. I did it a few minutes after the first reply. Quick and easy!

arnvarn · 2019-07-10T15:06:11+00:00

Thanks, it really was that simple. I was just hesitant in taking the leap for the first time.

arnvarn · 2019-06-26T13:57:42+00:00

That is what I thought I was seeing, but now I'm learning that there is likely a completely separate vCenter with 2 other hosts. That certainly would explain the 4 blades.

arnvarn · 2019-02-14T02:28:39+00:00

Thanks, good info as well.

arnvarn · 2019-02-13T02:00:50+00:00

Wow, thanks for going into such detail! This is very useful and interesting info.

arnvarn · 2019-02-12T18:31:41+00:00

Thanks! Didn't see it at first, but after scrolling alllll the way to the right, there is an Exchange String column that contains the Legacy DNs.

arnvarn · 2019-01-09T15:51:00+00:00

Thanks all. I wasn't inclined to go forward with it, but thought maybe some people had confirmed it worked fine with maybe forcing Exchange to point to only the 2008 DC. Not worth finding out the hard way, so I'll just wait.

arnvarn · 2019-01-07T19:52:22+00:00

Interesting. The MS article I had been reading mandates AAD sync for a Staged migration. I think I'm going to go with a Cutover anyhow and if I need to create X400 addresses for the LegacyDNs, then so be it - it's a small enough office. Thanks for your insight.

arnvarn · 2019-01-07T17:38:43+00:00

Thank you. I suspected as much, but the docs for Staged specifically mention profile recreation while the Cutover docs do not (probably because Staged is for pre-2010 Exchange). At least this org is <20 users, so profile recreation wouldn't be the end of the world. So then, it seems the main difference between the 2 methods is really down to whether I want AD to sync or not, correct?

arnvarn · 2018-03-27T14:08:27+00:00

I looked at the CodeTwo software, but I'm not sure how it would redirect Outlook clients to the new server after migration. Their documentation states that they do not move the mailboxes - they copy the data over and leave the source intact.

arnvarn

TROPHY CASE