220-1102 Question 803
Single answerRDPA technician needs to remotely access a user's Windows 10 Pro office PC from another room to install a line-of-business application. The PC is powered on and connected to the network, and the technician can successfully ping it by hostname. However, when attempting to connect with Remote Desktop Connection, the technician receives a message that the remote computer is not accepting connections. Which action should the technician take FIRST on the user's PC to resolve the issue?
- A
Enable Remote Desktop in System settings and allow Remote Desktop through Windows Defender Firewall
- B
Install the Telnet Client feature and test connectivity to TCP port 23 on the remote PC
- C
Add the technician's account to the local Power Users group on the remote PC
- D
Disable Network Level Authentication on the remote PC so older clients can connect
Show answer and explanation
Correct answer: A
Explanation
This question tests practical RDP troubleshooting in a Windows environment. A successful ping confirms basic network connectivity and name resolution, but that does not mean the RDP service is enabled or permitted. On Windows 10 Pro, Remote Desktop host capability is available, but it must be turned on in Settings/System/Remote Desktop or the equivalent system configuration tools. When enabled, Windows typically also configures the appropriate firewall exception for Remote Desktop. Best practice is to verify edition support first as well, since Windows 10 Home cannot act as an RDP host. Network Level Authentication should remain enabled unless there is a known compatibility issue. Microsoft documentation for Remote Desktop on Windows notes that the host must support Remote Desktop, have it enabled, and permit access through the firewall.
- A. Correct.
Correct. On Windows 10 Pro, Remote Desktop must be enabled on the target PC before it will accept inbound RDP connections. Enabling Remote Desktop also typically configures the required Windows Defender Firewall rules for RDP. Since the technician can already reach the host by name and ping it, the most likely issue is that the PC is not configured to accept Remote Desktop connections.
- B. Incorrect.
Incorrect. Telnet and TCP port 23 are unrelated to Remote Desktop, which uses RDP over TCP port 3389 by default. A candidate might choose this option if they confuse general remote access tools with RDP-specific requirements.
- C. Incorrect.
Incorrect. Membership in Power Users does not grant the ability to connect via Remote Desktop. For RDP access, the user must generally be an administrator or a member of the Remote Desktop Users group on the target system. Even then, the PC must still have Remote Desktop enabled first.
- D. Incorrect.
Incorrect. Disabling Network Level Authentication is not the first step and is not generally recommended unless there is a specific compatibility problem with an older RDP client. The scenario indicates the computer is not accepting connections, which is more consistent with Remote Desktop not being enabled than with an NLA mismatch.