Why doesn't ping when you disable a host?

pinguely device educause the facility, pings are lost, include a device that pings do not appear, but it is available, it is possible for example to log in via the web. If you reconnect the interface in Windows that pings will appear again.

https://www.youtube.com/watch?v=TnJbiXA7mpg
June 14th 19 at 20:15
1 answer
June 14th 19 at 20:17
ping -t in Windows pings the session, Mikrotik apparently sends a one-time queries.
make ctrl+c in cmd and run the ping again, most likely he will go again.
if not, then the problem is something else.
Something else - this may be the route did not arrive (which is unlikely, because the web ip is opened), or where the filtering rule has not arrived.
no, doesn't help, pings are restored only after you disable and then enable the interface in Windows - Orpha commented on June 14th 19 at 20:20
then the problem is clearly in the route\rule.
Routes will see what appear\disappear after you disable the vpn on your client.
in Windows it's netstat-r (-rn)
If routing is not - see the rules Windows (win firewall) on Mikrotik or intermediate equipment. There may be something somewhere is updated or just have a unilateral rule with keep state. - sven28 commented on June 14th 19 at 20:23
static route, firewall disabled - Orpha commented on June 14th 19 at 20:26
read again what I wrote:
Routes will see what appear\disappear after you disable the vpn on your client.
in Windows it's netstat-r (-rn)
If routing is not - see the rules Windows (win firewall) on Mikrotik or intermediate equipment. There may be something somewhere is updated or just have a unilateral rule with keep state. - sven28 commented on June 14th 19 at 20:29
client VPN no - Orpha commented on June 14th 19 at 20:32
OK, routes, and rules never change? when disconnecting VPN - sven28 commented on June 14th 19 at 20:35
don't change just for the tick, which raised the VPN server is reset (deleted) route, and when VPN client is connected it will be automatically created - Orpha commented on June 14th 19 at 20:38
miracles do not happen. reason globally, can be 4:
1) keep state - checked not working
2) routing - you say that the routes are all correct and nothing is added when on / off adapter
3) filtration - the same p 2
4) something low-level, tied to hardware or driver\NIC,

if items 2 and 3 100% not Your case, try to test on another machine with another OS. If you come to dig in this direction - sven28 commented on June 14th 19 at 20:41
Like a glitch Mikrotik. Not just things with other device and Windows - pings normally get up. With microtia the experience was not.
This happens on all computers? There is a possibility to repeat the experience on Linux? - Lucio commented on June 14th 19 at 20:44
Yes, I tried to deploy next WM tick, and the same problem. 59d5013f11390130463033.jpeg
Mikrotik and wind - VM - Orpha commented on June 14th 19 at 20:47

Find more questions by tags System administration