Security

Reply
MVP

Re: CPPM AD Authentication Error Message : Reading windind reply failed!

That solved my problem.

 

I specified a specific domain controller and I was able to join our CPPM's.

 

As well now the clients auth. as expected

 

Thanks for all the help and sorry for all the questions!

Guru Elite

Re: CPPM AD Authentication Error Message : Reading windind reply failed!

Nice, no problem!


Just be sure to add multiple domain controllers to your authentication source with the "Backup server" option.


| Tim Cappalli | Aruba Security | @timcappalli | timcappalli.me |

NOTE: Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba or Hewlett Packard Enterprise.
MVP

Re: CPPM AD Authentication Error Message : Reading windind reply failed!

Yeah that is an awesome feature I was that when I was creating the source for the first time!

I have since added in 2 additional DC's as a backup. Very cool feature!

 

One thing I did notice with the AD auth. source is that it doesn't seem to like the FQDN of either the domain or of a specific domain controller. We ended up having to use IP's only.

 

Not sure if that is normal behavior or not.

 

Thanks again!

 

Cheers

Guru Elite

Re: CPPM AD Authentication Error Message : Reading windind reply failed!

Hm. You definitely should be able to use FQDN. Is ClearPass pointed at your AD DNS?

| Tim Cappalli | Aruba Security | @timcappalli | timcappalli.me |

NOTE: Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba or Hewlett Packard Enterprise.
MVP

Re: CPPM AD Authentication Error Message : Reading windind reply failed!

It is point at the new AD DNS servers.

 

At first it wasn't. It was still using our old DNS servers. But we modified everything to point at the DNS of our AD servers.

 

We even went onto the command line of the CPPM and used nslookup to make sure everything would resolve correctly and it was working without an issue.

 

But for some reason when we use anything other than the IP it says that it cannot connect to the server on port 389.

 

I wonder if now that the CPPM is apart of the domain it will work correctly?

 

I should give that a try.

 

---------------------------------  EDIT

 

I was wrong.

Even after joining it doesn't let me use the FQDN.

 

Strange.

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: