CLEANACCESS Archives

December 2009

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:
Brian Beausoleil <[log in to unmask]>
Reply To:
Cisco Clean Access Users and Administrators <[log in to unmask]>
Date:
Thu, 10 Dec 2009 13:28:55 -0500
Content-Type:
multipart/mixed
Parts/Attachments:
I am having trouble with our iPod Touch/iPhone users on our wireless network.  They receive an ip address and get redirected to the authentication page.  In testing the issue with an iPod Touch, I receive the following error message when I submit my username and password in the form... "Hotspot login cannot open the page because the server cannot be found."  We have 2 SSID's and it happens on both of them.  If I put an allow all rule on the unathenticated role (or a filter), I can surf the web like a normal user.  I have restarted the CAS HA pair and CAM HA pair related to the wireless network.    Another thing to note is this happens with a local account or an AD account.

My environment is...
CAS: 4.1.8
CAM: 4.1.8
Mac Agent: 4.1.3.1
Windows Agent: 4.1.10.0

The Mac Agent is turned off at the moment for the Snow Leopard work around.  This was all working fine until a weeks days ago when we began hearing reports trickle in about iPods not connecting to the wireless.  We dismissed the first couple as end-user error since we do not support personal devices at this time.  I had a filter on my iPod so I wasn't aware or affected by this issue, but am now that I removed my filter for testing.

I have attached some screen shots that I felt were related to this issue to help troubleshoot and diagnose the issue.  I have almost exhausted everything related to the NAC that I can think of.  

Tac has logged into all our servers and cannot find anything wrong on their end, so the last thing would be to suspect the iPod's as the issue.  I am not aware of any updates that may have "broken" them either.  

Has anyone experienced this issue or have any suggestions on something else to look for?

Thanks in advance.

Brian










ATOM RSS1 RSS2