Talk:Cisco NAC Appliance

I'm thinking that the title should be changed from the current "Clean access agent" to "Clean Access Agent" (caps on the first letter of each word) so as to bring this entry in-line with the (apparent) wikipedia formatting. Still being relatively new to wikipedia editing, I don't see that I can make such a change myslef (but I may just be missing it). -7/17/06 Thorprime


 * Moved --Thorprime 16:58, 27 July 2006 (UTC)

As the article cites it is quite common in university and corporate environments, I would like to see examples cited of universities that have this in place (even though U. Miami is linked to in the references section). 70.169.13.71 20:09, 1 December 2006 (UTC)
 * Bridgewater State College (MA) uses it, unfortunately.207.206.238.253 (talk) 14:23, 13 May 2009 (UTC)

It was recently put into affect at the University of Louisville--this fact I disdain. I've never hated using Windows more in my life.

I am a student at McMaster University, and everyone is forced to connect to the wireless internet through clean access agent. It is very difficult to connect to the internet, and a lot of students can't even use their personal laptops. Most of the time it takes a few reconnects and reboots to be able to get through the access agent. This is an absolute horrible system, it should be treated as a virus. Disgusting

Advert-speak?
"helps ensure a secure and clean network environment" .. This sounds like it came directly from cisco's mouth. The appliance forces clients to run antivirus software and windows update- that does not make for a "clean" network environment, whatever that means. A clean network environment is the standardized handshake and direct connection to the internet. That's clean. What's not clean is forcing clients to run some proprietary, closed-source software just to connect to the network when their OS and computer are already perfectly networking-capable. It goes against all ideas of encapsulation and modular design, and while IT departments might be forced to resort to it because of user complaints about the amount of traffic on the network consumed by viruses spreading themselves or whatever (seems hard to believe..) they have to know that it makes their "network environment" no more secure whatsoever than before, it just forces clients to take care of themselves (which is none of the network's business). At least add a criticisms section- quote me directly! Public Domain'd. Take it. --⁪frotht 22:26, 22 August 2007 (UTC)

Clean access agent is horrible. Not user friendly at all, they should never —Preceding unsigned comment added by 130.113.172.53 (talk) 19:10, 26 September 2008 (UTC)

Help?
Anyone have any luck getting online on Windows 7 in a place that requires Clean Access Agent? I can easily get on Ubuntu (without the program), but I can't get online (more than local access only, which lets me go to like 2 pages) with Windows 7, which I have had since the pre-beta started. I am hoping that now that anyone can play with the Windows 7 RC that someone has figured something out. 207.206.238.253 (talk) 14:23, 13 May 2009 (UTC)

Had same problem here. Cisco does not support Windows 7 yet. Now I'm stuck with a new computer for college without internet access. Thanks Cisco! —Preceding unsigned comment added by 132.161.1.151 (talk) 20:35, 27 August 2009 (UTC)

4.7.1 cam/cas and client or higher is required for WIN 7 support Note: Windows 7 Starter is not supported. The Cam/Cas means that you need to upgrade the server side of the software as well, not just the client. --Typhoon87 (talk) 02:43, 5 January 2010 (UTC)

Gaming consoles and MAC spoofing
This section reads like a 2600 article. It needs references or it's going to be purged and/or published in 2600. --Stybn (talk) 20:30, 13 January 2010 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 4 external links on Cisco NAC Appliance. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20060829121851/http://www.cisco.com/univercd/cc/td/doc/product/vpn/ciscosec/cca/cca36/36rn.htm to http://www.cisco.com/univercd/cc/td/doc/product/vpn/ciscosec/cca/cca36/36rn.htm
 * Added archive https://web.archive.org/web/20071012021701/http://cisco.com/en/US/products/ps6128/prod_release_note09186a008085b16f.html to http://www.cisco.com/en/US/products/ps6128/prod_release_note09186a008085b16f.html
 * Added archive https://web.archive.org/web/20060829121851/http://www.cisco.com/univercd/cc/td/doc/product/vpn/ciscosec/cca/cca36/36rn.htm to http://www.cisco.com/univercd/cc/td/doc/product/vpn/ciscosec/cca/cca36/36rn.htm
 * Added archive https://web.archive.org/web/20070306201855/http://www.cisco.com/warp/public/707/cisco-sr-20060826-nac.shtml to http://www.cisco.com/warp/public/707/cisco-sr-20060826-nac.shtml

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 20:16, 11 January 2018 (UTC)