Difficulty: Medium
Correct Answer: Ensure the remote access server can reach a DHCP server that has an active scope for its subnet
Explanation:
Introduction / Context:
When Routing and Remote Access Service (RRAS) assigns an Automatic Private IP Addressing (APIPA) address (169.254.x.x) to dial-in clients, it indicates the server could not obtain a valid lease to hand out. Without a valid IP on the client, routing and resource access will fail, hence the timeouts.
Given Data / Assumptions:
Concept / Approach:
RRAS can deliver IPs to remote clients either from a static address pool or by acting as a DHCP proxy (obtaining leases from a DHCP server on behalf of clients). If RRAS cannot contact a DHCP server with an active scope, clients fall back to APIPA. Therefore, the remedy is to guarantee DHCP reachability and a valid scope that matches the RRAS server’s subnet, or alternatively configure a static pool directly on RRAS.
Step-by-Step Solution:
Verification / Alternative check:
As an alternative to DHCP dependency, configure a static address pool on RRAS and confirm clients receive those addresses successfully.
Why Other Options Are Wrong:
Merely “configuring the server with the address of a DHCP server” or “authorizing” without actual reachability and an active scope does not solve the root problem.
DHCP Relay Agent is used to forward client DHCP broadcasts across routers; RRAS already proxies for remote clients and primarily needs a reachable DHCP scope.
None: A direct, correct action exists.
Common Pitfalls:
Forgetting to create a scope or isolating RRAS from DHCP by firewall; misinterpreting APIPA as a client-side modem or authentication issue.
Final Answer:
Ensure the remote access server can reach a DHCP server that has an active scope for its subnet
Discussion & Comments