Skip to main content
ggntt
ggntt
New Member
January 22, 2015
Question

Device Detection - Incorrect user matched with device

  • January 22, 2015
  • 2 replies
  • 8955 views

Hi all

 

We have a site running 5.2.1 (HA a/a)

We have device detection enabled and it works, we also have the FSSO agent on AD.

Devices listed show the MAC, OS and logged in user for windows devices.

However, it sometimes shows the same user as being logged into an android or other devices. (even though they are not)

Just wondering if anyone else has experienced this and any idea how to resolve ?  

 

(We are concerned that this will result in spurious data in our reporting)

 

Thanks

Greg

    2 replies

    seadave
    seadave
    New Member
    January 24, 2015

    Is your LAN default gateway in your switching stack or the FG Internal?  We route in our stack with a dedicated interface to the FG Internal.  This masks the MACs (because you are routing between segments) and causes problems such as this.  I just deployed 5.2.2 haven't had a chance to see if the found some other way to do the mapping.

    ggntt
    ggnttAuthor
    New Member
    January 27, 2015

    Hi Dave

     

    No, we don't have any later 3 switches, the FG is the gateway, thanks for the suggestion.

     

    We have held off on the upgrade to 5.22

    Its very strange / misleading from a reporting perspective.

    Anyone else out there getting results like this ?

     

    We suspect it might be the FSSO agent on AD... that will report an IP/ username to the FG which is perfect.

    However when someone connects to the network from a non windows device...e.g Android phone they dont have to login to get an IP address.... I suspect that the FG just assumes that the same user who had  that IP in the past is now the person "logged in" to the android device which is not possible / untrue.

     

    Other devices (e.g VOIP phones) are being reported as windows devices and sometimes have an AD username associated with them which is incorrect.

     

    The trouble is we use user / device based profiles for access control and restriction 

     

    Anyone any suggestions ? (Perhaps its the way we have the FSSO agent configured?)

     

     

    hlatki
    hlatki
    New Member
    July 3, 2018

    This problem was solved? I have the same issue here, if was solved please share with us, thanks!

    Terms & ConditionsAccessibility statement