Access Points

Reply
New Contributor
Posts: 1
Registered: ‎10-13-2011

IAP-105 Not Responding to Pings Sometimes

We are having an issue where client machines occasionally lose connectivity to a device on the same subnet when on the wireless. When it happens, the laptops can't ping a single device (or access any ports on it), but if they move over to an ethernet connection, their pings to the device work. When they are on the wireless, they can ping other devices, just not a single IP (one of the servers). We have noticed the issue at two different offices who both have IAP-105 APs and it's happened a total of 3 times. The IP they are trying to communicate with at the time happens to be a Windows 2003 or 2008 server depending on the location. When the issue is occurring, the Windows server can't ping the IP of the IAP-105 the users are associated with, or the client workstations behind it, but the AP is pingable from the gateway router or any other device hard wired to the network. The SSID they are connected to are configured with unrestricted access. The arp table on the windows server had the mac address of the AP having the issues listed, but when running the ping to the AP, no replies would happen. As soon as the IAP-105 that was having the issues was rebooted, it all began working, the server could ping the AP, and the clients could ping the server again.

Version: 5.0.3.0-1.1.0.1_29974

Mac and IP address of Windows server: 00:1C:C4:C2:76:04 10.1.71.26
Mac and IP address of IAP 105: 00:0b:86:cf:85:ab 10.1.71.22

I captured a Tech-dump, and I'm pretty sure it was before we rebooted the AP having the issue.
Guru Elite
Posts: 21,279
Registered: ‎03-29-2007

Re: IAP-105 Not Responding to Pings Sometimes


We are having an issue where client machines occasionally lose connectivity to a device on the same subnet when on the wireless. When it happens, the laptops can't ping a single device (or access any ports on it), but if they move over to an ethernet connection, their pings to the device work. When they are on the wireless, they can ping other devices, just not a single IP (one of the servers). We have noticed the issue at two different offices who both have IAP-105 APs and it's happened a total of 3 times. The IP they are trying to communicate with at the time happens to be a Windows 2003 or 2008 server depending on the location. When the issue is occurring, the Windows server can't ping the IP of the IAP-105 the users are associated with, or the client workstations behind it, but the AP is pingable from the gateway router or any other device hard wired to the network. The SSID they are connected to are configured with unrestricted access. The arp table on the windows server had the mac address of the AP having the issues listed, but when running the ping to the AP, no replies would happen. As soon as the IAP-105 that was having the issues was rebooted, it all began working, the server could ping the AP, and the clients could ping the server again.



Version: 5.0.3.0-1.1.0.1_29974

Mac and IP address of Windows server: 00:1C:C4:C2:76:04 10.1.71.26
Mac and IP address of IAP 105: 00:0b:86:cf:85:ab 10.1.71.22

I captured a Tech-dump, and I'm pretty sure it was before we rebooted the AP having the issue.




Cody,

Please consider enabling "Drop Broadcasts and Multicast" on all Virtual APs. It could be broadcast traffic causing contention.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: