Is SEP causing this change in ping behavior?
We updated from 12.1.14 or .11 to 12.1.2 about a month ago. Maybe it was that or a recent update of another kind.
A simple ping is behaving differently.
Before I got...
Destination port unreachable. after sending a ping to a machine that's not on.
Now/today I get...
Reply from (my local computer's ip address): Destination host unreachable.
Nothing with Windows updates. We've figured that out.
Two computers without SEP on it behave the old/normal way
One comupter without SEP gives me the old/normal ping results from I ping from another comupter and the targe/non-SEP computer is off. Weird.
All the computers are on our subnet. I'm wondering what's changed recently. We used to have 'dest port unreachable.' I have read several pages online that say if it's on your subnet, it's only one hop, and the pinging computer knows the device isn't there and just displays 'dest host unreachable.'
It's a problem because I've got several batch files monitoring machines. If it's on, it pings back and error level is 0. Today if it's off, I get 'dest host unreach' and still the error level is 0. The batch file responds as if it were on. The old way gave me either a time out (which I read shouldn't happen, but it was and that's ok) or a 'dest port unreachable' with an error level of 1. That was fine. I used the error state, 0 or 1, to control whether alerts are sent out, etc.
Is anyone else using SEP having issues with pings not working 'normally?'