boneyard
Valued Contributor
‎11-17-2021
Last activity: Nov 17, 2021 8:46:59 PM
0 Profile 0% Complete

User Statistics

  • Topics
    16 Topics
  • Posts
    432 Posts
  • Solutions
    22 Solutions
  • Kudos
    2 Kudos
Most Liked Posts Recent Solutions
No Content Available

User Activity

Anyone been looking at this and got it worked out? Azure AD domain joined machines seem a bit different, you can't join the FortiNAC to it, it doesnt seem able to read from it. wondering how people dealt with this.
due to the VPN traffic possibly coming in or going out via one of three interfaces (due to BGP) i felt i should configure the VPN on another interface of the FortiGate. only the VPN process doesn't want to start the VPN now, the debug logs shows: 202...
not many FortiNAC users here yet it seems but going to give it a try. im working on it in a lab environment with FortiGate + managed / fortlink FortiSwitch (6.2) and FortiNAC 8.8. anyone experiences with that setup working fine? im getting odd issues...
a bit of a vague subject but is also a vague issue. we got dozens of VPN tunnels from 100D / 100E (running 6.2.4 currently, but the issue also happened while on 6.0) to different VPN devices. on some of these it sometimes happens traffic doesn't flow...
we had a pretty nice zone based basic configuration for new implementation. this got more complicated when the sd-wan interface was introduced. because it acts a little different. from 6.2.1 it is possible to create firewall policies on the interface...
Kudos from