CLEANACCESS Archives

October 2008

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ben Fielden <[log in to unmask]>
Reply To:
Cisco Clean Access Users and Administrators <[log in to unmask]>
Date:
Thu, 2 Oct 2008 11:09:19 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
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

ATOM RSS1 RSS2