Authentication problem with ACS 4.1 TACACS+ (Windows Server 2000
From the logs you’ve provided “TCS 09/07/2012 17:23:10 I 1312 3296 0x3e Cannot connect to TACACS+ server on :49” it appears that your TACACS services is down.
Since you’ve restart the CSAdmin services, and reboot the server, and this still doesn’t help, I can only assume that this is a bug issue. Please patch it with ACS for Windows 220.127.116.11.20 cumulative patch (Release Date: 14 Nov 2009).
However, before you proceed to patch your Cisco ACS 4.1, try to increase the TACACS+/RADIUS timeout interval from the default, 5, to 20 in your Cisco devices.
tacacs-server timeout 20
radius-server timeout 20
By the way, have you recently patch your Windows 0/S with any Service Packs or updates etc. This could be another possible cause, as well.
P/S: If you think this comment is useful, please do rate them nicely :-)
Ramraj Sivagnanam Sivajanam
Technical Specialist/Service Delivery Manager – Managed Service Department
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...