Jump to content

Troubleshooting Web Authentication

  • PrintPrint

Information

Procedure to troubleshoot Cisco Wireless LAN Controller (WLC) web authentication issues.

Details

From the Cisco website Troubleshooting Web Authentication on a Wireless LAN Controller (WLC) document:
Troubleshooting Web Authentication
After user configures web authentication, if the feature does not work as expected, complete these troubleshooting steps:
  1. Check if the client gets an IP address. If not, users can uncheck DHCP Required on the WLAN and give the wireless client a static IP address. This assumes association with the access point. Refer to the IP addressing issues section of Troubleshooting Client Issues in the Cisco Unified Wireless Network for troubleshooting DHCP related issues .
  2. On WLC versions earlier than 3.2.150.10, user must manually enter https://1.1.1.1/login.html in order to navigate to the web authentication window.
    The next step in the process is DNS resolution of the URL in the web browser. When a WLAN client connects to a WLAN configured for web authentication, the client obtains an IP address from the DHCP server. The user opens a web browser and enters a website address. The client then performs the DNS resolution to obtain the IP address of the website. Now, when the client tries to reach the website, the WLC intercepts the HTTP Get session of the client and redirects the user to the web authentication login page.
  3. Therefore, ensure that the client is able to perform DNS resolution for the redirection to work. On Windows, choose Start > Run , enter CMD in order to open a command window, and do a nslookup www.cisco.com and see if the IP address comes back.
    On Mac/Linux: open a terminal window and do an nslookup www.cisco.com and see if the IP address comes back.
    If user believes the client is not getting DNS resolution, user can either:
    • Enter either the IP address of the URL (for example, http://www.cisco.com is http://198.133.219.25 ).
    • Try to directly reach the controller's webauth page with https://<Virtual_interface_IP_Address>/login.html . Typically this is http://1.1.1.1/login.html .
    Does entering this URL bring up the web page? If yes, it is most likely a DNS problem. It might also be a certificate problem. The controller, by default, uses a self-signed certificate and most web browsers warn against using them.
  4. For web authentication using customized web page, ensure that the HTML code for the customized web page is appropriate.
    User can download a sample Web Authentication script from Cisco Software Downloads. For example, for the 4400 controllers, choose Products > Wireless > Wireless LAN Controller > Standalone Controllers > Cisco 4400 Series Wireless LAN Controllers > Cisco 4404 Wireless LAN Controller > Software on Chassis > Wireless Lan Controller Web Authentication Bundle-1.0.1 and download the webauth_bundle.zip file .
    These parameters are added to the URL when the user's Internet browser is redirected to the customized login page:
    • ap_mac—The MAC address of the access point to which the wireless user is associated.
    • switch_url—The URL of the controller to which the user credentials should be posted.
    • redirect—The URL to which the user is redirected after authentication is successful.
    • statusCode—The status code returned from the controller's web authentication server.
    • wlan—The WLAN SSID to which the wireless user is associated.
    These are the available status codes:
    • Status Code 1: "You are already logged in. No further action is required on your part."
    • Status Code 2: "You are not configured to authenticate against web portal. No further action is required on your part."
    • Status Code 3: "The username specified cannot be used at this time. Perhaps the username is already logged into the system?"
    • Status Code 4: "You have been excluded."
    • Status Code 5: "The User Name and Password combination you have entered is invalid. Please try again."
  5. All the files and pictures that need to appear on the Customized web page should be bundled into a .tar file before uploading to the WLC. Ensure that one of the files included in the tar bundle is login.html . User receives this error message if user does not include the login.html file:
    Refer to the Guidelines for Customized Web Authentication section of Wireless LAN Controller Web Authentication Configuration Example for more information on how to create a customized web authentication window.
    NOTE: Files that are large and files that have long names will result in an extraction error. It is recommended that pictures are in .jpg format.
  6. Internet Explorer 6.0 SP1 or later is the browser recommended for the use of web authentication. Other browsers may or may not work.
  7. Ensure that the Scripting option is not blocked on the client browser as the customized web page on the WLC is basically an HTML script. On IE 6.0, this is disabled by default for security purposes.
    NOTE:The Pop Up blocker needs to be disabled on the browser if you have configured any Pop Up messages for the user.
    NOTE: If you browse to an https site, redirection does not work. Refer to Cisco bug ID CSCar04580 (registered customers only) for more information.
  8. If user has a host name configured for the virtual interface of the WLC, make sure that the DNS resolution is available for the host name of the virtual interface.
    NOTE:Navigate to the Controller > Interfaces menu from the WLC GUI in order to assign a DNS hostname to the virtual interface.
  9. Sometimes the firewall installed on the client computer blocks the web authentication login page. Disable the firewall before accessing the login page. The firewall can be enabled again once the web authentication is completed.
  10. Topology/solution firewall can be placed between the client and web-auth server, which depends on the network. As for each network design/solution implemented, the end user should make sure these ports are allowed on the network firewall:
    ProtocolPort
    HTTP/HTTPS TrafficTCP port 80/443
    CAPWAP Data/Control TrafficUDP port 5247/5246
    LWAPP Data/Control Traffic (before rel 5.0)UDP port 12222/12223
    EOIP packetsIP protocol 97
    MobilityUDP port 16666 (non secured) UDP port 16667 (secured IPSEC tunnel)
  11. For web authentication to occur, the client should first associate to the appropriate WLAN on the WLC. Navigate to the Monitor > Clients menu on the WLC GUI in order to see if the client is associated to the WLC. Check if the client has a valid IP address.
  12. Disable the Proxy Settings on the client browser until web authentication is completed.
  13. The default web authentication method is PAP. Ensure that PAP authentication is allowed on the RADIUS server for this to work. In order to check the status of client authentication, check the debugs and log messages from the RADIUS server. User can use the debug aaa all command on the WLC to view the debugs from the RADIUS server.
  14. Update the hardware driver on the computer to the latest code from manufacturer's website.
  15. Verify settings in the supplicant (program on laptop).
  16. When using the Windows Zero Config supplicant built into Windows:
    • Verify user has latest patches installed.
    • Run debugs on supplicant.
  17. On the client, turn on the EAPOL (WPA+WPA2) and RASTLS logs from a command window, Start > Run > CMD :
    netsh ras set tracing eapol enable
    netsh ras set tracing rastls enableIn order to disable the logs, run the same command but replace enable with disable. For XP, all logs will be located in C:\Windows\tracing .
  18. If user still has no login web page, collect and analyze this output from a single client:
    debug client <mac_address in format xx:xx:xx:xx:xx:xx>debug dhcp message enabledebug aaa all enabledebug dot1x aaa enabledebug mobility handoff enable
  19. If the issue is not resolved after completing these steps, collect these debugs and use the TAC Service Request Tool (registered customers only) in order to open a Service Request:
    debug pm ssh-appgw enabledebug pm ssh-tcp enabledebug pm rules enabledebug emweb server enabledebug pm ssh-engine enable packet <client ip>
The preceding information can be found in the below given document:

Disclaimer

NOTE: One or more of the links above will take you outside the Hewlett-Packard Web site, HP does not control and is not responsible for information outside of the HP Web site.

HP Support forums

Find solutions and collaborate with others on the HP Support Forum
HP.comHP on FacebookHP on TwitterHP on YouTubeHP on Linked InHP on FlickrHP on Google+