CLEANACCESS Archives

April 2007

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:
"Joyce, Todd N" <[log in to unmask]>
Reply To:
Cisco Clean Access Users and Administrators <[log in to unmask]>
Date:
Thu, 12 Apr 2007 10:36:53 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (71 lines)
Right click on the clean access agent and turn off pop up 

That is the suggestion we always use.

todd

Todd Joyce
Network Services
Radford University - The Smart Choice
[log in to unmask]
(540) 831-7777
 
Keep your boots and ChapStick and ice hotels.
Give me shorts and sandals and a thirty-blocker.

Temperance Brennan - Monday Mourning
-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of David Stempien
Sent: Thursday, April 12, 2007 10:26 AM
To: [log in to unmask]
Subject: Agent behavior while connected to wired and wireless networks

Scenario:

A user has a laptop which is plugged into a wired connection (non-CCA)
and a
wireless connection (CCA).  Both interfaces are active.

If the user has not-yet-authenticated with the Clean Access Agent, it
will
pop up and ask the user to do so.  User does, but the agent either keeps
popping back up to ask for credentials again and again, or it eventually
times-out with an error 500.  I assume the agent is discovering the
Clean
Access server on the wireless connection, but it is sending its traffic
to
the Clean Access server out of the preferred wired connection, thus
causing
this behavior.

If the user was using wireless-only and had successfully logged into
CCA,
then later plugged into the wired connection, there's no harm done.
Although I suspect when we later migrate the wired connection to CCA we
will
experience additional pains regarding interface confusion within the CCA
agent.


Question:

Obviously, this is a user training issue (if you're using a wired
network
connection, shut off your wireless first).  Until Microsoft fixes this
behavior with their wireless network control or Cisco makes the agent
interface-aware or we recommend a third-party wireless supplicant which
can
automagically shut down the wireless interface, I'm wondering if anyone
else
might have and idea for another technical solution for this problem?


Thanks,

--
Dave Stempien, Network Security Engineer
University of Rochester Medical Center
Information Systems Division
585-784-2427

ATOM RSS1 RSS2