Windows 10 since 1803 cant ping (most of the time) by ipv6 or rdp?

markm75 · 20 Aug 2018

I have a problem with my desktop since i ran the update to 1803..If i do a ping machinename (in this case a 2016 server)..
it will say cannot find host name.. if i keep hammering it, eventually one ping might go through.Same deal with RDP.

My network consists of a netgear wifi accesspoint/router with the server and desktop (i also have this same issue with a laptop that was updated).

Has anyone ran into this and found a fix?I have already tried netsh resets to the stack and winsock without success. I'm pretty sure if i were to disable ipv6 on the desktop/server it would be fine and use that as the preferred connection (ping -4 machinename works all the time).. but thats not a solution either.

Thanks in advance

markm75 · 20 Aug 2018

i should add, that, though the ping command will immediately fail most of the time.. if i do a ping and say n 50, for 50 tries and i get it to work, none of those fail throughout that test which is odd, given it seems intermittent.

markm75 · 20 Aug 2018

I tried disabling ipv6 on both the server and workstation.. same issue randomly occurring.
Again, if you hammer the command to ping it eventually does go through and it will succeed for n times too, but that initial attempt will fail mostly.
In the netgear router there is an ipv6 section, its disabled.. but given i disabled both ipv6 on both server/workstation and it still fails, i still feel like this is a win10 issue not with the netgear.. and the netgear has always been disabled.. this only changed after the 1803 update

edit: enabling ipv6 in the netgear admin console didnt help either

update: re-disabling ipv6 on both ends and doing the flushdns ipconfig and registerdns and waiting does seem to have fixed this.. but again, not really a fix.. what could have changed from before 1803 to now to make this a requirement However, the laptop despite disabling ipv6, seems to still have the same issue.