Issue Problem: WARNING: "Failed to associate with XX:XX:XX:XX:XX (ESSID:????)

Discussion in 'Xiaopan Support' started by Neshone, 26 Mar 2013.

  1. Neshone

    Neshone Member

    Joined:
    26 Mar 2013
    Messages:
    5
    Likes Received:
    0
    Hello guys , please help me :(

    I have this problem: WARNING: Failed to associate with XX:XX:XX:XX:XX (ESSID:????)

    I using this wireless card: TL-WN7200ND
    http://www.tp-link.com.au/products/details/?categoryid=&model=TL-WN7200ND#down

    On some networks it works perfectly, and on others it won't start at all.

    The signal strength of the network is about : -55

    i run xiaopan 0451 with VWvare at Windows7
    --- Double Post Merged, 27 Mar 2013 ---
    Now i know what is my problem. WPS is locked. Is there a way to use Reaver 1.4 ?
    --- Double Post Merged, 27 Mar 2013 ---
    [​IMG]
     
  2. Pascal

    Pascal Wifi Sniffer
    Staff Member Moderator VIP

    Joined:
    6 Jun 2012
    Messages:
    211
    Likes Received:
    89
    Try with reaver 1.3 ;)

    For :

    Code:
    Select All
    cd /tmp/ wget https://reaver-wps.googlecode.com/files/reaver-1.3.tar.gz tar -xf reaver-1.3.tar.gz cd reaver-1.3/src/ cd src/ ./configure make make install

    ;)
     
  3. Neshone

    Neshone Member

    Joined:
    26 Mar 2013
    Messages:
    5
    Likes Received:
    0
    Tnx Pascal. I now will try ;)
     
  4. ImJoJo

    ImJoJo The One & Only
    VIP

    Joined:
    25 Jun 2012
    Messages:
    257
    Likes Received:
    121
    There is a way to unlock WPS...but make note of the following: All AP's around you will go back in default mode..(it can be good in a way) The tool is called mdk3..read this https://xiaopan.co/forums/posts/7837/
     
  5. Mr. Penguin

    Mr. Penguin Administrator
    Staff Member VIP Admin

    Joined:
    18 May 2012
    Messages:
    3,093
    Likes Received:
    1,262
    Is this working in 0.4.5.1? because on the onboot.lst its not quite right.
     
  6. ImJoJo

    ImJoJo The One & Only
    VIP

    Joined:
    25 Jun 2012
    Messages:
    257
    Likes Received:
    121
    you mean mdk3?
     
  7. Mr. Penguin

    Mr. Penguin Administrator
    Staff Member VIP Admin

    Joined:
    18 May 2012
    Messages:
    3,093
    Likes Received:
    1,262
  8. ImJoJo

    ImJoJo The One & Only
    VIP

    Joined:
    25 Jun 2012
    Messages:
    257
    Likes Received:
    121
    Gosh! How did I miss that :facepalm:
     
  9. Roham Soroush

    Roham Soroush Active Member

    Joined:
    23 Nov 2013
    Messages:
    4
    Likes Received:
    1
    reaver -i mon0 -b XX:XX:XX:XX:XX:XX -vv

    [!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: XXXXX-XXXX)
    [!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: XXXXX-XXXX)
    [!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: XXXXX-XXXX)
    [!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: XXXXX-XXXX)
    [!] WARNING: Failed to associate with XX:XX:XX:XX:XX:XX (ESSID: XXXXX-XXXX)


    "Not able to associate"

    For this, you can try associating yourself. So launch reaver with the -A option and do the following command:
    aireplay-ng -1 0 -b [target bssid] -h [your mac] [monitor interface]

    If the progress is really slow, you might want to look up the mac address of the target and see if you should use a delay for the attempts.
     

Share This Page

Loading...