Single alert produces Session denied multiple DC servers LDAP 389 and why ?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Single alert produces Session denied multiple DC servers LDAP 389 and why ?

Hi,
Login Successful After Scan Attempt 
I have a question regarding when user connecting VPN --which means session denied for multiple DC servers--Via global protect VPN. 
SourceZone:GP-c
Type -TRAFFIC
Denied Port-389 which means LDAP.

Session End Reason-policy-deny
@everyone

once the user connected VPN with successful authentication Why scanning happening?

 

2 REPLIES 2

L3 Networker

What type of scan is happening? 

We observed multiple DC servers  from one SRC machine to Multiple DST DC servers IP are captured and for the port 137 & 389 all the sessions are denied when user facing VPN issues. 

  • 344 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!