PaloAlto does not pass through itself a request for AD

[ArtemTokarenko]

Hi !

I have problem with connection PC to AD between which stands PaloAlto

PC 192.168.10.10
AD 192.168.30.40 (loc.lab)
pings go from  PC  to AD 192.168.30.40 (loc.lab) and return successfully
pings go from  PC  to loc.lab (192.168.30.40) and return successfully

But when I try to connect a PC with a local account enter into the domain i get

 

when i transfer pc to network 30 i successfully connect to AD

 

  

 

 

[OtakarKlier]

Hello,

My guess is that the Palo Alto is blocking the traffic. Make sure there is a policy that allows the traffic to/from the Domain Controllers to the subnet the PC is on. Enable logging on all policies and use the Traffic logs to check for blocks, etc. Also from one of the screenshots, looks like the LDAP is still set to use the default ,eg the management interface.

Regards,

[laurence64]

I agree with @OtakarKlier I would check for dropped traffic, although as pointed out definately in the screenshot the route for LDAP is the MGMT interface so you would have to check which firewall that traffic is going through and this is the intended route.

[Arnesh]

Hi @ArtemTokarenko 

When you say "after transfer pc to network 30 i successfully connect to AD", what is the network configured on the PC in which the connection fails?
I would check the routing table on the PC when configured in the problematic network to see if the traffic is forwarded to the firewall? (Basically, tracing the traffic)

**My understanding says -- The service-route settings is for the management-plane traffic. If we are just concerned about the traffic between PC <--> AD, then we can rest assured that the service will not be used.

Regards,

[laurence64]

I think you are right that this may be simply connecting the PC to the domain, but looking at the rule base, all rules are completely open, this would suggest that any connected network that has a route to the AD server should be OK, I am just wondering if it is the PC or the firewall that the AD connection is for, if @ArtemTokarenko was not trying to connect the firewall then why show the LDAP config on it, however the error message is not from the Palo.

Could you provide some more context please @ArtemTokarenko 

[ArtemTokarenko]

Hello everyone, I could not understand what is the reason for this problem, I created another Win10 VM and everything was fine. Microsoft Magic