WAP behind ethernet not working

papasmurf

Distinguished
Apr 14, 2002
2,280
0
19,780
I have a wireless access point behind an ethernet router. the eth router has dhcp disabled and is a dlink dl604 the wap is a linksys wap11 v2.6

the eth router is plugged into the modem, the wap is plugged into one of the eth routers ports via a patch cable.

the link light is steady on the wap but no act light appears when it's plugged into the eth router. when the wap is plugged directly into the modem it works fine. I don't understand why.

any ideas guys?

Join the TomsHardware IRC channel <A HREF="http://chat.oddnet.net/tom/" target="_new">http://chat.oddnet.net/tom/</A><P ID="edit"><FONT SIZE=-1><EM>Edited by PapaSmurf on 11/03/04 02:30 AM.</EM></FONT></P>
 

kwebb

Distinguished
Oct 6, 2001
456
0
18,780
Tried another port on your router's switch? Do you still have connectivity to the AP from a wireless client? Meaning, can you ping the AP? You can try defaulting the AP as well. I would probably do that first even though it might be overkill. Only takes a few minutes to reconfigure and you can eliminate one of the biggies as a factor. Flashing the firmware as well. Make sure that is up to date. What do the AP logs say?
 

papasmurf

Distinguished
Apr 14, 2002
2,280
0
19,780
can't log into the ap. I'm using an ipaq and a pcmcia network card with it. the thing is it can not connect to it unless it's plugged in directly to the modem. can't connect at all. strangest thing. I've tried different ports on the router


Join the TomsHardware IRC channel <A HREF="http://chat.oddnet.net/tom/" target="_new">http://chat.oddnet.net/tom/</A>
 

kwebb

Distinguished
Oct 6, 2001
456
0
18,780
Connect to what? The internet? That is a secondary problem if you can't associate to the AP. Don't know if a pocket PC has a command prompt but there's got to be a way to ping the AP. Do that and report back. Also, there is surely a utility that will tell you if your associated. Logon to the router's admin page with a wired PC. Look at the logs, default it if you like. Internet not working is just a symptom. Getting linked to the AP is the first priority. Define if your doing that or not. Then start pinging, of if there is a prompt run ipconfig /all at the prompt and report back what your IP is.
 

papasmurf

Distinguished
Apr 14, 2002
2,280
0
19,780
I meant that it cannot connect the the wap at all. no connectivity. for some reason it is not transmitting when it is behind the router. to connect to the wap via ethernet what would it's ip address be behind the router?

Join the TomsHardware IRC channel <A HREF="http://chat.oddnet.net/tom/" target="_new">http://chat.oddnet.net/tom/</A>
 

kwebb

Distinguished
Oct 6, 2001
456
0
18,780
Look at your DHCP log on your router. That is if it is setup as a dhcp client. It might actually be a DHCP server itself. What model AP do you have? If it is not picking up and IP from your router then it will be whatever default IP it has. Check your manual for that. I couldn't tell you what IP it has nor could anybody else unless they have that same model and it's setup like theirs. There are some common IP ranges for SOHO products. 192.168..0.1 or 1.1 Anyway, being behind a router will have nothing to do with AP to client asssociation. Perhaps you don't have IP connectivity but I doubt you lose your association to the AP just because you plug it into a switch port on your router.
 

papasmurf

Distinguished
Apr 14, 2002
2,280
0
19,780
the ap is a linksys wap11 2.6 the router is a dlink 604. for some strange reason last night the wap worked. I had connectivity. than today nothing. no change to the netork occurred during this time. I tried changing the ethernet cables and nothing... I don't understand it. the ipaq does not see the wap anymore. at all.

Join the TomsHardware IRC channel <A HREF="http://chat.oddnet.net/tom/" target="_new">http://chat.oddnet.net/tom/</A>