220-801 · Question #199
A user is trying to use Remote Desktop to connect to another computer on the LAN. The connection fails. The technician opens up a command prompt and types the followinG. "telnet computernamE. 3389"…
The correct answer is C. The RDP connection has been configured to use a non-standard port. The telnet test to port 3389 confirms nothing is listening on that port, which means RDP is either not running or configured to use a non-standard port. Since this is a LAN connection, the ISP cannot block internal traffic (eliminating B). If telnet were not installed, the…
Question
A user is trying to use Remote Desktop to connect to another computer on the LAN. The connection fails. The technician opens up a command prompt and types the followinG. "telnet computernamE. 3389" and also gets the same error message. Which of the following is the MOST likely cause of this error, assuming that the OS firewall has been disabled?
Options
- AThe antivirus software is blocking the incoming connection.
- BThe ISP is blocking Remote Desktop at their end.
- CThe RDP connection has been configured to use a non-standard port.
- DThe telnet service has not been installed.
How the community answered
(42 responses)- A5% (2)
- B17% (7)
- C71% (30)
- D7% (3)
Explanation
The telnet test to port 3389 confirms nothing is listening on that port, which means RDP is either not running or configured to use a non-standard port. Since this is a LAN connection, the ISP cannot block internal traffic (eliminating B). If telnet were not installed, the error would say the command is not recognized - not match the RDP error (eliminating D). Antivirus software could block connections, but reassigning RDP to a non-standard port is the most direct explanation for why port 3389 is unreachable despite the firewall being disabled.
Topics
Community Discussion
No community discussion yet for this question.