Security

last person joined: 12 hours ago 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Back to discussions
Expand all | Collapse all

QuikcConnect Onboard Wizard Error (403)

This thread has been viewed 4 times

  • 1.  QuikcConnect Onboard Wizard Error (403)

    Posted Apr 18, 2016 07:10 PM

    On some computers, I get this error:

    Capture.JPG

    And only interesting thing in quick1x.log is here:

     

    2016-04-18 10:29:49,969 [null] DEBUG Quick1X.QuickConnectDlg - Downloading device credentials from the Onboard server - http://XXX.YYY.NET/guest/mdps_qc_enroll.php
    2016-04-18 10:29:49,969 [null] DEBUG Quick1X.QuickConnectDlg - Onboard server Host Name XXX.YYY.NET
    2016-04-18 10:29:49,969 [null] DEBUG Quick1X.QuickConnectDlg - Onboard server URL Path /guest/mdps_qc_enroll.php
    2016-04-18 10:29:49,969 [null] DEBUG Quick1X.QuickConnectDlg - Detected Windows version - Windows 8.1
    2016-04-18 10:30:00,110 [null] ERROR Quick1X.QuickConnectDlg - Received error HTTP Status code - 403
    2016-04-18 10:30:00,110 [null] DEBUG Quick1X.Util - Running config task as logged in user



  • 2.  RE: QuikcConnect Onboard Wizard Error (403)

    EMPLOYEE
    Posted Apr 18, 2016 11:17 PM
    Does the user have administrative rights to that PC?


  • 3.  RE: QuikcConnect Onboard Wizard Error (403)

    Posted Apr 19, 2016 10:28 AM
    @cjoseph wrote:
    Does the user have administrative rights to that PC?

    We tried on both regular and local admin, and got the same results.



  • 4.  RE: QuikcConnect Onboard Wizard Error (403)

    EMPLOYEE
    Posted Apr 19, 2016 03:13 AM

    I would check the Application Log, which is under the Guest/Onboard part of ClearPass, down to the bottom under the section Support -> Application Log:

    2016-04-19 09_09_43-Application Log.png

    In many cases the Application Log will show you what is happening and why requests are failing.

     

    Also check that there is no proxy of firewall in between that may require specific authentication. A 403 error code means that something is actively denying the request from your client to ClearPass. I would start to see if ClearPass Onboard is that something, by checking the Application Log.

     

    Herman