Results 1 to 8 of 8

Thread: Wireless network detected but will not connect

  1. #1

    Default Wireless network detected but will not connect

    Hi there!

    I have a D-link dir-635 firmware v. 2.30eu (latest) and a USB WLAN adapter D-link DWA-140 802.11n. The driver seems to be installed correctly since lsusb lists it correctly and all the wireless networks in the vicinity are detected including mine. When I try to connect however NetworkManager says it is activating but after awhile the windows with the newtork password appers. dmesg output:

    [ 5509.487262] wlan0: direct probe to AP 00:1c:f0:71:03:88 try 1
    [ 5509.684014] wlan0: direct probe to AP 00:1c:f0:71:03:88 try 2
    [ 5509.884020] wlan0: direct probe to AP 00:1c:f0:71:03:88 try 3
    [ 5510.084014] wlan0: direct probe to AP 00:1c:f0:71:03:88 timed out

    So it is able to determine the AP:s mac address but each time it times out.

    I have tried disabling the security on the router but no luck.

    Not sure what to try next. I have checked some of the tips supplied in these forums but none seem to handle the issue I am having.

    Any suggestions would be great.

  2. #2
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,381

    Default Re: Wireless network detected but will not connect

    On 02/16/2010 09:46 AM, scaryxited wrote:
    >
    > Hi there!
    >
    > I have a D-link dir-635 firmware v. 2.30eu (latest) and a USB WLAN
    > adapter D-link DWA-140 802.11n. The driver seems to be installed
    > correctly since lsusb lists it correctly and all the wireless networks
    > in the vicinity are detected including mine. When I try to connect
    > however NetworkManager says it is activating but after awhile the
    > windows with the newtork password appers. dmesg output:
    >
    > [ 5509.487262] wlan0: direct probe to AP 00:1c:f0:71:03:88 try 1
    > [ 5509.684014] wlan0: direct probe to AP 00:1c:f0:71:03:88 try 2
    > [ 5509.884020] wlan0: direct probe to AP 00:1c:f0:71:03:88 try 3
    > [ 5510.084014] wlan0: direct probe to AP 00:1c:f0:71:03:88 timed out
    >
    > So it is able to determine the AP:s mac address but each time it times
    > out.
    >
    > I have tried disabling the security on the router but no luck.
    >
    > Not sure what to try next. I have checked some of the tips supplied in
    > these forums but none seem to handle the issue I am having.
    >
    > Any suggestions would be great.


    Are you using KDE or Gnome? If KDE, click on the applet, choose "Manage
    Connections" and create a connection for your wireless. It is a design fault
    (bug?) in the current NM that security information entered into the pop-up does
    not get entered into the database.

    If you are using WEP, you must use the hexadecimal key. A passphrase is unlikely
    to work as there are two ways to convert a phrase to a key, and Linux uses a
    different one than Window$.

  3. #3

    Default Re: Wireless network detected but will not connect

    Hi thanks for the reply. I am using KDE. I have tried disabling wireless security on the router so the wireless network is unsecured then adding a connenction that dosn't use wireless security but it still will not connect. Perhaps the router dosn't work with linux?

  4. #4
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    14,084
    Blog Entries
    12

    Default Re: Wireless network detected but will not connect

    Quote Originally Posted by scaryxited View Post
    Perhaps the router dosn't work with linux?
    AFAIK most routers are small linux machines, that's not where the problem is.

    Open a terminal window and post output of:

    su -c ifconfig

    enter rootpassword when asked for.
    - Athlon X6 3.6 GHz, 16 GB DDR3, 64 GB SSD, 3 TB of disks, GT540, openSUSE Factory + KDE
    - ASUS A73SD, Intel + GT610M Optimus, 6 GB, 2 x 120 GB SSD, openSUSE Factory + KDE

    Anything that can go wrong.... will teach us

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  5. #5
    Join Date
    Jan 2010
    Location
    Redding, California, USA
    Posts
    26

    Default Re: Wireless network detected but will not connect

    I had a similar problem and a tcpdump showed the probes were sent with a source address of 0.0.0.0 causing my D-Link router to reject them as not from the correct network. I never addressed the problem as I connected using a static managed net from the router instead of trying to create a dynamic Ad-Hoc net.

    Sounds like either a configuration problem or a routing problem. You are going to have to post your router setup and what you've entered into NetworkManager. The output from ifstatus wlan0 would be helpful.

  6. #6

    Default Re: Wireless network detected but will not connect

    Ok. Now it won't even detect my wireless network. My windows laptop can detect 6 wireless networks in the vicinity including my own. My linux machine only detects 4 one of whitch my windows machine dosn't detect. I have tried connecting to another unsecured Zyxel router and it just times out there too.

    My router uses automatic channel scan, WPA2 personal with passphrase, auto channel with 20/40 Mhz, Mixed 802.11n and 802.11g mode. transmission rate is also automatic

    ifconfig output:
    wlan0 Link encap:Ethernet HWaddr 00:1B:11:C5:F5:39
    inet6 addr: fe80::21b:11ff:fec5:f539/64 Scope:Link
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:15 errors:0 dropped:0 overruns:0 frame:0
    TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1695 (1.6 Kb) TX bytes:2348 (2.2 Kb)

    ifstatus output:
    wlan0 name: 802.11 n WLAN
    DHCP4 client (dhcpcd) is running
    . . . but is still waiting for data
    wlan0 is up
    4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:1b:11:c5:f5:39 brd ff:ff:ff:ff:ff:ff
    wpa_state=SCANNING


    EDIT: My router is detected now. There was a setting in the router for WPA mode. The options were "WPA or WPA2", "WPA only" or "WPA2 Only" if I set it to WPA2 only Linux was able to detect it.
    Still times out though.
    Setting in NetworkManager or my connection is:
    Mode: INfrastructure
    BSSID: empty
    Restrict to interface: WLAN0
    MTU:Auto

    Wireless security: WPA/WPA2 Personal

    UNder IP address tab:
    Configure Auto DHCP
    DHCP Client ID: empty

  7. #7

    Default Re: Wireless network detected but will not connect

    EDIT2: tried using static ipaddresses but it didn't even try to connect.

  8. #8
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,381

    Default Re: Wireless network detected but will not connect

    On 02/26/2010 08:06 AM, scaryxited wrote:
    >
    > EDIT2: tried using static ipaddresses but it didn't even try to connect.


    I see no indication that you have authenticated or associated.

    Please return you AP to WPA or WPA2, get rid of static IP's, try to connect, and
    post the output of

    sudo /usr/sbin/iwconfig
    sudo /use/sbin/iwlist scan
    dmesg | tail -n 100
    sudo tail -n 100 /var/log/wpa_supplicant.log
    sudo tail -n 100 /var/log/NetwotkManager

Posting Permissions

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