RDP to Server 2008

I have an XP SP3 PC and I am unable to use RDP to connect to a Windows 2008 server:
"An authentication error has occurred (0x80090303)"
I'm using system32\mstsc.exe, version 6.0.6001.18589
The server is in a different domain.

try the solution suggested here
http://social.technet.microsoft.com/forums/windowsserver/en-US/a60dafb0-382f-4865-b29f-678daf0fae67/xp-sp3-rdp-wont-connect-reposted-in-rdp-forum

Similar Messages

Unable to print to local Printer over RDP - Windows Server 2008

Hi,
Windows 2008 Foundation R2.
Started to have issues with printing to a Local printer over RDP.
The problems started on Friday 11th April. The only possible issue I can identify is that around that time LogMeIn was updated on the server, including the LMIPrinter DLL's. I have contacted Logmein for instructions on how to uninstall LMI completely
and followed these but am still experiencing the problem.
When attempting a Test Page print the confirmation that the Test Print has been sent to is displayed and the print appears then disappears in the Print queue but nothing appears on the Local PC print queue or event logs.
On the server the Event Log shows the following error;
The document Test Page, owned by admin, failed to print on printer Canon MG7100 series Printer (redirected 2/copy 1). Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 142691. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\ONESTAGE-TS01. Win32 error code returned by the print processor: 2147500037. Unspecified
error
I have searched for possible solutions to RDP printing problems and where relevant implemented them but no change.
I have access to a second customer who uses RDP and am able to log onto that and print to my local printer so am pretty sure there is nothing wrong with the local printer or settings. On the Server with the problem the problem affects all RDP users
and all printers (including Adobe PDF printer and MS XPS printer). All printers are defaulting to the EasyPrint Drivers.
Grasping at straws I think the LMI update has banjaxed something with the RDP remote printing and an LMI uninstall hasn't fixed it. Is there a way to reinstall the RDP Printing? Would uninstalling & reinstalling .NET have that effect?

Hi,
Thank you for posting in Windows Server Forum.
What’s your client OS and RDP version in your environment?
First of all suggest you to run “sfc /scanow” with this link to check whether which file causing the issue. Check the RDP version on the RDP client computer as well as the .NET framework version with respect to the operating system used (as explained above).
Also verify that the RD Session Host / Terminal Server role is installed if the host computer is running Windows Server 2008 R2 or Windows Server 2008.
The setting “Use Remote Desktop Easy Print printer driver first” must be set to “Enabled” for Easy Print redirection, and it has to be “Disabled” for Legacy Print. For “Not configured”, Easy Print is chosen by default.
Check The Remote Desktop Configuration Tool (tsconfig.msc) settings to ensure that the “Windows Printer” option is not disabled (it is not disabled by default).
Make sure that the “Printers” check box in the client (mstsc.exe) window on the “Local Resources” tab is checked. The corresponding setting in the associated RDP file is “redirectprinters:i:1”.
More information:
Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2
http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx?Redirected=true
Hope it helps!
Thanks.
Dharmesh Solanki

Server 2008 R2 Terminal Server c0000005 and c0000006 errors with KERNELBASE.dll error in RDP sessions.

