up vote 3 down vote favorite
1
share [g+] share [fb]

Today I tried printing on a shared printer on one of our homegroup members. Sadly it did not work (printer marked as offline). Shortly after, I noticed I can't even ping the machine that owns the printer (I also can not remotely access it in any other way I've tried).

Currently I'm trying to ping the machine from the router both computers are connected to (and my machine in question doesn't answer). I do receive the echo requests (as verified with WireShark). I also added a rule in the Windows Firewall to specifically allow ICMP echo requests, but that didn't change anything. I also tried netsh firewall set icmpsetting 8 enable, but that didn't change anything either. Completely disabling the Windows Firewall has no effect on the issue either.

Where does Windows log when and why it ignored any incoming packets? How can I get to the bottom of this?

Here are some ways I found to dig deeper into the issue:

Both methods at least give more insight into the issue. The plain log file is full of entries like this:

2011-11-11 14:35:27 DROP ICMP 192.168.133.1 192.168.133.128 - - 84 - - - - 8 0 - RECEIVE

So the ICMP packets are being dropped as if that was intended.

The Event Viewer now gives a little bit more details:

The Windows Filtering Platform has blocked a packet.

Application Information:
Process ID:             4
Application Name:       System

Network Information:
Direction:              Inbound
Source Address:         192.168.133.1
Source Port:            0
Destination Address:    192.168.133.128
Destination Port:       8
Protocol:               1

Filter Information:
Filter Run-Time ID:     214517
Layer Name:             Receive/Accept
Layer Run-Time ID:      44

This same entry is always repeated with two points of information changing:

Process ID:             420
Application Name:       \device\harddiskvolume2\windows\system32\svchost.exe

The service host with the PID 420 is the host for the following services:

  • Windows Audio
  • DHCP Client
  • Windows Event Log
  • HomeGroup Provider
  • TCP/IP NetBIOS Helper
  • Security Center

Additionally, there is currently this problem with the same machine:

Windows is confused about the type of network

Even though my network is set to be a "Home network", I am unable to create a new homegroup.

link|improve this question
88% accept rate
Are the devices connected across a router, or is this a SOHO router with switch ports that the devices are connected to? Are the devices on the same IP network? It is also my understanding that if your device is configured as Public in Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings then ICMP is blocked. – dbasnett Nov 11 '11 at 15:57
@dbasnett I'm currently testing from an SSH session on my router, which the target machine is connected to via cable. It's the same network. In the dialog you noted, "Home or Work" is marked as "current profile". – Oliver Salzburg Nov 11 '11 at 17:14
can you ping locally i.e. e.g. ping 127.0.0.1 ? – barlop Nov 14 '11 at 3:16
@barlop Yes, pinging any of my local or loopback addresses works just fine. – Oliver Salzburg Nov 14 '11 at 17:05
@gencha loopback works and local LAN ones like 192.168 don't work.. Really filtering sounds like a firewall function.. so you want to get to those settings. Whenever I look up about configuring windows filtering, I get programming stuff. So I suggest asking on Stackoverflow, and put windows filtering platform in the subject. A bit like this question stackoverflow.com/questions/5077164/… and you may get somebody that can code the configuration. – barlop Nov 14 '11 at 22:07
show 2 more comments
feedback

closed as too localized by Sathya♦ Feb 27 at 12:55

This question is unlikely to ever help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. See the FAQ for guidance on how to improve it.