Users on a LAN are unable to get to a company web server but are able to get elsewhere. What should be done or checked?

If users are able to access other destinations but not the company web server, verifying that the static route to the server is present in the routing table is indeed a crucial step. This ensures that the network path to reach the web server is explicitly defined for the routers on the network.

If the static route is missing or incorrect, routers may not know how to forward packets to the server’s network, resulting in users being unable to access the web server. It’s also important to ensure that the route is not only present but also has the correct subnet, next-hop IP address, and interface. Checking the routing table can be done with commands like show ip route on a Cisco router, for example, which will display all the routes known to the router, including static routes. If the route to the server’s network is missing or incorrect, it would need to be added or corrected in the router’s configuration.