I Mavhu,
If you run the 4.1.2.2 agent, and want it to work on 64 bit machines, you MUST
run the 4.1.2.1 CAM/CAS version.
RELEASE NOTES:
The 4.1.2.2 Agent performs authentication only for 64-bit Windows Vista and
Windows XP client operating systems. Once the user is authenticated, the Agent
does not perform posture assessment or remediation. To support 64-bit
operating system Agents, the CAM and CAS must also be running release 4.1.2.1.
Because Cisco NAC Appliance provides authentication-only support for 64-bit
operating system Agents, nessus scanning via the Clean Access Agent does not
perform remediation on the client machine.
-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of Chidaushe, Mavhu
Sent: Friday, October 26, 2007 3:07 PM
To: [log in to unmask]
Subject: Re: New Agent
We did some testing with the latest agent version 4.1.2.2 and it turns out
it does not work at all with Vista x64 bit editions. It fails to login and
outputs the following error:
"Login Failed!
Detail: This client version is old and not compatible. Please login from the
web browser to see the download link for the new version"
We are running CAM/CAS version 4.1.2.0
L2 in-band
We are going to keep using agent version 4.1.2.0 for all our users.
Mavhu Chidaushe
Communications Network Analyst
University Networking Systems and Services
South Dakota State University
Old Horticulture #206a
-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of Bradley W. Kramer
Sent: Friday, October 12, 2007 1:01 PM
To: [log in to unmask]
Subject: Re: New Agent
We are having similar problems with 4.1.2.2 here, users are getting
about 10 minutes of connectivity followed by 10 minutes of non-
connectivity... We are forcing a back-rev on all of our agents... we
have a significant amount of students having this problem and the
only thing that has changed in ResNet this week is our CCA version.
Please keep us posted, i am convinced it could be spyware or
something conflicting with the agent, however firewall is not the
issue, i could reproduce the problem with no av/firewall installed on
a freshly installed system....
-Brad Kramer
On Oct 12, 2007, at 10:06 AM, Simon Kissler wrote:
> Any chance there's a host firewall that keys in on the application
> binary (incl. version) and isn't letting the new version talk/
> receive network traffic ? I've seen that before where the firewall
> needed to be configured again to allow traffic when the agent
> updated (although haven't seen it for some time).
>
> -S
>
>
> >>> On 10/12/2007 at 8:54 AM, Jeff Stewart <[log in to unmask]>
> wrote:
> Nope, with the old agent it logs in, with the new agent I don't have
> that option.
>
> Osborne, Bruce W. (NS) wrote:
> > Since it is a Sony Vaio, is CCA forcing it into your game console
> role?
> >
> > Check the MAC address in your filters.
> >
> > Bruce Osborne
> > Liberty University
> >
> > -----Original Message-----
> > From: Cisco Clean Access Users and Administrators
> > [mailto:[log in to unmask]] On Behalf Of Jeff Stewart
> > Sent: Friday, October 12, 2007 9:23 AM
> > To: [log in to unmask]
> > Subject: [CLEANACCESS] New Agent
> >
> > Has anyone had any trouble with the latest agent release? I have a
> > machine where agent 4.1.2.1 works fine but as soon as I upgrade to
> > 4.1.2.2 the agent stops working. Looks like the agent is running
> but
> > the login is grayed out. It's a Sony Vaio running Vista.
> >
> > Jeff
> >
> >
>
> --
> Jeff Stewart
>
> Network Engineer
> Network Computing & Support
> Western Kentucky University
|
