WinRM-HTTP Connection Refused

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

WinRM-HTTP Connection Refused

L2 Linker

Hello,

 

I'm using agentless user-id with a Windows Server 2012 AD through WMI, we recently updated the server, and it started throwing Authentication Error 10036 flooding our Windows logs. We've searched and troubleshooted the problem for a long time and nothing worked, the only workaround that we think might work is to change the authentication protocol from WMI to WinRM-HTTP. (We cannot roll back the update for vulnerability requirements)

 

We used this guide https://docs.paloaltonetworks.com/pan-os/9-0/pan-os-admin/user-id/map-ip-addresses-to-users/configur... to set up the configuration, and once we committed we're getting "Connection Refused(0)". The user-id logs are not specifying the error, just a "connection failed, error=0"

Likewise, we also troubleshooted everything, from the configs to the service account having the correct permissions as per Palo Alto's recommendation, and still.

 

Any ideas?

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hello,

We weren't able to solve the issue using WinRM HTTP, we did however migrate from PAN-OS Integrated User-ID agent to Windows User-ID Agent which solved the Authentication Error 10036 isuue.

View solution in original post

7 REPLIES 7

L7 Applicator

I also changed from wmi to winrm and seems ok...   have you tested your kerberos profile?

Yes, and it was successful.

L0 Member

Hello,

happy new year !

We have exactly the same issue...

Everything is configured by following Palo's instructions, but always "Connection refused (0)"

Any ideas?

@echahine have you solved on your side ?

Thank's

Hello,

We weren't able to solve the issue using WinRM HTTP, we did however migrate from PAN-OS Integrated User-ID agent to Windows User-ID Agent which solved the Authentication Error 10036 isuue.

L0 Member
Hi,
Thank you very much for the information, now it works with Windows User-ID Agent !
Why do Palo make PAN-OS Integrated User-ID agent available if it doesn't work ...
Have a nice day

It's actually a Windows hardening issue. But you're right Palo Alto should be compatible with these hardenings already since it's an old recurring issue.

 

Glad to help!

L0 Member

 

Hello,

You'll need a policy rule from the management IP to the domain servers, remember that it does not use the default port, so you must define "any" in "service/url category". 

 

EnricRipoll_0-1661165148934.png

 

bye,

 

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!