- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
01-22-2021 02:11 AM
Hello everyone,
I installed a PTA agent (version 1.0.62)on each Windows Collector server and it is working well.
Now I'm deploying the PTA agent on DC controller (we bought the license for that) and activate the network inspection on the network ldap.
The agent is working a while but after a certain period of time, depending of the load for LDAP, Kerberos, etc, the agent is crashing.
The INI file:
[Forwarder]
Windows_Event_Log=ForwardedEvents
[ServerInfo]
PTA_IP_Address=XXXXXXXXXXXXX
SSL_Data_Port=6514
SSL_Control_Port=7514
Data_Port=11615
[DCInfo]
Network_Interface_ID=1
Server_Verification_Required=true
Windows_Event_Enabled=false
Network_Enabled=true
[ClientCertificate]
Client_Certificate_Enabled=true
Client_Certificate_Subject_Name=XXXXXXXXXXXXX
[Debug]
Write_Events_To_Log=true
Faulting application name: PTAAgent.exe, version: 1.10.0.62, time stamp: 0x5f16add0
Faulting module name: ntdll.dll, version: 10.0.14393.3986, time stamp: 0x5f77edb8
Exception code: 0xc0000005
Fault offset: 0x0003a4f3
Faulting process id: 0x1420
Faulting application start time: 0x01d6e4d0721c22ea
Faulting application path: C:\Program Files\CyberArk\PTA Agent\PTAAgent.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: c58f5b77-a9c9-422e-9174-94fde8120cf6
Faulting package full name:
Faulting package-relative application ID:
I created the exception for the AV. But nothing has changed.
Do you think that it is related that I received a strange traffic on the network interface and crashing the agent?
03-15-2021 11:57 AM
Yes sorry for my late answer.
The fix from the support was to add a [Debug] section with the following parameters:
This is our jinja template to deploy the agent:
[Forwarder]
Windows_Event_Log=Security
[ServerInfo]
PTA_IP_Address= {{ pta_server }}
SSL_Data_Port=6514
SSL_Control_Port=7514
Data_Port=11615
[DCInfo]
Network_Interface_ID=1
Server_Verification_Required=true
Windows_Event_Enabled=true
Network_Enabled=true
[ClientCertificate]
Client_Certificate_Enabled=true
Client_Certificate_Subject_Name={{ cert_subject }}
[Debug]
Packet_Filter="not tcp port 445 and less 2000"
Max_Fragments_Number=4
Hope it will help you.
01-22-2021 09:47 AM
We are facing the same issue with PTA Agent crashing after a couple minutes working, we already opened a case and no solution yet.
01-25-2021 02:27 AM
I escalated the case, I will keep you informed if we found something.
03-11-2021 12:14 PM
Hi @Gregory Schildknecht did you get a solution on this?
03-15-2021 11:57 AM
Yes sorry for my late answer.
The fix from the support was to add a [Debug] section with the following parameters:
This is our jinja template to deploy the agent:
[Forwarder]
Windows_Event_Log=Security
[ServerInfo]
PTA_IP_Address= {{ pta_server }}
SSL_Data_Port=6514
SSL_Control_Port=7514
Data_Port=11615
[DCInfo]
Network_Interface_ID=1
Server_Verification_Required=true
Windows_Event_Enabled=true
Network_Enabled=true
[ClientCertificate]
Client_Certificate_Enabled=true
Client_Certificate_Subject_Name={{ cert_subject }}
[Debug]
Packet_Filter="not tcp port 445 and less 2000"
Max_Fragments_Number=4
Hope it will help you.
03-15-2021 12:53 PM
Hi @Gregory Schildknecht thank you.
Did you notice any lost of information on the PTA Security Warnings when using the Packet_Filter="not tcp port 445 and less 2000" ?
03-16-2021 03:37 AM
The support confirms me that it was enough to detect / analyze the traffic by the agent.
I asked the same question to the support and we must not have any information lost for the DC protection.
03-17-2021 09:26 AM
Thanks for the reply Gregory. It was very helpful
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

