cannot ping web server from network

I cannot ping our web server co-located at a web hosting company. This is only if i'm using a computer in our company network. There's no problem if i try pinging from outside.
The website can be seen from outside the network.

I can browse all other sites with no problem. Even the other server that we have also co-located side by side with this one.

Anyone have any idea why is this so? i would appreciate any advice.

--- djhun

Im assuming your ISP gave you a public address on your router and your web server is about 2 or three hops away and your ISP gave your web server an address that is in a subnet of your Public IP (using VLSM). Trace to the server from within your network. Then have the ISP trace from the server to your network most likely the server never even made it to the first hop router and was not given the correct subnet mask and thinks your network is the same as its own.

example... your public address is 192.168.1.2/28
and the web server address is 192.168.1.128/24
The web server will arp for your address and not forward to its default gateway since it thinks your on the same network.
Put a static route on the server for your address.

My guess is your company network firewall is blocking icmp traffic.

Im assuming this is not an ICMP issue due to this quote and me thinks he cant veiw the web site either but he can on the server co-located with this one. However, you do have a point there may be ACL's in place prohibiting this.

Thanks juniper, doug for the info/suggestion. I'm more of a programmer than a network/system admin so please bear with me. I'll try to describe the problem in more details as much as I can. Here goes.

The site has been operational until we suddenly cannot browse it from our network.
We can ping the other web server co-located the same as this one.
Our web hosting company is different from our ISP.
When I try tracert, the trace goes thru the ISP and then to our host and finally times out on the final hop to the web server. (I compared the trace with the one on the other server that is ok.)
The other thing is, we have setup the (SSH, putty) on the web server to accept only the IP address of our company firewall, so if this IP addr is rejected or whatever, there is no other way to access it other than go to the server site.

Do you think rebooting the server will solve the problem?
Last thing I can do is change the IP addr of our firewall but that means also adding the new IP on the list allowed access on the server.

If you did a trace all the way to the last hop router that meens that there is most likely an issue with the server itself for the simple fact that the last hop router replied to you and has a path back but the server tries to reply and does not send to the router or drops it due to an acl or something. you need to access the server and try and trace back. ( sounds to me it will imediately drop the packet or if it does make it your firewall is dropping it. I cant tell you where the problem is without a return trace from the server.