Today, we were blocked by a stupid message from Microsoft Remote Desktop Connection 2 on a user workstation’s. RDC was showing this message :
The problem was that the “windows-based” computer is a Mac OS X Terminal Server and there are enough licenses for dozens more users. The problem was system wide, others users on the same computer were affected by this error but the same user on another workstation was working fine.
General: Fluid Remote Desktop; General: Can't sign into Jump Desktop Connect. Nach Eingabe der lokalen IP-Adresse des fernzusteuernden PC kommt jedoch folgende Fehlermeldung: failed to connect: Connection refused (61). Copying and pasting between the remote connection and virtual machine doesn't seem to be supported at least on a Mac. Original Title: 'Remote Desktop Connection for Mac' I have downloaded but not able to connect. Is there a step by step manual to follow? I have done everything possible on the trouble shooting guide. I am using Windows 7 Professional. Want to be able to connect remotely using my Mac laptop.Thank you.
After some experimentation on the workstation, we noticed that the problem was from files in the directory “RDC Crucial Server Information” in the Shared directory. Simply remove the complete Microsoft folder and now RDC is working again.-->
This article provides a workaround for the issue that Remote Desktop Connection 6.0 prompts you for credentials, before you establish a remote desktop connection.
Original product version: Windows Server 2012 R2
Original KB number: 941641
After you install the Remote Desktop Connection 6.0 client update (update 925876), you may experience one or more of the following symptoms:
- Remote Desktop Connection 6.0 prompts you for credentials before you establish a remote desktop connection.
- Remote Desktop Connection 6.0 prompts you to accept the identity of the server if the identity of the server cannot be verified.
- You may be unable to use a smart card to log on to Remote Desktop Connection 6.0, even though you could use a smart card to log on to Remote Desktop Connection 5.x.
For more information about the Remote Desktop Connection 6.0 client update, click the following article number to view the article in the Microsoft Knowledge Base:
925876 Remote Desktop Connection (Terminal Services Client 6.0)
Microsoft Remote Desktop For Mac Connection Refused Working
To work around this problem, turn off the new features in Remote Desktop Connection 6.0 to revert to the features in Remote Desktop Connection 5.x. To implement this workaround, follow these steps:
Click Start, click Run, type mstsc.exe, and then click OK.
Click Options, and then click the General tab.
Click Save As, and then type a file name in the File name box.
Select the location where you want to save the remote desktop file, click Save, and then click Cancel.
The saved file has the .rdp file name extension.
Click Start, click Run, type notepad, and then click OK.
Firefox 8 for mac os catalina. On the File menu, click Open.
In the Files of type list, click All Files.
In the Look in list, locate and then click the file that you saved in step 4. Then, click Open.
Locate the line that resembles as: authentication level: i: n
The n placeholder represents the current authentication level.
Change the authentication level to 0 so that the line becomes:
When you set the authentication level to 0 , RDP 6.0 does not check for server authentication.
Add the following line to the end of the file:enablecredsspsupport:i:0
When this line is present, you do not have to provide credentials before you establish a remote desktop connection.
On the File menu, click Save.
To connect by using Remote Desktop Connection, run the file that you saved in step 12.
Microsoft Remote Desktop For Mac Connection Refused Windows 10
After you follow these steps, the new security features that Remote Desktop Connection 6.0 provides are removed. Additionally, Remote Desktop Connection 6.0 becomes incompatible with Windows Vista-based computers that have the Allow connections only from computers running Remote Desktop with Network Level Authentication option enabled in the system properties.