The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Wireless AP self-destructed while away...
meatflower
Registered User regular
Registered User regular
I left for a trip two days before New Years, when I came back yesterday both the Mac laptop and my Eee were not online. Been running the Airlink101 AP431w for over a year now, never had a problem. Now, both machines cannot acquire an address through DHCP. After some time the Eee will assume a 169.254.x.x address, which I've read is from the range XP assigns when it gets no DHCP response.
I've restored factory defaults, reloaded the latest firmware (only available as well). It's definitely the AP itself, as these are two completely different machines that were both connected to it before I left and both were not working when I returned. In addition, they're both able to join and get addresses from my neighbors unsecured wireless router.
There's no option anywhere on the AP's admin page for turning on/off DHCP, the only reference being if the AP itself should find its address that way or be static. After extensive Google'ing I was able to Telnet into the AP and run some commands that initially told me the DHCP server was off. It was definitely operational before, I find it hard to believe somebody else Telnet'd into the damned thing and deactivated. I tried to simply turn it back on but it has no idea what range to assign addresses from...wants a WINS server, and a bunch of other stuff that's just a little over my head. Doesn't seem right that I should have to manually assign all this info when it did it automatically before.
I've tried just setting up the computers with static IP's and while they do gain connectivity to the AP (I can access the admin page from them), they can't ping the main router and hence have no internet access.
Kind of at my wits end here, should I just buy a new access point?
I've restored factory defaults, reloaded the latest firmware (only available as well). It's definitely the AP itself, as these are two completely different machines that were both connected to it before I left and both were not working when I returned. In addition, they're both able to join and get addresses from my neighbors unsecured wireless router.
There's no option anywhere on the AP's admin page for turning on/off DHCP, the only reference being if the AP itself should find its address that way or be static. After extensive Google'ing I was able to Telnet into the AP and run some commands that initially told me the DHCP server was off. It was definitely operational before, I find it hard to believe somebody else Telnet'd into the damned thing and deactivated. I tried to simply turn it back on but it has no idea what range to assign addresses from...wants a WINS server, and a bunch of other stuff that's just a little over my head. Doesn't seem right that I should have to manually assign all this info when it did it automatically before.
I've tried just setting up the computers with static IP's and while they do gain connectivity to the AP (I can access the admin page from them), they can't ping the main router and hence have no internet access.
Kind of at my wits end here, should I just buy a new access point?
meatflower on
0
Posts
I ask because DHCP would be off if it were an AP passing DHCP requests back to your main router.
It should default to DHCP On.
Can trade TF2 items or whatever else you're interested in. PM me.
The AP is connected to a 4-port switch, which is then connected to the router, through a Homeplug device (ethernet over power). It's rather convoluted, I guess I need to get into the web admin page for the switch but it might just be a passive device.
e: And just to clarify, I have the Mac now hooked up to the switch via ethernet and it's online so the switch seems to be good.
e2: I can also get to the admin page of the AP from my main computer which doesn't even go through the switch, but is hooked up directly to the router. This seems to suggest that the AP should be able to get DHCP assignments from it.
I Telnet'd into the AP again and ping'd the router, and it worked. Why won't it pass the DHCP requests? :x
I guess it really is dead...
Any reason you're using EoP? Would it be impractical to move or run cabling?
And yeah, those are exactly the reasons I'm using EoP. Actually have three of them in total, and they've always been great, totally transparent.
I'm moving out in two days and I'm the only one who was really using it anyway (that other laptop is pretty much a desktop machine now so the wired connection is fine), not even gonna replace it.
So uh...solved?
Thanks everyone, I appreciate the help.