Results 1 to 7 of 7

Thread: Connection Failed: Could not contact wireless access point

  1. #1
    Just burned his ISO
    Join Date
    May 2011
    Posts
    2

    Default Connection Failed: Could not contact wireless access point

    So i have tried everything. I'm relatively new to Linux. I have used Ubuntu 10.04 a while ago. But have been on a windows box for some time and forgot a lot about it. This time, i have Backtrack 5 installed on a laptop with intel PRO/Wireless 3945 [golan]. So here is my problem. I am able to See networks in wicd client, and also when i run airodump-ng. Airmon-ng shows my wlan0 interface, and i can crack wep just fine. But when i try and connect to a cracked network, or even my own, it tells me can not obtain IP address. So i changed to static and input the information known for my network. Assigned an IP within the scope, and then it tells me that "connection Failed: Could not contact the wireless access point" I've checked with /var/logs/wicd/wicd.logs and its returning that Connection failed: Failed to ping the access point. exiting connection thread, sending connection attempt result association_failed. I am at a stand still. I dont know waht else to do. Can someone help? thanks in advance for all who post positive replies.

  2. #2
    Just burned his ISO
    Join Date
    Feb 2012
    Posts
    7

    Default Re: Connection Failed: Could not contact wireless access point

    I am having the same issue on my Vostro 1510 laptop. I wasn't able to get it to do anything at all with wicd 1.7. I saw some articles about the same issue that suggested I downgrade to 1.6.2.2. I did that and was able to get further than I had before. But then it started telling me it couldn't get an IP. If I put in a static IP it tells me it can't connect to the access point.

    Here's what the logs are showing me:

    2012/02/04 23:09:27 :: Attempting to authenticate...
    2012/02/04 23:09:27 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c',
    '/var/lib/wicd/configurations/14d64d2f5e08', '-D', 'wext']
    2012/02/04 23:09:27 :: ['iwconfig', 'wlan0', 'essid', 'WOPR']
    2012/02/04 23:09:27 :: iwconfig wlan0 channel 8
    2012/02/04 23:09:27 :: iwconfig wlan0 ap 146:4D:2F:5E:08
    2012/02/04 23:09:27 :: WPA_CLI RESULT IS DISCONNECTED
    2012/02/04 23:09:28 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:29 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:30 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:31 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:32 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:33 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:34 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:35 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:36 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:37 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:38 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:39 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:40 :: WPA_CLI RESULT IS SCANNING
    2012/02/04 23:09:41 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:42 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:43 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:44 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:45 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:46 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:47 :: WPA_CLI RESULT IS DISCONNECTED
    2012/02/04 23:09:48 :: WPA_CLI RESULT IS SCANNING
    2012/02/04 23:09:49 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:50 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:51 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:52 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:53 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:54 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:55 :: WPA_CLI RESULT IS SCANNING
    2012/02/04 23:09:56 :: WPA_CLI RESULT IS SCANNING
    2012/02/04 23:09:57 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:58 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:09:59 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:10:00 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:10:01 :: WPA_CLI RESULT IS ASSOCIATED
    2012/02/04 23:10:02 :: wpa_supplicant authentication may have failed.
    2012/02/04 23:10:02 :: Running DHCP
    2012/02/04 23:10:02 :: /sbin/dhcpcd wlan0
    2012/02/04 23:10:22 :: err, wlan0: timed out
    2012/02/04 23:10:22 ::
    2012/02/04 23:10:22 :: DHCP connection failed
    2012/02/04 23:10:22 :: exiting connection thread
    2012/02/04 23:10:23 :: Sending connection attempt result dhcp_failed

    It's saying DHCP failed. I'm getting it no problem when booted into windows 7. I've reset everything on my wireless router and tried multiple fixes from around the web. Has anyone else run into this? I'm kind of at a loss...

  3. #3
    Just burned his ISO
    Join Date
    Feb 2010
    Posts
    19

    Default AW: Connection Failed: Could not contact wireless access point

    Seems like backtrack 5.1 has multiple issues with WLAN configuration.

    installing network-manager instead of WICD normally fixes this.
    The problem with the kernel flag that disallows iwtools and so on remains. I dunno exactly how to fix this, but I think reinstalling the kernel without that flag should do the job. Though I dont know exactly how to do this.

    Maybe someone has advices here?

  4. #4
    Just burned his ISO
    Join Date
    Feb 2012
    Posts
    7

    Default Re: AW: Connection Failed: Could not contact wireless access point

    It seems like it's just broadcom issues. I plugged in the Alfa card that just arrived and no issues at all. Works like a charm. Going to disable the broadcom in Bios and forget it's even there.

  5. #5
    Just burned his ISO Rasta420's Avatar
    Join Date
    Feb 2012
    Location
    I'm on a boat somewhere off the Spanish coast.
    Posts
    8

    Default Re: AW: Connection Failed: Could not contact wireless access point

    Quote Originally Posted by almightyzappa View Post
    It seems like it's just broadcom issues. I plugged in the Alfa card that just arrived and no issues at all. Works like a charm. Going to disable the broadcom in Bios and forget it's even there.
    almightyzappa,

    what alfa card did you go with? I assume it's a pci based card...

  6. #6
    Just burned his ISO
    Join Date
    Feb 2012
    Posts
    7

    Default Re: AW: Connection Failed: Could not contact wireless access point

    It's one of the USB ones recommended on the forums here and there. It's the ALFA AWUS036NH. Got it on amazon for 32 and change. Works like a charm.

  7. #7
    Just burned his ISO Rasta420's Avatar
    Join Date
    Feb 2012
    Location
    I'm on a boat somewhere off the Spanish coast.
    Posts
    8

    Default Re: Connection Failed: Could not contact wireless access point

    cool, thanks for the info, i think i am currently using an old belkin f5d7000 v8 with the ath5k driver, and the alfa 5dbi 10' antenna extender in my tower but it doesn't support packet injection (as far as I can find) so trying to find a new one that works good with BT5 x64

    Rasta420

Similar Threads

  1. Replies: 5
    Last Post: 12-11-2010, 04:32 PM
  2. Backtrack 4 R1 won't connect to my wireless access point
    By Mike1990 in forum Beginners Forum
    Replies: 1
    Last Post: 10-27-2010, 02:34 AM
  3. Using Backtrack as Wireless Access Point
    By quick in forum Beginners Forum
    Replies: 2
    Last Post: 02-04-2010, 11:19 AM
  4. Having problems with my Wireless USB connecting my Access Point
    By Johndoe1893 in forum OLD Newbie Area
    Replies: 6
    Last Post: 02-27-2009, 09:35 PM
  5. Wireless Connection Failed with BT3-USB
    By lolopopo in forum OLD Newbie Area
    Replies: 0
    Last Post: 02-12-2008, 06:51 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •