Hey Robert, Isabelle,

This usually happens when the client has an old agent but the NAC Server
has the same agent with a wrong version number when the agent was
uploaded  manually. For example, end user is using 4.1.3.0 and the NAC
Server is also having a 4.1.3.0 agent but when someone uploads it, they
tell the system that it is a 4.1.3.1 agent. This will cause the loop.
This is one possibility.

To find out the actual cause, I will need the agent log.

Thanks
-Alok

-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[email protected]] On Behalf Of Isabelle Graham
Sent: Tuesday, March 03, 2009 12:34 PM
To: [email protected]
Subject: Re: Mac Agent problems

We had this same problem here (as I remember, it's been some time since
I've tested it). We opened a 
TAC case but haven't heard back about a work-around. I've since done
some testing with running the 
4.5 agent for Mac (with the 4.1.2.1 server) and it seems to work fine. I
know that agent/server 
combination is supported, but I'm not sure what the licensing
restrictions might be on distributing 
the 4.5 client if you are still licensed for 4.1.

----
Isabelle Graham
Information Security
American University

Robert J. Rutkowski wrote:
> I have an issue that I can't find a way to get around. We are
currently
> running CAS/CAM 4.1.2.1 with the Windows agent at 4.1.8.0 and Mac
agent
> at 4.1.3.1. I just changed the Windows agent yesterday, because we
were
> having problems with the older version not correctly identifying AV
> definition dates. Today Macintosh users are having problems with their
> agents. When you attempt to login you receive a box stating that "A
> newer version is available!" and you have no choice but to upgrade the
> agent. The problem is that there is not an update for the Mac agent.
The
> updater just installs 4.1.3.1 over the existing 4.1.3.1 and then
> displays the newer version available box again. They seem to be stuck
in
> this loop, with no way around it.
> 
>  
> 
> The only way I have found to stop the loop is to check the box on the
> CAM to not offer current Clean Access Agent Patch to users for
upgrade.
> If I check that box then my Windows users won't get the newest agent
> though, and I'm back with the problem I had yesterday. 
> 
>  
> 
> I don't know if anyone has run into this before or has any advice. I'd
> appreciate anything at this point.
> 
>  
> 
> Thank you,
> 
>  
> 
> Robert J. Rutkowski
> 
> Network Administrator
> 
> Keystone College
> 
> (570) 945-8204
> 
> [email protected] <mailto:[email protected]>  
> 
>  
> 
> 

Reply via email to