We installed a new Server 2008 R2 server this spring. It is configured as a Terminal Server with 16 Wyse t10 thin clients connecting with RDP. We are a small resort so we run Springer Miller Host and SpaSoft. Ever since moving from PCs to the thin clients
and TS we have been seeing SpaSoft randomly crash with KERNELBASE.dll errors and also a lot of c0000005 and c0000006 errors. Springer Miller support says its a Microsoft Networking issue so no help there. The company we worked with to install this has no clue
so I hope to reach out to this community to solve this. I can also open support case with Microsoft Support but I am not sure if they will be of any help. Here are some examples of the errors:
"Event 1000
Faulting application name: SpaWin.exe, version: 3.4.0.0, time stamp: 0x2a425e19
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x0eedfade
Fault offset: 0x0000c42d
Faulting process id: 0x3718
Faulting application start time: 0x01cf9ac7922487e9
Faulting application path: \\spasoft\spaapps\TermServ\SpaWin.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: cfdcf9a9-06ba-11e4-a5af-000c298d9aa5"
Also:
"Faulting application name: VH.EXE, version: 18.80.430.0, time stamp: 0x3f73b447
Faulting module name: VFP8R.DLL, version: 8.0.0.3117, time stamp: 0x3f73c232
Exception code: 0xc0000006
Fault offset: 0x0001d598
Faulting process id: 0x2bc8
Faulting application start time: 0x01cf99297ee1742f
Faulting application path: J:\HOSTPLUS\fxp32\VH.EXE
Faulting module path: J:\HOSTPLUS\fxp32\VFP8R.DLL
Report Id: 5fbc65c4-055c-11e4-a5af-000c298d9aa5"
And:
"Faulting application name: SpaWin.exe, version: 3.4.0.0, time stamp: 0x2a425e19
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x2aa0
Faulting application start time: 0x01cf988e6770e619
Faulting application path: \\spasoft\spaapps\TermServ\SpaWin.exe
Faulting module path: unknown
Report Id: 01029179-04b9-11e4-a5af-000c298d9aa5"
There are no network specific errors in any of the logs. I am thinking that SpaSoft needs to be run as an administrator but I am not sure how to do that in this environment. We have disabled DEP for all but essential Windows processes. All of the firewall
and AV has been completely disabled, and still getting these errors. Is there a way to run these applications as admin without the user actually being an admin? Should I go ahead and open a Microsoft support case? Thanks

Hi,
Thank you for posting in Windows Server Forum.
Explanation
The indicated program stopped unexpectedly. The message contains details on which program and module stopped. A matching event with Event ID 1001 might also appear in the event log. This matching event displays information about the specific error that occurred.
User Action
If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.
Yeah, you can open a support case with Microsoft as they will help and guide you for proper solution. You can go through
this source article.
Hope it helps!
Thanks.
Dharmesh Solanki

Windows 8.1 RDP Issues with Windows Server 2008 Standard.

I have an issue maintaining an RDP connection from 64-bit windows 8.1 (standard and pro) to 32-bit Windows Server 2008 Standard. Initial connection is normal, and as long as I am constantly typing on the link, for the most part it stays up. However
if I do not keep typing, or go to another desktop program for a few minutes, and then go back, the following happens:
If I am typing into notepad (or some screen that does not require windows to be refreshed) I can continue to do so, so the connection has not been lost, however if I try to do something that requires more extensive exchange of information (like file
- open, or even trying to pull up the start menu), the connection pauses with about half the screen refreshed, sometimes after about 30 seconds a bit more of the screen fills out, but otherwise the connection is not responsive. Then after about 2 minutes,
RDP reconnects, at which point I am back to "normal". I have conducted some tests and made inquiries of others attempting to connect to the server.
1) I can connect to other Windows (servers 2008 R2 and 2012) with no connection issues from this PC
2) I can connect to the 32-bit server with no issues using Windows Vista Ultimate and Windows 7 from the same location as the WIndows 8.1 PC
3) When I do a network speed test while having these issues I see full download and upload speeds, so I am not experiencing intermittent internet issues.
4) No-one else from other locations (not of course using Windows 8.1) has any issues using RDP to the 32-bit Windows Server Standard.
These various tests seem to eliminate my network connection, and other operating systems, from the equation, and point to RDP issues on windows 8.1 connecting to the older OS. I noticed in the September updates, a case 2989039 which seemed to point
to similar issues when using UDP through Remote Desktop Gateway. That update is on my machine, and my connection has the setting Automatically detect RD Access Gateway server settings.
Any thoughts anyone?

Hi RonaldRenaud,
If my understanding is right, this RDP issue only occur in the connection between Windows 8.1 and Server 2008.
Please check if you have installed the update kb2984006.
To resolve this issue caused by update 2989039, install update rollup 2984006. For more information, please refer to the following KB.
http://support2.microsoft.com/kb/2989039/en-us
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

Printing problem with Konica Minolta BizHub282 using RDP on Windows Server 2008 R2

