Home » Posts tagged 'RDP'

Tag Archives: RDP

RDP Error – The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.

Unable to connect to the Remote Desktop. Server operating system is Windows Server 2012 Standard R2. When we try to RDP, we get the below error message:

The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.

There was two server with same configuration and setting but one of connecting to RDP with AD authentication whereas the other was not working. One was physical and the other was virtual hosted on an ESX host.
RDP on physical was good and the issue was with the virtual host. It was confirmed that the issue was due to time latency.
Therefore, this issue was due to the time difference between the virtual machine and the NTP server set on an ESX host.
This issue was later fixed by synchronizing the server time with the ESX host.

Note:
If you do not wish to have auto sync, disable the Windows Time service or block the outbound port 123 on your local firewall.

Thanks,
WintelAdmin

Fix RDP on Windows 2003 without reboot.

A very common issue on a daily life of a Windows server administrator is that the users complaining about RDP issue. If the issue is with Windows 2008, that’s fine as we can restart the remote desktop services to fix the issue. But the same issue on Windows 2003 is bit annoying.

However, I have found a solution which works perfect.

The fix: (remotely using command prompt)

tasklist /s \\servername /svc /fi “imagename eq svchost.exe” (locate PID for TermService)
taskkill /s \\servername /pid xxxx (may need /f to force, UAC might give problems as well)
sc \\servername start TermService

The Fix: (local, using command prompt)

tasklist /svc /fi “imagename eq svchost.exe” (locate PID for TermService)
taskkill /pid xxxx (may need /f to force, UAC might give problems as well)
sc \\servername start TermService

Detailed Information:

Open a command prompt
Type in: tasklist /svc /fi “imagename eq svchost.exe”
This will list the different instances of svchost.exe and the associated service and PID
Locate TermService and note the PID for it
Open Task Manager and go to the Processes tab. Then click View > Select Columns and check PID, then click OK
Locate the svchost.exe process with the PID noted in step 4, right click it, select End Process
Open services.msc
Start the Terminal Services service

Thanks,
WintelAdmin

Fixing Remote Desktop (Unnecessary pop-up)

 

Microsoft Remote Desktop is a great tool for connecting to any windows machine on remote. Sometimes, when you are in need of working on many different machines, you get irritated by annoying pop-up like asking username and password before connecting to the server and annoying remote identity pop-up. This needs our manual intervention and sometime delays our task. Hence, found a suitable option to disable these pop-ups. It’s very simple, please follow the below steps:
1. Close all remote desktop connections and exit the remote desktop client.
2. Click Start, click Run, type notepad, and then click OK.
3. On the File menu, click Open.
4. In the Files of type list, click All Files.
5. In the File name box enter Default.rdp (The full path to this file would be similar to the following: C:\Users\<your username>\Documents\Default.rdp)
6. At the bottom of the Default.rdp file, add the following text:
enablecredsspsupport:i:0
authentication level:i:0
7. Save the file and exit notepad.
8. You should no longer be prompted to enter credentials before connecting to remote desktops and confirm that you do indeed intend to connect.

Thanks,
WintelAdmin.com

Black screen when I connect to my Windows server via RDP

Why do I get a black screen when I connect to my Windows server via RDP (Remote Desktop)?

This issue is a known Windows bug that occurs when the primary drive ( C: ) runs out of available free space. When this happens, Windows often overwrites control panel color settings for the desktop and login screen, resulting in the “blacked out” login screen and/or desktop.

When the login screen is black, you can often still access the normal Windows desktop, you just have to alt/tab through the various login screens:

When you first connect via RDP, there are two blanks you can tab through, the top one being the username (which should be Administrator,or, whatever you have set as your admin name), then, when you tab again, you will be in the password field. After entering the username and password, you should be able to Tab/Enter, and gain access to the system. If the system was just recently rebooted without warning, another screen (black) will pop up, asking why the server was rebooted. You can type anything here, and tab/enter again.

Remote Desktop Protocol

Developed by Microsoft, which concerns providing a user with a graphical interface to another computer. By default the server listens on TCP port 3389.

Switch to connect to server console via RDP.

on RDP Client v5, use mstsc /Console
on RDP Client v6, use mstsc /admin

Here is the screenshot showing the difference between RDP Client v5 & v6

This is RDP Client v5
RDP Client Version 5

This is RDP Client v6
RDP Client Version 6


Visitors Count

Subscriber Count

    4029
June 2017
M T W T F S S
« May    
 1234
567891011
12131415161718
19202122232425
2627282930