|
After the Persistent Agent establishes communication with FortiNAC, the FortiNAC requests the PA to log in through a pop-up window.
It is possible to search the keyword 'Login' in the 'C:\ProgramData\Bradford Networks\bndaemon_log.txt'.
FortiNAC requested the login credentials from the device:
2025-12-12 15:24:42 UTC :: Received,req=6305,resp=0,Login,fnac76.eb.lab
2025-12-12 15:24:42 UTC :: Processed,req=6305,resp=0,Login,fnac76.eb.lab
The Persistent Agent responded with the credentials:
2025-12-12 15:26:07 UTC :: Submitted,req=42,resp=0,Authenticate,fnac76.eb.lab
2025-12-12 15:26:07 UTC :: Sent,req=42,resp=0,Authenticate,fnac76.eb.lab
A similar result can also be checked in 'C:\ProgramData\Bradford Networks\generatl.txt'.
FortiNAC requested the login credentials from the device and the pop-up appears:
2025-12-12 15:24:42 UTC :: constructFromBufer verb = Login
2025-12-12 15:24:42 UTC :: handleReceivedPacket() -- received this packet:
Login
END of packet
The Persistent Agent responded with the credentials:
2025-12-12 15:26:06 UTC :: IPC Verb = AUTH
2025-12-12 15:26:07 UTC :: SslStreamTransport::sslSendThread calling sendImpl()
2025-12-12 15:26:07 UTC :: SslStreamTransport::sslSendThread calling take()
If the pop-up window takes too much time to be requested by FortiNAC, it may be necessary to check the CPU and memory utilization of the FortiNAC.
Related articles:
Technical Tip: Disable Persistent Agent Credentials Pop Up Window
Troubleshooting Tip: Agent logs on end hosts
Technical Tip: Persistent Agent communication ports
Technical Tip: Manually install and configure 'Persistent Agent' on Windows OS
|
