Unable to ping/telnet/access gui of access point accross WAN
After several weeks of testing I have recently installed a Cisco Aironet 350 wireless access point and network at one of our sites. The network is working fine however I cannot connect to the access point remotely across the WAN. I cannot access the web interface of it or ping, tracert or telnet to it.
If you are on site this is possible but accessing it from across the WAN it is not working.
The access point is connected to a Cisco 2950 switch into interface fastethernet0/2 which is configured to 100MB full duplex
When tracing to the access point, the trace goes across the WAN to the
site however it gets no further than the router of that site.
Could anyone offer any advice as to how I can resolve this as I need to get onto the access point to be able to administer it. The other site is on a different subnet I am on 10.1 subnet with mask 255.255.0.0 and the access point is on 10.5 subnet with same mask.
Re: Unable to ping/telnet/access gui of access point accross WAN
Make sure that you have not applied any access-list(ACL) or any other similar filters in the gateway router Acess Contol Lists filter network traffic by controlling whether routed packets are forwarded or blocked at the router interface. Your router examines each packet to determine whether to forward or drop the packet, based on the criteria you specified within the ACL. ACL criteria can be the source address of the traffic, the destination address of the traffic, or the upper-layer protocol.
Check if you have any acesslist to deny the 10.1 subnet. If so, by permitting thsi subnet in the AXL, you will be able to ping, browse or telnet to the access point. See this document for more information:
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...