Skip to main content
foxlet
foxlet
New Member
June 3, 2020
Question

FSSO Issue " Some users didn't reach internet "

  • June 3, 2020
  • 1 reply
  • 9632 views

Good day dears, 

 

I have recently deployed FSSO in my environment.

 

I have FSSO agent installed on DC , Status Running and perfect.

I have FSSO Fabric Connector up and running.

I have FFSO Login Logs from Users.

I have FFSO IPV4 Policy to rout the AD Group working.

 

Many Domain users managed to reach internet through that Ipv4 policy and everything is fine with them, except few other users including me :D ! my machine is domain joined and my account is fine, yet i could not reach internet, neither did few other users.

 

What could be the problem ?

1 reply

xsilver_FTNT
Staff
xsilver_FTNT
Staff
June 4, 2020

I'd start from user to FGT .. 

1. when you login to windows, is your logon caught by FSSO and reported to FGT ?

2. no? then what's the mode .. polling DCs or DCAgents installed ?

3. DCAgents .. on ALL DCs ? so echo %logonserver% on workstation shows the DC chosen to verify your creds and that DC is monitored by DCAgent (or polled) ?

 

Usual problems are:

- DC used by WKS (logonserver) not monitored - user's group membership not matching with group filters

- Collector Agent running in Standard mode but FGT set with LDAP server and so Group Filters are not in compatible format (FGT push LDAP format, while Collector in standard uses MSFT group format, in advanced mode it uses LDAP format and so IS compatible with FGT config. Alt. is to have FGT configured WITHOUT LDAP in FSSO connector and so getting groups from Collector in whatever form. However when you switch then check also groups on FGT as they might not match as change breaks the bonds between 'config user group' and 'config user adgrp' records.)

- users might also be on Ignore List

davidestebanforero
davidestebanforero
New Member
July 16, 2021

Hi @xsilver_FTNT:

 

I am having problems with the authentication mode FSSO Agent DC and Active Directory WinSRV2016.

Although the users are registered in the FW User Monitor and the policy is applied well according to the group, after a few minutes working on the computers, the users are left without an Internet connection. So far I can only fix by logging out of Windows and logging back in. In this way users navigate again.

Does anyone know what this condition is due to? Any extra parameter to modify in the Agent?

 

I am attentive to your answers

 

Thank you !!

xsilver_FTNT
Staff
xsilver_FTNT
Staff
August 2, 2021

So user logs in OK, he is recognized by FSSO and allowed by policy on FGT accordingly, but after some time, like 5 minutes, he is unable to pass through same policy.

First check if workstations' IP is still in FSSO list. Basically looking for the state where source IP from which user was known before, is still listed.

 

If not, then user was removed. Set FSSO Collector log to debug level and check what happened when user was removed. If it was some logout event (WMI), or some over-tweaked workstation check. As failed Workstation check will put record to dead entry and respective timer (settable on FSSO Collector) will start ticking. If that timer ticks out, the record is removed as Collector was unable to determine if user is still logged in. Workstation check can be disabled, but then workstations will be listed till their user logs out (and WMI event is spotted) or indefinitely, which is insecure a bit. Checks might use Remote registry service (which is by default disabled on WKS and needs to be enabled), but I would suggest to use WMI which collector should use when WMI is enabled in Advanced settings and for example WinSec+WMI is used to collect SSO data from DC. WMI is by default running service on any Win2000+ MSFT OS, and uses port 445. So next step is also to check that 445 communication from Collector to workstations is allowed and not blocked by some intermediate firewall or by some security app on workstations itself.

If yes, so it is still listed, then there is most probably another user, not the same as before, and his group-membership driven access rights do not allow previous access level. This is most usually caused by some background operations/application and service processes which "Run as" as different user. And as those operations are authenticated and authorized by domain, then there are logon events as if made by regular user. So put those service accounts to Ignore List on DC Agent and their logon events will not propagate to FSSO.

 

Last possible reason is when workstation do have more than single NIC (network connection) and so IP address changes. Also it might be caused by broken DNS as by default Collector track IP changes via DNS queries, but if correct A record for name is not found or IP is incorrect, then it will cause issues in FSSO. Wrong IP will cause change of SSO record, but as workstation will originate traffic from old/same IP as before it will not match "new" IP learned from DNS anymore, for example.

 

Terms & ConditionsAccessibility statement