Hello,
I have an office setup as follows: Local office IP adress scheme 192.168.201.x. There is a Konica Minolta BizHub 282 printer connected to the 192.168.201.x network as well as around 10 workstations running Windows 7. There are also about
10 additional teleworkers WHO DO NOT NEED print access to the Minolta 282. All of their data is on a cloud server. I have them setup to first connect to the cloud server using a RRAS PPTP VPN and then to start an RDP session to the separate
RDP server. The Konica Minolta works ??okay?? with the easy print services and until now, we have just dealt with the lack of features and the occasional print job that goes crazy and prints out 400 blank pages (btw, this is usually on Excel) or a job
that cuts off the margins even when you have it set to "fit to page" (this usually happens in Adobe.) When I originally set this up, I tried loading the native Konica drivers on the server, but there was no joy because I couldn't get it to
work using the native drivers. The problem at hand is a feature called "account track." This feature authenticates your print job by using an account code. If there is no code, the job just disappears. When I load the native
Konica driver, the ability to turn on this feature is greyed out (see below):
When I use easy print, the codes seem to go through, but as I mentioned earlier, sometimes the print job just goes insane. After researching this, it seems to me that there are two ways to overcome this if we can't turn off the account track feature:
1) Overcome the driver problem. I've tried both of their current drivers without success: VXL and Visual Postscript. When I login to RDP, the (redirected) Konica 282 printer is listed, but when I try to print, it fails due to the missing account track code.
I'm hoping that there is a registry hack to turn this feature on by default with the code or a driver version that works with RDP. They have a WHQL driver available, but it didn't work any better. Is there a way to report this issue to the WHQL labs? Maybe
I can light a fire under Konica's rear end and motivate them to fix the driver.
2) I saw one discussion where the guy installed the printer out in the clouds as a local printer. He seemed to have a site-to-site VPN, not a client-to-site VPN, so this worked. Is there a way to do something similar when the customer connects to the
VPN through standard "connect to workplace" setup? I tried pinging the Konica 282 from the server while logged into the VPN, but the printer could not be found.
3) I considered setting it up as a google cloud print prnter, but that would require everyone to setup a google account and add a layer of complexity.
Anyone else run into this and have a solution? If not, does anyone have any ideas on a solution or workaround?
Thanks,
Jeffery Smith

Hi Jeffery,
Thank you for your comment.
Yeah, you can use universal print driver by configuring Remote Desktop Easy print on RDS Server. Install the driver on RDS server. Now to configure Easy print you need to have minimum client RDP 6.1(But suggest you to install RDP 8.1), .Net Framework 3.5 or
above and RDSH role.
Also under GPO setting need to check below settings.
Do not allow client print redirection: Disable
Use Terminal Service Easy print printer driver first: Enable
Computer Configuration > Administrative templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Printer redirection
For more information, you can refer below articles.
How to configure Microsoft RDS Universal Printing
http://www.virtualizationadmin.com/articles-tutorials/vdi-articles/microsoft-hyper-v/how-configure-microsoft-rds-universal-printing.html
Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2
http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx?Redirected=true
Hope it helps!
Thanks.
Dharmesh Solanki

Can't RDP From Windows 7 to Server 2008 R2 SP1

Hello,
We have a server 2008 R2 SP1 with all the latest updates installed as of today (11/12/2014) that runs terminal services.
We started upgrading our office computers to windows 7 x64 and now unable to RDP into the server. They were able to RDP for a few days and now are unable.
Once you hit connect, it asks for a username & password, and then it says configuring remote connection and after about 15-30 seconds it just says can not connect to remote computer.
I am able to RDP from windows 7 into 2003 servers.
Windows XP Computers can RDP just fine.
I went through all the articles that had the updates that needed to be removed/reinstalled for RDP to work and none of them fixed the issue.
This has been going on since Monday 11/10/2014
Any advice or assistance is greatly appreciated.

SP1 Is installed. as well as updated as of 11/12/2104
Here is the only thing that shows up in the logs on the server side:
Attempt to send connect message to Windows video subsystem failed. The relevant status code was 0xd0000001.
System
Provider
[ Name]
Microsoft-Windows-TerminalServices-LocalSessionManager
[ Guid]
{5D896912-022D-40AA-A3A8-4FA5515C76D7}
EventID
20
Version
0
Level
2
Task
0
Opcode
0
Keywords
0x1000000000000000
TimeCreated
[ SystemTime]
2014-11-12T23:47:45.532187000Z
EventRecordID
19249
Correlation
Execution
[ ProcessID]
644
[ ThreadID]
1624
Channel
Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Computer
LAXCA-PD-TS01.XXXXXXXXXXXXXXX.local
Security
[ UserID]
S-1-5-18
UserData
EventXML
messageName
connect
errorCode
0xd0000001

