A technician is troubleshooting a server that is inaccessible to customer at a remote site but accessible to customers locally. The only configuration that has changed is the internal IP address…

DHCP dynamically assigns IP addresses to end-client devices and plays no role in forwarding routed traffic toward a server whose IP has already been changed.

DNS resolves hostnames to IP addresses, but if clients access the server by IP directly, a stale DNS record would not explain the remote-only failure described.

A firewall rule restricts traffic based on policy criteria such as IP and port, but a policy block would typically affect both local and remote clients equally rather than only remote ones.

A routing table maps destination IP prefixes to the appropriate next-hop interface for forwarding packets across network segments. When the server's internal IP changes, any static or summarized routes pointing to the old address become stale, so remote clients' packets are dropped or misdirected. Local clients on the same subnet communicate at Layer 2 and bypass inter-segment routing, which explains why local access still works while remote access fails.