Patch/Reboot of AD servers requires restart of ACS 4.2 Windows Service

[spinnabs1]

We have been experiencing an ACS issue when our Active Directory servers are patch and rebooted. When this is done, the ACS service must be restarted on both our ACS servers. The ACS servers are Windows 2003 with ACS 4.2. Has anyone else experienced this? If so, any solution?

[Jatin Katyal]

So after patching/rebooting AD server, the authentication starts failing and you need to restart ACS services to fix the problem. Do you only need to restart csauth or all services from services.msc?

~BR
Jatin Katyal

**Do rate helpful posts**

[spinnabs1]

Use the "restart service" from inside the ACS web interface.

There are 16 AD servers, they patch/reboot the even ones first and then the odd ones.

[blenka]

Does it mean if you restart the AD you are forcefully required to restart the ACS ?

or else is it working fine ? if yes I would suggest look for physical connection or change the switch port.

Or it may IP conflict !

[spinnabs1]

The ACS will respond to local database queries fine, it is when it relays it to the active directory cluster that it fails. The ACS servers are on different subnets in different data centers, same with the AD servers. I checked the switch ports and have found no errors and no indication of dupe IP’s. In the ACS logs, is see the fail error as either a “External DB user invalid or bad password” or “External DB unknown error”.