More information. I found the same issue happened to a user in a different CAS today. The log showed she was kicked out early moring during the routine weekly re-authentication. Then she can't get back on and got 12029 error. Today, I decided rather than rebooting CAS. I removed the IP from dhcp. When she got a brand new IP, then she was able to get on fine now. So, I assume the CAS db must be somewhat confused and that maybe why it worked in different CAS and also after we reboot the CAS. Any suggestions besides reinstalling the software? It only happens to couple users a week out of 4-5K. The timer setting is to kick the oldest 1000 users per day and the user minimum certifcation age is 7 days. Thanks.
________________________________________ From: Cisco Clean Access Users and Administrators [EMAIL PROTECTED] On Behalf Of SHIH, WENDY [EMAIL PROTECTED] Sent: Thursday, October 02, 2008 12:02 PM To: [email protected] Subject: Re: CCA getting error 12029 In our case, we only get that error on a very few users out of 4 subnets in a particular pair of CAS (v.4.1.3.1). We tried all common troubleshooting and found if we move the users to a different pair of CAS, then they work immediately. We had to reboot that CAS 3 times this semester for clients to work and not sure what causes it yet. The other 9 pair of CAS(s) have not experienced any of the 12029 error. -----Original Message----- From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On Behalf Of Ben Fielden Sent: Thursday, October 02, 2008 11:09 AM To: [email protected] Subject: Re: CCA getting error 12029 We see 12029 ALL the time. In every single case I have seen, it has been that the user is plugged into our CCA port and is also associated with our non-CCA wireless network. Disabling the wifi card has always worked for us. Ben Fielden ISS Student Technology Services The George Washington University David Pifer wrote: > Recently we have seen a round 12029 'Can't connect' errors on some > machines when running the CCA client. It comes and goes. Anyone seen > this error before? > > > About the same time we also started to see 12057 errors regarding the > cert revocation not being around. This one I know how to fix. It all > started last Wednesday... funny after a MS patch update.... Hmmm...... > Maybe these are related...... > > We are at 4.1.3.1 on the Engines and 4.1.3.2 on the clients. > > > > David L. Pifer - N9YNF - CCNA > Network Engineering Services > Indiana State University, Office of Information Technology > 210 N. 7th St., Rankin Hall R044, Terre Haute, IN 47809 > 812.237.2923 office 812.237.4361 fax
