locked
Received Crypto-Binding TLV is invalid RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Please I am in desperate help, I can't figure out why I can't authenticate to windows 2008 radius server.  Could you help me figure it out why/what cause the error: Received Crypto-Binding TLV is invalid.  I could authenticate with windows 2000 AIS without a problem.   Thanks you for your help

    Network Policy Server denied access to a user.

    Contact the Network Policy Server administrator for more information.

    User:
        Security ID:            ***\***
        Account Name:            ***\***
        Account Domain:            ***
        Fully Qualified Account Name:    *****

    Client Machine:
        Security ID:            NULL SID Submit
        Account Name:            -
        Fully Qualified Account Name:    -
        OS-Version:            -
        Called Station Identifier:        0017.0fd8.8b40
        Calling Station Identifier:       (edit out)

    NAS:
        NAS IPv4 Address:        x.x.x.x (edited out)
        NAS IPv6 Address:        -
        NAS Identifier:            swap1
        NAS Port-Type:            Wireless - IEEE 802.11
        NAS Port:            308

    RADIUS Client:
        Client Friendly Name:        swap1
        Client IP Address:            x.x.x.x

    Authentication Details:
        Proxy Policy Name:        Use Windows authentication for all users
        Network Policy Name:        Production Wireless Users
        Authentication Provider:        Windows
        Authentication Server:        editout.com
        Authentication Type:        PEAP
        EAP Type:            -
        Account Session Identifier:        -
        Reason Code:            301
        Reason:                Received Crypto-Binding TLV is invalid. 
    Wednesday, November 12, 2008 11:21 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    hi let me know the operating system of your NAP client, and it setting..
    regards
    Brijesh Shukla
    Friday, November 21, 2008 3:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am getting the same thing....
    What was the outcome and resolution??
    Monday, October 12, 2009 4:24 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    This appears to be a problem with Broadcom based WLAN controllers, and possibly Cisco one also. If you enable Windows to be the Wireless controller everything will work.  
    Friday, August 13, 2010 5:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just to validate, Disabling the Dell Wireless Manager on our Dell Wireless 1390 WLAN cards and enabling the Windows Zero Config service fixed the issue for us. 

    I also had to go into the properties of the Adapter > Wireless Networks > Properties of the desired network > Authentication  and change it from SmartCard to PEAP in our case. 

    Thanks craymond

    Friday, March 30, 2012 12:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This could be because of old cipher suites supported by supplicant . You can try enabling MD5 or other old cipher suites through registries.
    Thursday, October 10, 2013 9:51 PM