The 10.1.16.1 router should be fine, as both routes are the same to that point. Question why the .76 needs to be going thru the extra 10.32.25.2 router.

It could be the webserver was recently dual-homed on the 10.32.25.x and 10.32.26.x networks, and it is favoring the 10.32.25.x route back to you. TCP connections would need consistent routes to work. If it’s dual-homed, the webserver routes may need a permanent route added depending on who can’t see the server and which solution is preferred:
1) Add a new static route to 10.34.42.0/24 using the 10.32.26.x router.
2) Change the metrics of the default routes 0.0.0.0 so the 10.32.26.x router is preferred.

If my assumptions and the tracerts are all correct, the router is likely the 10.1.16.2 and has an interface 10.32.26.1 for that subnet.

But a word of caution: some companies, esp larger corporations, would frown upon publishing IP address schemes and tracerts on a public website. If you don’t own the network or the webserver, careful how you present your ideas towards the problem.

Also for a large corporation, there should be some change-mgmt/trouble ticket from the timeframe the website became unreachable, either for the webserver or its gateway router. Maybe someone can find this ticket to determine what happened.

Good luck!

Web servers (and some routers too) often block/ignore these to avoid the “Ping of Death” type Denial of Service attacks.

Sometimes the blocking is based on IP. Home workstations are often less trusted than a IPs of a business partner or government office.

I’d look back at the webpage message itself. “Oops!…” isn’t a normal IE or FireFox internal mesage (you didn’t mention browser type) but is a typical open source web server error message.

So I am wondering if your home workstation is simply being blocked/filtered from accessing the page based on IP address.

Something else that is odd in your tracerts. The one that reaches it’s destination ends with “request timed out” instead of “Trace complete”. I’m not sure what would cause that, but it’s not right. I’m still suspicious of router issues.

D

I disagree with petrol about routing. You are on subnet 10.34.42.xx, your web server is on 10.32.26.xx. Different subnets as far as I can see.

The tracerts you posted are interesting. When you trace to the web server, the fifth hop is 10.32.25.2 . When you trace to the other address the fifth hop is the address you are trying to hit.

I would suspect a problem in the routing tables on the 10.1.16.2 router.

If you hook up your laptop or use someone else’s computer, what does the tracert look like? Also, what ip address do you get? It could be that you are assigned an address in a different subnet, or that your coworkers computer has an address in a different subnet. This could produce different results.

If you don’t have access to the routers, I don’t think that you will be able to fix this on your own.

D

Since the webserver (.76 address) is on the same subnet as your computer it should not be transversing a router, therefore the problem must lay somewhere between your local computer and the webserver. Anything beyond that would affect other machines on the subnet.

From your computer run the command C:>ipconfig /flushdns to clear out any corrupt entries in your local DNS resolver cache. Now from the webserver run first C:>ipconfig /flushdns to clear the DNS resolver cache on the webserver, then run C:>ipconfig /registerdns to force a re-registration of the webserver’s DNS information with the DNS server responsible for your subnet.

Since you are able to hit the website from other computers on your subnet and your not transversing a router it leads me to believe that the problem is in the DNS resolver cache because if an entry (right or wrong) exists in the cache, this is where the process stops. It only moves up the chain if an entry is not available.

Good luck!

You say that tracert fails at the .76 address directly. I would be suspicious of the router that is right before that. It may have an incorrect return route to you. Have you spoken to the administrator of that router?.

D