Wireless Connection is there, but not working?

Discussion in 'Hardware' started by katie_21_, Sep 22, 2006.

  1. katie_21_

    katie_21_ Private E-2

    I'm hoping someone might be able to give me some ideas as to how to fix a wireless network problem. :)

    I have a wirless network setup in my house with 3 computers. The router is a D-Link AirPlus XTreme G and the network cards are D-Link DWL-G520's. Recently I reformatted one of the computers (previously running WinME) and put XP on it. There is nothing but the OS on this computer now. I installed the D-link driver, entered the WEP Key, and it says that there is a connection. BUT I can't connect to the internet. I get a "Cannot find server or DNS Error" in explorer. Also it can send packets, but not recieve them?

    Any suggestions would be greatly appreciated!
     
  2. erikske

    erikske Sergeant

    Open a command prompt, type ipconfig /all and post the output here.
     
  3. katie_21_

    katie_21_ Private E-2

    From which computer? The one that isn't working? :)
    I'll do both, just incase.. haha

    Computer w/ Router:

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : KITCHEN
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Eth
    ernet NIC
    Physical Address. . . . . . . . . : 00-40-F4-66-56-E7
    Dhcp Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IP Address. . . . . . . . . . . . : 192.168.0.101
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.0.1
    DHCP Server . . . . . . . . . . . : 192.168.0.1
    DNS Servers . . . . . . . . . . . : 192.168.0.1
    Lease Obtained. . . . . . . . . . : Saturday, September 23, 2006 9:24:18
    AM
    Lease Expires . . . . . . . . . . : Saturday, September 30, 2006 9:24:18
    AM

    Computer that isn't connecting properly:

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Kate
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Wireless Network Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : D-Link AirPlus DWL-G520 Wireless PCI
    Adapter(rev.B)
    Physical Address. . . . . . . . . : 00-0F-3D-AE-32-52
    Dhcp Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.0.102
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.0.1
    DNS Servers . . . . . . . . . . . : 192.168.0.1

    Thanks again for any help! :)
     
  4. rosewoodtech

    rosewoodtech Private E-2

    double check you wep key
    i would bet their is some thing wrong with the key, try and disable it on the router and see if the computer can access the internet

    ping 127.0.0.1 if good
    ping 192.168.0.102 (or ip assigned to computer) if good
    ping 102.168.0.1 (router) if good
    tracert www.microsoft.com (ip addresses may not show) if it finds routes
    you should be fine
     
  5. erikske

    erikske Sergeant

    That always works, you don't even need a network card. 127.0.0.1 is a loop back address.

    I noticed the PC that is not connecting has DHCP and autoconfiguration disabled. You should enable these.
    Go to control panel, click Network and internet connections, click Network connections, right click on your network connection and select properties. verify everything in the list is checked. If not, check all unchecked items. Now select the last entry, the Internet Protocol. Click the properties button. In the window that appears make sure 'Obtain an IP address automatically' and 'Obtain DNS server address automatically' are checked. (screenshot). Click OK. Click OK in the properties window too and close all remaining windows.
    Open a command prompt and execute the following commands
    Code:
    ipconfig /renew
    ipconfig /flushdns
    (If any errors occur, post them)
    Try again.
     
  6. rosewoodtech

    rosewoodtech Private E-2

     
  7. katie_21_

    katie_21_ Private E-2

    Ok, Here's what I got after I "Obtain IP address automatically" and "Obtain DNS address automatically":

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : KATE
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Wireless Network Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : D-Link AirPlus DWL-G520 Wireless PCI
    Adapter(rev.B)
    Physical Address. . . . . . . . . : 00-0F-3D-AE-32-52
    Dhcp Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Autoconfiguration IP Address. . . : 169.254.27.135
    Subnet Mask . . . . . . . . . . . : 255.255

    When I ping 127.0.0.1:

    Pinging 127.0.0.1 with 32 bytes of data:

    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

    Ping statistics for 127.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

    But when I ping the router:


    Pinging 192.168.0.1 with 32 bytes of data:

    Destination host unreachable.
    Destination host unreachable.
    Destination host unreachable.
    Destination host unreachable.

    Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


    The WEP is fine... I've checked and re-checked it. Plus there is another computer (PC3) which has a network card and is connected just fine using this key..

    Thanks again for your help! :)
     
  8. rosewoodtech

    rosewoodtech Private E-2

    ip stack is working. however if you notice the ip address 169.x.x.x this is the default when the computer does not pull an ip from a dhcp server (your router)
    if you can detect the signal but not connect to it it is a problem with the wep key.

    are you letting the d-link software control the wireless card or windows?
    i would double check the wep key you are using .. make sure you typed it in right
     
  9. erikske

    erikske Sergeant

    You're right, forgot about that.
    Have you installed the latest XP service pack? If not, check this URL http://support.microsoft.com/?kbid=313896
     
  10. katie_21_

    katie_21_ Private E-2

    I can't install the latest XP Service pack because I can't connect to the internet from that computer :)

    And I'm using Windows to control the wireless key... I have tried entering it a million times! The same key works for the other computers....
     
  11. rosewoodtech

    rosewoodtech Private E-2

    heres the issue with allowing windows to control the wireless. the wep key requirments they use are different from what d-link uses. windows requires a key to be 5 or 13 characters long. dlink and linksys will allow it to be any length. if some of your computers are using the dlink software to control the network cards they can be any length. however windows would let you know that the key is the wrong length and require you to change it.

    disable wep on the router and this computer, if the connection works come up with a new wep key and put it on all the computers. a phone number is a good key and easy to remember.
     
  12. erikske

    erikske Sergeant

    Download the SP2 standalone installer (272MB) to your working PC, copy it to the other one using a Cd or so and run.

    Are you sure? This would mean the key is not conform with the WEP specification. I'm not saying you are wrong (i don't trust windows either), but the way a WEP key works doesn't allow it to be any length. If you can specify a key of any length, this usually means it will be padded to the correct length. If D-Link uses another method to do this than windows, rosewoodtech has found the problem. If D-Link ships a tool with the network card, you should use it instead of the windows one.
     
  13. rosewoodtech

    rosewoodtech Private E-2

    with the d-link and linksys they request a key phrase and then parse it to the proper key. in windows you have to type the key
     
  14. katie_21_

    katie_21_ Private E-2

    After all that... It was the key!
    Boy do I feel like an idiot... haha

    Thanks again for your help. :eek:
     
  15. Alex Moon

    Alex Moon Private E-2

    I am a newcomer to the forums myself, but I can see
    right away that we are dealing with some heavy-duty
    geeks here. I appreciate from afar the doggedness of
    you guys hanging on to help out and find success.
    Much grass!
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds