I have seen this 12029 error when MacAfee access protection is enabled
was the clean access agent is blocked by MacAfee.  I open the virus scan
console and click the red stop button access protection. 
Tracey

-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of Osborne, Bruce W.
(NS)
Sent: Thursday, October 02, 2008 12:28 PM
To: [log in to unmask]
Subject: Re: CCA getting error 12029

Wendy,

Maybe you need to reinstall the CASs. Sometimes old changes still
"stick" on the CAS.

One time when I accidentally configured the CAS as In-Band, TAC
recommended reinstalling it because some erroneous settings would still
remain on the CAS.


Just a thought,

Bruce Osborne
Liberty University

-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of SHIH, WENDY
Sent: Thursday, October 02, 2008 12:02 PM
To: [log in to unmask]
Subject: Re: [CLEANACCESS] 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:[log in to unmask]] On Behalf Of Ben Fielden
Sent: Thursday, October 02, 2008 11:09 AM
To: [log in to unmask]
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