Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am finding more and more users that report they cannot reach my server (website or services). Their tracert from that user looks like this:

Tracing route to [*.*.*.255] 
over a maximum of 30 hops: 
1 * * * Request timed out.

The server is up and functional and every else reports it is fine. But there are various users who cannot get to it. I have no firewall or anything that would block anyone.

Yes, the last part of the server IP is 255. Could this be causing it?

Or would a certain ISP be denying traffic to my server?

Or something on their router level?

share|improve this question

That IP is definitely one I would avoid. Even if the end users devices can handle a .255, there's a chance some bad config anywhere between your server and your users might also be mishandling the traffic. Guessing it's a hold-over from the old class-based way of handling subnets.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.