Problem solve Get help with specific problems with your technologies, process and projects.

Bring Back PING in Win10 1803

The old putatively Chinese curse goes “May you live in interesting times.” And in that sense, interesting is the adjective I’d apply to networking in Window 10 Version 1803 of late. My previous blog post explained my difficulties in resolving a NetBIOS name, only to figure out that it was case-sensitive when it shouldn’t be. Today, I’m discovering that some upgraded systems lose their ability to respond to a PING from the LAN. This took some sleuthing, but I figured out how to bring back PING in Win10 1803.

How to Bring Back PING in Win10 1803

I can’t replicate this on all my upgraded machines. But I have observed that at least two PCs here on the Chez Tittel LAN have lost their ability to respond to PING requests in the wake of the 1803 upgrade. As it happens, PING relies on the ICMP Echo command to do its thing. And sure enough, in investigating the potential causes of a “missing PING response,” firewall settings head that list. On my two affected machines, both running Windows Defender and its firewall, the Inbound rules for File and Printer Sharing (Echo Request) for both ICMPv4-In and ICMPv6-In were not enabled for any profile: Local/Private (what I wanted), Public (left disabled) and Domain (also enabled). Here’s what the resulting set of rules looks like after the change:

Bring Back PING in Win10 1803.inbound rules

I enabled Private and Domain for both IPv4 and IPv6, but left public turned off. A PING response on a Public network is an invitation to attack!
[Click item to see full-sized view.]

If you find yourself in the situation where you can see a local PC using arp or nbtstat, but it won’t respond to a PING, odds are excellent that this fix will help you, too. Keep this in mind as you upgrade to 1803 going forward. By the time your organization or company takes the plunge, it may be moot. But I still believe that forewarned is fore-armed!

More Win10 Network Follies A’Comin…

As I was digging into this issue, I discovered a couple of other interesting networking gotchas. I haven’t had time to tackle them yet, but will do so as soon as I can. Gotcha #1 is that on at least one of my PCs (one running the Insider Preview), IPv6 has gone missing. Gotcha #2 is that my T520 machine (the subject of my previous post) will now happily connect to or ping either “t520” or “T520.” But alas, my X220 Tablet works only as “x220t” not as any of the other possible permutations: “X220t”, “x220T,” or “X220T.” Weird!

Join the conversation

1 comment

Send me notifications when other members comment.

Please create a username to comment.

Ed, thanks for your posts. I especially appreciate the clarity of your descriptions and LACK of a "this WILL fix your problem".

Any further updates related to this? I've been battling the network ever since I upgraded to 1803 and have as yet been unable to resolve much with any certainty. That is, an RDP connection failing due to case is a pain, but if that were the only item, I'd have much more hair at this point. I believe it to be symptomatic of other issue (or more).

I have 4 PHYSICAL machines on my LAN and several VIRTUAL machines (Hyper-V), all Windows 10 with the 1803 update. I created a script to have each of them loop and do 3 simple commands: Ping, Dir, & Copy from/to each of the 6 machines. The results basically confirm that it's INTERMITTENT. That is, if I pick 2 machines (source/target) and a command (Ping), it WORKS some of the time and FAILS some of the time. That's true for the other 2 commands as well, and I'm pretty sure (without actually individually analyzing every combination) that the others are as well.

A side-note is that the configuration at my employer is very similar (small office). There I removed (rolled back) from 1803 and the stability I had been experiencing before the update returned. So I'm personally pretty darn certain that 1803 is the culprit.
Cancel

-ADS BY GOOGLE

SearchVirtualDesktop

SearchWindowsServer

Close