What would cause a Cisco WAP to be perfectly functional besides the fact that you can't ping it, and from the con line can't ping anything outside it?
2007-12-19 04:37:19 · 4 answers · asked by Hitmytotem 2 in Computers & Internet ➔ Computer Networking
The WAPs all go through 2950/3550s... look on the switch for an ping deny statement? What would it look like?
2007-12-19 05:11:56 · update #1
Have you altered the configuration since this problem occurred? I know my WAPs sometimes, due to power outages, stall and I simply recycle the power on them and they come back up.
2007-12-19 04:48:49 · answer #1 · answered by Slick 5 · 0⤊ 0⤋
You can set the Cisco WAP to not acknowledge ping requests, just like you can with any computer on the net. This helps to make that access point stealth to the outside world, preventing a lot of DOS attacks or hacks.
"can't ping anything outside it" is another matter. It may be a setting in the router that won't forward ping requests.
Try looking at the packets going/coming from the WAP and see what's being sent or blocked.
2007-12-19 04:51:41 · answer #2 · answered by snorkelface1 3 · 0⤊ 0⤋
What VLAN is the management of the WAP in? Where is this VLAN routed? Try sourcing your ping from the default gateway (either SVI or Router interface) to the WAP - if it replies to that, then source it from another network. If it does NOT respond to that second ping, then you have a routing issue - the two VLAN's are not routing between one another. If you cannot ping it from the gateway on its management network, then you have a Layer 2 issue ... check VLAN setting, subnet mask, default GW, etc.
2007-12-20 11:15:47 · answer #3 · answered by Anonymous · 0⤊ 0⤋
It could be a default setting. Cisco has an a deny statement at the end of all routers. So you might have to tell to allow pinging from inside, like turning on the ability to use ICMP
2007-12-19 05:08:29 · answer #4 · answered by datalj12 3 · 0⤊ 0⤋