cancel
Showing results for 
Search instead for 
Did you mean: 

Can't ping clients from LAN

Can't ping clients from LAN

bchambers1
New Contributor

I'm having all kinds of issues with connections from wireless clients to the LAN lately. The biggest thing that I have noticed is that I've lost the ability to ping to the clients from the LAN.

 

I can ping from the client to the LAN, but not the LAN to the client. There are no firewalls in the way, and it even occurs when they are on the same VLAN, but one is on LAN and the other on wireless on Aerohive. I can't find where this is being blocked from.

 

There are other things, mainly group policy related, but I have a feeling that this is all related. I have a feeling that once I have the ping issue resolved, the rest will fall into place.

3 REPLIES 3

bchambers1
New Contributor

Ok. I was able to finally track it down using our RMM tool. Looks like the one computer that was allowing me to ping it, the antivirus was crashing on the system. I looked at the policies in the antivirus, and it was set to treat wireless networks like Public networks by default. I set it to let Windows decide if it was public or not, and that solved the issue. All the devices are pinging on the wireless now. I also suspect this will fix the rest of the problems that I was having with wireless laptops and domain trust issues.

 

Thank you very much.

bchambers1
New Contributor

Sam,

 

I put my computer in the same VLAN in order to eliminate any routing hops in the network. It's simply layer 2 connection now. That said, I was able to do some troubleshooting. I have found one windows client on one AP that is pinging.

 

Pinging [10.9.0.57] with 32 bytes of data:

Reply from 10.9.0.57: bytes=32 time=4ms TTL=128

Reply from 10.9.0.57: bytes=32 time=2ms TTL=128

Reply from 10.9.0.57: bytes=32 time=2ms TTL=128

Reply from 10.9.0.57: bytes=32 time=2ms TTL=128

 

a different windows client with the same settings, GPOs, domain, etc. on the same exact AP:

Pinging [10.9.0.218] with 32 bytes of data:

Reply from 10.9.1.100: Destination host unreachable.

Reply from 10.9.1.100: Destination host unreachable.

Reply from 10.9.1.100: Destination host unreachable.

Reply from 10.9.1.100: Destination host unreachable.

 

In the arp table on my computer:

10.9.0.57       e4-70-b8-dd-b6-8e   dynamic

10.9.0.218      d0-ab-d5-e5-11-a9   dynamic

 

On the port on my switch where they both are:

 show mac address-table int gi2/0/25

Aging time is 300 sec

 

 Vlan    Mac Address     Port    Type

-------- --------------------- ---------- ----------

  59   08??44:77:39:80  gi2/0/25  dynamic

  60   04:d3:b0:27:c3:3d  gi2/0/25  dynamic

  60   34:08:bc:37:e5:ee  gi2/0/25  dynamic

  60   d0?d5:e5:11:a9  gi2/0/25  dynamic

  60   e4:70:b8:dd:b6:8e  gi2/0/25  dynamic

 

So, same VLAN, same switchport, both windows clients, both on the same corporate domain with all the same applications, settings, GPOs (they're literally in the same department in a clinic). One pings the other doesn't.

 

I rebooted every AP in our ExtremeCloud last night and also enabled inter-station traffic and pushed the configs earlier in the day. Not sure what is going on here.

samantha_lynn
Esteemed Contributor III

Can you confirm that ICMP traffic is allowed on your network? If it is, could you try running a trace route so we can see where the traffic gets dropped? To run a trace route, the command is: tracert <address>

GTM-P2G8KFN