1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Connecting to wireless channel but cannot get IP

Discussion in 'Cisco/Linksys Wireless Routers' started by Billio, Sep 13, 2004.

  1. Billio

    Billio Guest

    I just bought a WRT54G to replace my D-Link 614+ to gain 802.11g capabilities.

    I've configured the WRT54G and it connects to my ISP and gets it's IP successfully. Any machines connected to it on the LAN, via wire, are also able to access the internet without any problems.

    None of my wireless equipment is working properly. I'm using open wep with 128 bit encryption. I get a successful wireless connection according to my 2 laptops running winxp, one pre-sp2 one @ sp2. I tried the default firmware and then upgraded to the latest firmware without success. I then upgraded to Sveasoft Satori-4.0 v2.07.1.7sv. Still no luck. I can even verify, through status wireless, that the WRT54G can see the connecting systems and shows good signal strength. I have loopback disabled.

    My default setup is to use one of my internal servers as my DHCP server. No ip address is acquired although the laptops connect to the WRT54G. I tried configuring a hard ip once again with no luck. I cannot ping the router or any machines on the lan. I then setup the WRT54G to provide DHCP, once again without any luck.

    Any thoughts? Should I return this unit and go back to D-Link?

  2. AbNormal

    AbNormal Network Guru Member

    First, try disabling WEP on both the router and your PC, to ensure the wireless link is not your problem.

    Second, have the router issue DHCP IP addresses, and disable or unplug the other DHCP server from your router.

    You want to start with a minimum system with as few variables as possible. As you begin to sort out where your problem is, then put back one more component at a time.

    At this point, there are just too many possibilities to deal with all at once.

  3. Guyfromhe

    Guyfromhe Network Guru Member

    also check for mac filtering, that can cause strange results if it's blocking your systerm.

Share This Page