RRAS dial-up client receives 169.254.x.x (APIPA) on a private network (192.168.0.0). Connection succeeds, but no resources are reachable (pings time out). What server-side action resolves the addressing issue so dial-in clients receive valid IPs?
-
AConfigure the remote access server with the address of a DHCP server
-
BAuthorize the remote access server to receive multiple addresses from a DHCP server
-
CConfigure the remote access server to act as a DHCP Relay Agent
-
DEnsure the remote access server can reach a DHCP server that has an active scope for its subnet
-
ENone of above
Answer
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:
- Private network uses 192.168.0.0 addressing.
- RRAS is installed; dial-up connects but lacks usable IP configuration.
- ipconfig on the client shows 169.254.75.182 (APIPA).
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:
Verify that a DHCP server exists and has an active scope for the RRAS subnet.Ensure Layer-3 connectivity between RRAS and DHCP (no filters blocking UDP 67/68).In RRAS IP assignment settings, select DHCP and confirm leases are obtained.Reconnect a client and confirm it receives a valid 192.168.x.x address and can reach resources.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