Folks,

The solution today is to instruct/educate the users to "disable the
wireless when connected to wired". 
We are working on a short and long term solution to this. 

We apologize for any inconvenience caused.

Regards,
Nick  

-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of Lanstein, Alex C
Sent: Thursday, April 12, 2007 8:08 AM
To: [log in to unmask]
Subject: Re: Agent behavior while connected to wired and wireless
networks

We have that issue here.  We have a program through dell so most of the
PCs are dells.  dell has a sweet app called "quickset" that handles most
of the headaches like that.  it has a setting to disable the wireless
when the wire is plugged in.  
 
like you said though, it's a user education issue until m$/cisco change
their software, which I don't see happening
 
Regards, 
 
Alex Lanstein
Senior Software Engineer, Transitional Data Services Help Desk/Network
Junkie, Connecticut College BOFH, LBCCHosting
860-625-4277
[log in to unmask]

________________________________

From: Cisco Clean Access Users and Administrators on behalf of David
Stempien
Sent: Thu 4/12/2007 10:25 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