Server 2008 R2 RDP: limit max number of rdp connections per user group?

Hello everyone,
I have a Windows Server 2008 R2 with RDP installed.
I want to create a couple of user groups which will have 5 different users in each. Then I would like to limit RDP connections, let's say 2 connections for the first group and 3 connections for the second group. For example, if 2 users from Group 1 are connected
then when a 3rd user from Group 1 tries to connect it will be rejected to connect, but 3 users from Group 2 still can connect. Is it doable?
Thanks in advance.

Hi,
I would like to check if you need further assistance.
If you need help to create script, please post your questions in our related forums.
http://social.technet.microsoft.com/Forums/scriptcenter/en-US/home
Thanks.
Jeremy Wu
TechNet Community Support

RDP Port not Listen in Windows Server 2008 Std With Sp2

Hi all
I have Windows 2008 Server Std with SP2 Domain Member Server.. From Last week On-wards , am not able to take remote desktop control .. But i can able to Ping my Server from network .. I check remote settings on that server.. It
is enabled.. and also remote desktop service(Terminal service) was started successfully.. I checked my network firewall for port(3389) blocking.. But there is no much block in my network firewall.. i also disabled windows firewall in my server.. But
still i couldn't able to take RDP.. I also checked my Domain GPO and Local GPO settings for RDP Block.. But there is no such settings enabled. I did following Troubleshooting Steps, but still the problem persist
1. Telnet serverip 3389
Result : Could not open connection to the host, on port 3389:
2. netstat -n -a -o | find "3389" (i run this command in my RDP Problem server)
Result : nothing displayed (3389 port not listed )
3. i again & again restarted Terminal service and the server, but still problem exists
4.i changed the RDP port no and restarted the service as well as the server , but still problem exist
5. I checked all RDP related Registry settings , everything is perfect
Please help me to solve this issue
I need your valuable reply urgently
Thanks in advance

Hi Mohamed,
You mention, that you the server is not listening to port 3389 when you run netstat. This is the reason why telnet and RDP connectivity fails in a first place. You also said that you changed the RDP port number. What was is before the change, and to what
did you change it to?
Please verify if the Terminal Service is listening to 3389 (0xd3d) with following command:
reg query "HKLM\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v PortNumber
Output:
PortNumber REG_DWORD 0xd3d
Try to enable the Operational log for TerminalServices-RemoteConnectionManager events in Event Viewer:
Open Event Viewer
Navigate to Applications and Service Logs\Microsoft\Windows\TerminalServices-RemoteConnectionManager
Select the Operational log and chose Enable Log
from the Action or context menu
Restart Terminal Services service
Then consult this event log and the System and Application logs for any related errors and warning. It might be helpful to post relevant event log entries here.
Additional information and solutions about Terminal Server Listener events and errors can be found here:
http://technet.microsoft.com/en-us/library/cc727385(v=ws.10).aspx
Regards,
Johann
// Johann

Windows Server 2008 R2 SP1 RDS hang and stop responding new rdp session. Already connected session also hang as well

We have a Windows Server 2008 R2 SP1 RDS supporting many ThinClients, mostly using a mandatory profile on a Windows 2003 R2 AD environment
at the moment of the hang what we experienced was:
New RDP sessions got stucked in the legend "Iniciando" (we have the spanish MUI).
Systems Events shows a lot of Warnings:
The Group Policy Client Side Extension Group Policy Shortcuts may have caused the Group Policy Service to terminate unexpectedly. To prevent further failures in the Group Policy
Service, this extension has been temporarily disabled until after the next system restart. Group Policy settings managed by this extension may no longer be enforced until the system is restarted. The vendor of this extension should be contacted if this issue
recurs.
and after that a lot of this errors:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the gpsvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SessionEnv service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CertPropSvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the IKEEXT service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SessionEnv service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service.
During the problem we ping DC and Network Share where Profile and Document Redirection resides and they were working OK (we also did a
\\server\HomeUsers and we reached it without problem)
Only reseting the server worked, Any Ideas of what could be causing this ?? Best Regards
Federico Giampietri Latamsupport IT Infrastructure Services

