When i tried to ping 172.23.254.220 from C:\WINDOWS\systems32\cmd.exe
C:\Users\aj>ping 172.23.254.220
I get the following results

Pinging 172.23.254.220 with 32 bytes of data:
Reply from 172.23.254.220: bytes=32 time=3ms TTL=249
Reply from 172.23.254.220: bytes=32 time=2ms TTL=249
Reply from 172.23.254.220: bytes=32 time=2ms TTL=249
Reply from 172.23.254.220: bytes=32 time=2ms TTL=249

Ping statistics for 172.23.254.220:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms


However When I try to ping 172.23.254.220 from this server at work, I get this output:
PING 172.23.254.220 (172.23.254.220) 56(84) bytes of data.
From 172.23.254.219 icmp_seq=1 Packet filtered
From 172.23.254.219 icmp_seq=2 Packet filtered
From 172.23.254.219 icmp_seq=3 Packet filtered
From 172.23.254.219 icmp_seq=4 Packet filtered

Can anyone tell or explain to me why ?

Your work seems to filter ICMP. This is often done as a security measure.

jattis03

i take it that you are unaware that this is a LINUX forum and not a Microsoft one

Also this is the Member INTRODUCTION!!!!! thread and NOT a tech support thread

recommended to be moved to the NON-Linux thread

Well john VV, When i join this site i did not join to hear comments from rocket scientist like you telling folks stuff such as
(i take it that you are unaware that this is a LINUX forum and not a Microsoft one.Also this is the Member INTRODUCTION!!!!! thread and NOT a tech support thread.recommended to be moved to the NON-Linux thread)

If you are so smart and read my question you would have known that (icmp_seq=1 Packet filtered.
) is related to linux
Next time do your homework before you post such dumb comment.

You do understand that:

a) Not all members even read this forum.
b) This is for "Member INTRODUCTIONS", NOT technical threads.

??

Thread and OP reported.

Actually on the surface it appears that while at home you are running cmd.exe from C:\windows which is certainly not Linux and from work you could be running Windows through a Linux intranet server. With unexplained misqcues like that you have no reason to be snarky. A simple explanation would have stopped the issue cold but with a warmer touch.

(Gentlebeings,™ when it comes to matters of networking, "these two worlds are really no different.")

It simply appears that your workplace is running a firewall, and that this firewall is set to REJECT the packet, instead of silently DROP-ping it.

Since "the Powers That Be" chose "reject," the sender – ping – is notified and thus is able to produce the "filtered" message. (Otherwise, "drop," it would have received no clue at all, and would have timed out.)

What your company is doing is perfectly ordinary ... and, prudent.