• Post author:
  • Post category:Blog
  • Reading time:4 mins read
  • Post last modified:March 16, 2024

Employees are unable to connect to servers on one of the internal networks. What should be done or checked?

  • Use the “show ip interface brief” command to see if an interface is down.
  • Verify that there is not a default route in any of the edge router routing tables.
  • Check the statistics on the default route for oversaturation.
  • Create static routes to all internal networks and a default route to the internet.
Explanation & Hint:

When employees are unable to connect to servers on one of the internal networks, several steps should be taken to diagnose and resolve the issue:

  1. Use the “show ip interface brief” Command:
    • This command will display the status of all interfaces on a router or switch. Check for any interfaces that are down, particularly those that should be connected to the affected network. An interface in a down state could indicate a physical connectivity issue, such as a disconnected cable or a hardware failure.
  2. Verify the Routing Table:
    • Ensure that the correct routes are present in the routing table of the routers. This includes checking for specific routes to the internal network where the servers reside.
    • If a route to the internal network is missing, packets destined for that network might be incorrectly routed or dropped.
  3. Check the Default Route:
    • Verify the presence and correctness of a default route in the routing tables, especially if the issue is with external connectivity. However, if the problem is solely with accessing internal servers, the default route may be less likely to be the issue.
    • Checking the statistics on the default route for oversaturation is also a good practice. If the default route is oversaturated, it could lead to performance issues, but this is more relevant for internet-bound traffic rather than internal network traffic.
  4. Review Access Control Lists (ACLs) and Firewall Rules:
    • Check if any ACLs or firewall rules are blocking the traffic to the servers. Sometimes, changes in these configurations can inadvertently block legitimate traffic.
  5. Network Health and Performance:
    • Look for signs of network congestion, oversaturation, or equipment issues that might be affecting traffic flow to the servers.
  6. Physical Connectivity and Network Hardware:
    • Verify physical connectivity. Ensure that cables, switches, and routers that connect to the affected servers are functioning correctly.
  7. Create Static Routes to Internal Networks (if necessary):
    • If dynamic routing is not properly distributing routes, or in a smaller network where dynamic routing might not be implemented, creating static routes to internal networks can ensure proper routing. However, this is typically considered when a new network segment is added or when changes are made to the network structure.

Given these options, the most immediate and relevant action would be to use the “show ip interface brief” command to check the status of the interfaces. This could quickly reveal if there is a straightforward connectivity issue. Subsequent steps would involve deeper investigation into routing and network configurations.

For more Questions and Answers:

CCNA 2 v7 – SRWE v7.02 Final Exam Answers Full 100%