Hi Clarence,
Today we experienced the problem again,
Users can’t login to RDS, but now they got stucked at “"Please wait for the Group Policy client”;
System log events recorded the following errors again:
timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the sessionenv service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the Wuauserv service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the CertPropSvc service.
What path do you suggest to investigate further?
Thanks a lot!
Federico Giampietri Latamsupport IT Infrastructure Services

Windows Server 2008 R2 SP1 freezes and cannot access RDP

The system freezes every 15 minutes after a reboot. I am trying to capture some stats using procmon to see what is going on, but while I am working on it, it freezes so I cannot even save the file. Next, RDP does not work even when the system is up for that
15 minutes. Any idea what is going on? This behavior is only on this server. The last patch that this system should have is October. We are patching the November one's now.
Any thoughts or suggestions?
thanks in advance
AA2913

Hi,
Thank you for posting in Windows Server Forum.
Is there update for your case with Dave comment? Have you seen which process is making the server hang?
Please see below Hotfix if it’s applicable for your case.
A computer that is running Windows Server 2008 R2 or Windows 7 stops responding randomly
http://support.microsoft.com/kb/2265716/
Also you can go through this article for server hang case.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Slow RDP (refresh rate) to Server 2008 R2 from Windows 8.1

Hi everyone,I have a user connecting to a Server 2008 R2 RDP server. He can connect no problem, but there is quite a bit of latency which I do not understand. He pings to the server at around ~60ms. I have another server on the same site (Server 2012 R2) and he does not experience the same latency. I've connected another Windows 8.1 computer to the Server 2008 R2 box and CANNOT replicate the issue.He appears to be the only one.I've temporarily disabled his AV, windows firewall, disabled local visualization settings (and on the server). I've configured RDP to 56k settings in the Experience tab which changed absolutely nothing.I've also run the netsh commands everyone seems to suggest with this issue.Any recommendations or things to try?EDIT: I've also updated his wireless drivers. I don't have the laptop in hand to try the local...
This topic first appeared in the Spiceworks Community

I need to upgrade the database size to >=100 GB to restore a database. I tried all described instructions including Hotfixes and possible upgrade to Enterprise or Standard EditionBhoomin Pandya
So what advise do you need. Did you tried upgrading first ? Did you faced any error
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

RDP Printing on Server 2008 /R2

Hi, I have a server with windows 2008 r2 and clients running rdp 6.0 on windows 7, the problem is that the clients send to print to the server printer but nothing happens, I made a rdp installer and after this they can log on but not
print, before this rdp installer the printing was ok, they had a mstsc shortcut with printers enabled but now with the installer icon this option is not present.
thanks in advace

Hi,
Initially please try to use latest version of RDP client v8.1. After that also try to apply RD Easy Print service and see whether it can make any difference.
Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2
http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

RDP audio issues with Windows Server 2008

I have a server with an M-Audio 1010LT audio card installed, running audio playback software. This software needs to stay running and playing at all times.
We were previously running Windows Server 2003 and when we RDPed into the box for maintenance, we simply made sure that 'Leave at remote computer" was selected under Remote Desktop's sound settings. This allowed us to control the console of the server while the audio continued to play through the server's audio card.
Now, with Windows Server 2008, even with this option selected when we remote into this server all audio stops and Windows shows no available audio devices. If I end my RDP session and phyically go to the server, I see the audio devices and am able to re-start the audio playback.
Is this a bug, or something that has changed in 2008? Any workarounds?
Thanks

*****************I
AM HAVING THIS ISSUE *****************
(Windows Server 2008 R2)
I
reply to this thread to hopefully get more attention to this issue and thus a [faster] resolution.

Problems with RDP/RDC from Mac OSX to Windows Server 2008 on External IP

