You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When visiting the Active Directory Domains page, I receive the following error:
This only happens for two domains on a remote network via VPN.
One or both of the two domains randomly shows this error and the "Domain Joined" status is red while in reality it is joined.
The internal domain doesn't show this error.
Maybe a timeout is set too strict?
Steps to reproduce the behavior:
Go to Active Directory Domains page
See error
PacketFence ZEN Version 14.0
The text was updated successfully, but these errors were encountered:
PF version (14.0) with commit id - this can be found by clicking the "?" at the top right of the admin UI.
Does PacketFence have to establish a VPN connection to talk with the AD ? - If yes, the problem is probably due to the VPN, currently PacketFence directly talks to domain controller unless a VPN connection will "redirect" or "proxy" the traffic transparently.
If the answer of question 2 is No. Does it take a longer time (RTT) to talk with the AD ? - currently the timeout is set to 2s.
What are the ADs - the working ones and the not working ones - do they have multiple DCs to load balance the authentication requests ?
Hi @vanderti
since the ZEN iso is built during the release, the content of the ios is solid after release.
you'll need to update (not to upgrade to a newer version) PacketFence to have the latest maintainance patches and bug fixes (and probably fix the issue you mentioned) unless there's some special networking conditions.
When visiting the Active Directory Domains page, I receive the following error:
This only happens for two domains on a remote network via VPN.
One or both of the two domains randomly shows this error and the "Domain Joined" status is red while in reality it is joined.
The internal domain doesn't show this error.
Maybe a timeout is set too strict?
Steps to reproduce the behavior:
PacketFence ZEN Version 14.0
The text was updated successfully, but these errors were encountered: