Reaver 1.4 - Failed to Associate ISSUE...

[GoogleCodeExporter]

I am having a problem of the following nature;

I posses the actual WPS PIN of a AP and i'm trying to retrieve it's WPA2 PSK 
via Reaver 1.4
(Live USB BT 5R3, Wireless Adapter Intel(R) WiFi Link 5300 AGN - performs well)
Signal strength is not the greatest, but is constant and it didn't evanescent, 
not for one moment
After airmon-ng start wlan0 i've tried: wash -i mon0 to confirm that APs WPS is 
NOT locked
Next input is: reaver -i mon0 -b A0:B1:C2:D3:E4:F5 -p 98529742 -vv
and it keeps going:

[+] Waiting for beacon from A0:B1:C2:D3:E4:F5
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[!] WARNING: Failed to associate with A0:B1:C2:D3:E4:F5 (ESSID: alooo)
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 1
[!] WARNING: Failed to associate with A0:B1:C2:D3:E4:F5 (ESSID: alooo)
[!] WARNING: Failed to associate with A0:B1:C2:D3:E4:F5 (ESSID: alooo)

No error messages, just keeps repeating from the above mentioned for quite long
than halts at some point, i repeat the procedure several times...
Tried adding different arguments: -T 2:00, -N, -c 1....with no avail

I did read various posts on folks having the "Failed to associate"
in which i didn't find the solution. 

Anyone got any suggestion/ideas what am i missing here
Any help very appreciated/thanks in advance.

Original issue reported on code.google.com by jeronom...@gmail.com on 15 Dec 2013 at 3:16

[GoogleCodeExporter]

what happens if you try: 
reaver -i mon0 -b A0:B1:C2:D3:E4:F5 -a -S -N -c X -vv

where "-c X" change X for channel correct show in wash.

Original comment by deltomaf...@gmail.com on 18 Dec 2013 at 11:57

[GoogleCodeExporter]

i did exactly as you suggested,

here, after wash, shows taht is still on channel 1, than i ran:
reaver -i mon0 -b A0:B1:C2:D3:E4:F5 -a -S -N -c 1 -vv

[+] Waiting for beacon from A0:B1:C2:D3:E4:F5
[+] Switching mon0 to channel 1
[!] WARNING: Failed to associate with A0:B1:C2:D3:E4:F5 (ESSID: alooo)

...and it just sits there, doing noting!?!?

Original comment by jeronom...@gmail.com on 20 Dec 2013 at 9:13

[GoogleCodeExporter]

open another terminal and leave running:
airodump mon0 -d A0:B1:C2:D3:E4:F5 -c 1 --ignore-negative-one

see if something changes

Original comment by deltomaf...@gmail.com on 21 Dec 2013 at 7:44

[GoogleCodeExporter]

Nope, no changes...except that when i ran the command you suggested, beacons 
and frames are constantly changing (growing) numbers.

!?!?!?

I really don't see why is this happening...
Obviously, i don't have enough knowledge to mess with this type of thing..
Will try on another known/friendly router, just to see can reaver perform well.

Original comment by jeronom...@gmail.com on 29 Dec 2013 at 3:59