We have a customer that is using Mac and Microsoft's RDC for Mac to their servers.
They've just upgraded from Windows Server 2003 to 2008 and can't connect through RDP to their TS server on external IP.
Their servers is not in any domain and it work for them to connect to another Windows Server 2008 that is located in their office when they use internal IP.
The problem is that when using RDC to the external IP they get bellow:
"Remote Desktop cannot verify the identity of the computer you want to connect to. This problem can occur if:
The remote computer is running a version of Windows that is earlier than Windows Vista.
The remote computer is configured to support only the RDP security layer.
Contact your network administrator or the owner of the remote computer for assistance."
From here they can choose "Connect" as they did on the Server 2003 but now they get: "Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.Try reconnecting to the Windows-based computer, or contact our administrator."
and is only able to choose "Ok".
I've changed the settings on the "configuration for host server for remote desktop sessions" under General from "RDP-Security Layer" to "Negotiate" and in this case I get a logon windows where i type in all my information click logon. Here I get another
error message which says something like: (We get it in Swedish). "Connection to the windows-based computer broke since there was a problem associated with the licensificationprotocol... Try to connect again" Where I can choose "Cansel" or "reconect"
but it just keeps poping up if i chose reconnect.
I've tried all settings in the TS server and there is not much to change on the RDP client. We have installed the server certificate on the Mac client but it didn't help.
We've also tried with CoRD and it works fine as RDP from a normal Windows based computer.
The only solution I've found on google is to use CoRD instead but we got problems with that connection since it keep crasching on our computer.
In my eyes the problem is on the security requirements that the RDC for Mac needs but I can't find any inforamtion on MS sites about it.
Greatfull for all tips and trix!

I too was having the problem same as everyone else. However, for me the problem all started when I replaced my SSL certificate that was used/selected in the Remote Desktop Session Host Configuration utility, connections, RDP-TCP Properties. The security
layer is negotiate and the certificate is the one selected on that screen. It was not licensing related.
The certificate had expired and I didn't believe I needed it. But turns out I did, so I had to generate and validate a new one using GoDaddy (though they specifically were not part of the problem). As my Terminal Servers (Remote desktop servers)
do not have IIS installed, I was a bit stumped on how to create a new certificate request. I finally found some instructions on how to create a certificate request using the MMC snap-in, advanced operations, create custom request. The template
chosen was "legacy key", and without boring the rest of the details that part was the root cause of my problem. The legacy key was not able to be processed correctly by the Mac RDC client. Neither the official 2.1.1 client or the 2.1.2 download.
The Terminal Server system event log was showing the following two errors, 36874 and 36888. The first one contained the best details and said: "An TLS 1.0 connection request was received from a remote client application, but none of the cipher suites
supported by the client application are supported by the server. The SSL connection request has failed." Upon searching the internet for that, I found this page which described the legacy key problem:
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/3a2d2eec-000d-432a-abd7-6b965268c671
So, my solution most familiar to me was to use IIS and create the SSL certificate request, process that with my 3rd party CA, export the certificate with private key and then import that certificate into all of my terminal servers. Then using the session
host configuration tool, pick the new certificate and the problem was now solved.

Installing RDP 8.1 on Server 2008

I've installed the prerequisite and update for RDP 8 on a Server 2008 R2 virtual server. When I look at the About information "Remote Desktop Protocol 8.0 supported". However, the gpedit option isn't there under:
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
What else needs installed?
Thanks!

Hi,
It is in both the KB article as well as the blog, but it is not as clear as it could be. Excerpts:
KB 2592687, one example:
From the Enable the update on the client section, "To enable RDP 8.0 on a remote computer that's running Windows 7 SP1, follow these steps: Note The following instructions are applicable only to remote computers that are running Windows
7 SP1."
From the blog article:
"Are the RemoteFX and RDP 8.0 enhancements available for Windows Server 2008 R2 Remote Desktop Session Host?
No, the RemoteFX and RDP 8.0 enhancements are not available for Windows Server 2008 R2 Session Host. However, a Windows Server 2008 R2 computer acting as a client access device will still get the Remote Desktop Connection 8.0 client and thereby get
the benefits listed in the ‘client access devices’ section earlier."
-TP

RDP to Server 2008

Similar Messages

Maybe you are looking for