Wireless LAN problem

[imi83]

Hi,

I have a Notebook with Windows 7 ultimate 64 bit connected to Buffalo AirStation router. I am trying to ping another PC that connected (wired) to the same router.

When I connect my Notebook with a wire, the ping successes, but with the wireless it doesn't. Can someone help?

Following the ping output:
From Wireless:

C:\Users>ping 192.168.11.2

Pinging 192.168.11.2 with 32 bytes of data:
Reply from 192.168.11.5: Destination host unreachable.
Reply from 192.168.11.5: Destination host unreachable.
Reply from 192.168.11.5: Destination host unreachable.
Reply from 192.168.11.5: Destination host unreachable.

Ping statistics for 192.168.11.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

From wire:

C:\Users>ping 192.168.11.2

Pinging 192.168.11.2 with 32 bytes of data:
Reply from 192.168.11.2: bytes=32 time<1ms TTL=64
Reply from 192.168.11.2: bytes=32 time<1ms TTL=64
Reply from 192.168.11.2: bytes=32 time<1ms TTL=64
Reply from 192.168.11.2: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.11.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

[Maguscreed]

Can we get the exact model of the router please?
There appears to be several models. My first guess is that allowing the dmz feature for the ip in question would fix the problem. This is most likely a router security feature to prevent people on the wireless from gaining access to the wired network. There should be a method to bypass it for specific computers on the wifi but I'll need a look at the manual for your specific model to get detailed.

 

[imi83]

Thanks for your reply, the router model is Buffalo AirStation WHR-G300N

 

[Maguscreed]

Did you use the AOSS feature or connect to the router using the traditional SSID method?

 

[imi83]

I am using the traditional SSID method, the ClientManager that allow you to use AOSS is incompatible with my operating system

 

[Maguscreed]

I was hoping there would be more detail in the manual than there actually is. Look for packet filtering options in both the wan and lan settings. It's also possible given the large number of options I can just barely make out in the tiny pictures in the manual, that it has a setting to specifically block ping request (my own router does this)
Unfortunately since the manual doesn't walk through all the possible settings I don't think I'm going to be able to point you directly to it. If your router has firewall rules, you may simply try allowing for the wireless ip you are using to have full access.

I'm sorry I can't be more specific you're going to have to dig around a bit since the manual doesn't contain a full break down of the interface for me to track the setting down for you.

 

[imi83]

Could it be Windows issue? Note that I get the ping reply from my notebook, not from the router:

Reply from 192.168.11.5: Destination host unreachable.

 

[imi83]

I found a solution:

Make sure that "Separate Feature" is unticked in wireless config>basic and that "Privacy Separator" is unticked in wireless config>advanced.

thanks

 

[Maguscreed]

It is possible if there was no response at all you'd be getting nothing but request timed out messages from a simple ping attempt.
Honestly I've not dealt with simple ping requests in some time myself as all the networks and tools I've used recently have been fully windows compatible it's been easier to just use the gui for connecting.

I assume you've run 'ipconfig /all' and verified that the local data is the same for the laptop whether it's plugged in or on the wireless. this could be a simple translation issue between ipv4 and ipv6.

edit: it was ipv6 after all. Thanks for letting me know. I was actually about to fire up my laptop to try and reproduce your problem when I realized my lappy was still running xp.