871W wired devices cannot communicate/ping with wireless

Answered Question
May 28th, 2010

Hello,

I have an 871W that is giving me fits.  I have been troubleshooting this for a few days now and cannot figure out what I am doing wrong.  My wired clients cannot communicate with any wireless devices.  My wireless devices cannot communicate with each other.  However, my wireless devices CAN initiate a connection to a wired device!  I know this because I have a local webmail server on the wired side that can be reached wirelessly.  All devices, wired and wireless, are on VLAN 1, which happens to be the only vlan configured.

Attached is my configuration file, properly sanitized.

When I try to ping from a wired device to a wireless device, I get the following error:

~$ ping 172.27.44.27
PING 172.27.44.27 (172.27.44.27) 56(84) bytes of data.
From 172.27.44.3 icmp_seq=1 Destination Host Unreachable
From 172.27.44.3 icmp_seq=2 Destination Host Unreachable
From 172.27.44.3 icmp_seq=3 Destination Host Unreachable
From 172.27.44.3 icmp_seq=4 Destination Host Unreachable
From 172.27.44.3 icmp_seq=5 Destination Host Unreachable
From 172.27.44.3 icmp_seq=6 Destination Host Unreachable

--- 172.27.44.27 ping statistics ---
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7051ms
, pipe 3

~$

Wireless devices simply timeout when trying to ping each other.

Thank you for your help.

Chris

I have this problem too.
0 votes
Correct Answer by johnwcorl about 6 years 6 months ago

Are there any firewalls on the wireless hosts?

Have you wiresharked any traffic to see if it is hitting the dest host?

Quick look on config looks ok. Some extra ACLs that i didnt see used are in there.

Can both wired and wireless ping a public IP?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
johnwcorl Sat, 05/29/2010 - 17:45

Are there any firewalls on the wireless hosts?

Have you wiresharked any traffic to see if it is hitting the dest host?

Quick look on config looks ok. Some extra ACLs that i didnt see used are in there.

Can both wired and wireless ping a public IP?

chris.gauthier Sat, 05/29/2010 - 19:18

Are there any firewalls on the  wireless hosts?

No.  The hosts I am pinging include a Brother wif- enabled printer (that answered to pings when I had it connected wired), a netgear print server (that answered to pings when I had it connected wired), and a Vista Home Premium system with firewalling turned off.

The wired hosts include a Windows 7 PC (this one) and a linux server.

Have you wiresharked any traffic to see if it is  hitting the dest host?

Not yet.

Quick look on config looks ok. Some extra ACLs  that i didnt see used are in there.

The extra ACL's were for some testing of different scenarios, unrelated to this.

Can both wired and wireless ping a  public IP?

Absolutely.  I can watch Netflix with no problems both the wired and wireless PCs. In addition, my mother-in-law (who is staying with us this weekend) would be having a fit if her wireless laptop wasn't able to do Farmville. *rolling my eyes*

Thanks for the help.

chris.gauthier Sun, 05/30/2010 - 23:01

Here is an update...

Now it is just my Windows 7 machine that is giving me problems.

I solved the issue of pinging by changing Interface Dot11Radio0 to station-role root access-point from station-role root.  Then, I did a shutdown followed by a no shutdown on the interface.  This made it so my linux clients could see the wifi clients just fine.  However, Win7 is not seeing the wifi clients.  It still gives me errors.  I have no known security enabled.

C:\Users\Chris>tracert 172.27.44.5

Tracing route to brother.k7sle.com [172.27.44.5]
over a maximum of 30 hops:

  1  main.k7sle.com [172.27.44.7]  reports: Destination host unreachable.

Trace complete.

C:\Users\Chris>ping  172.27.44.5

Pinging 172.27.44.5 with 32 bytes of data:
Reply from 172.27.44.7: Destination host unreachable.
Reply from 172.27.44.7: Destination host unreachable.
Request timed out.
Request timed out.

Ping statistics for 172.27.44.5:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

C:\Users\Chris>

During this same time, I had 2 different linux clients (on the wired side) pinging the same address.  Worked like a champ!

Weeeeiiiirrrrddddd.  Points to a Win7 issue now. 

chris.gauthier Sun, 05/30/2010 - 23:29

looks like a router reboot solved this issue. I just don't get it.

Thank you for the response!

Actions

This Discussion

Related Content