Windows 2016 RDP issue.
Hello,
I am getting the attached error when trying to RDP to a Windows 2016 server. The server has no windows firewall and no third party antivirus software enabled.
telnet test to the server via tcp 3389 is fine and RDP service is running on the server.
Please advise if you see anything we should check.
I was doing a software update on the server before the issue happens. The server is running in vmware and I have reverted back the snapshot.
Many thanks.
RDP-error.png
I am getting the attached error when trying to RDP to a Windows 2016 server. The server has no windows firewall and no third party antivirus software enabled.
telnet test to the server via tcp 3389 is fine and RDP service is running on the server.
Please advise if you see anything we should check.
I was doing a software update on the server before the issue happens. The server is running in vmware and I have reverted back the snapshot.
Many thanks.
RDP-error.png
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Firstly, turning off the Windows Firewall places it in a form of limp mode. It does not turn off like a light bulb does with a switch. Instead of turning it off, turn logging on for all three profiles and make sure it's on for same. Then, check the logs to verify if it is dropping the expected packets.
Secondly, make sure inbound RDP is enabled for Remote Access via Computer --> Properties.
NOTE: There are variations between Windows versions as far as exceptions for the Remote Desktop Protocol goes. If using Group Policy to set the exceptions keep in mind that some settings like TCP 3389 Inbound for certain versions of Windows may be needed to get things going in a heterogeneous Windows environment.
Secondly, make sure inbound RDP is enabled for Remote Access via Computer --> Properties.
NOTE: There are variations between Windows versions as far as exceptions for the Remote Desktop Protocol goes. If using Group Policy to set the exceptions keep in mind that some settings like TCP 3389 Inbound for certain versions of Windows may be needed to get things going in a heterogeneous Windows environment.
I thought you rdp goes to a disabled state with the firewall off. Can you try turning it on?
ASKER
The server is up. When I go to Windows Updates, I am seeing the attached screen for a long time. I have restarted the server couple of time but it does not help.
windows-updates..png