WIN remote desktop connection

i am a new mac user need to download and install remote desktop connection for mac have tried several times after download all i have is a excel doc.
i need it to work with Terminal Server 2003
mac bookpro Mac OS X (10.4.8)

You need to install Stuffit Expander, available free from Stuffit.com to open the download.

Similar Messages

Problem Establishing Remote Desktop Connection from Win 7 64Bit

I just got a new Lenovo laptop running Windows 7 Pro 64 Bit with Service Pack 1. I have installed all Win 7 Updates.
When I try to connect to other Windows 7 Ultimate (32 bit) desktops through Remote Desktop Connection over my LAN, I get the following error:
"An authentication error has occurred. The requested security package does not exist"
I can connect to a Windows Small Business Server 2003 32 bit server from the laptop without problem.
All machines are members of the same Windows domain.
The Windows 7 machines I am trying to connect to can connect to each other without issue. NLA is set as not required on each of the desktops, though I have tried turning the NLA setting on, and received the same error.
I have even tried running the 32 bit version of mstsc.exe and disabling the 64 bit version as discussed here:
http://www.davidmoore.info/2009/12/02/running-32-bit-remote-desktop-connection-on-windows-64-bit/
This had no effect either.

Hi,
Based on my research, please check whether the value of HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Security Packages is
kerberos
msv1_0
schannel
wdigest
tspkg
pku2u
If not, please correct it and see how it works.
Note: Serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For
more information about how to back up and restore the registry, please refer to
How to back up and restore the registry in Windows.
Hope this helps.
Jeremy Wu
TechNet Community Support

Remote Desktop Connection certification issue with Win Server 2008 R2

When connecting to Windows 2008 server R2, from Windows 7, Vista and Mac OS 10.6.7 via Remote Desktop Connection, i am getting a 'Server Name on the Certificate is Incorrect' error.
if i click connect, i can still connect to the machine, due to a 3rd party managing the server, this doesn't look very professional on my part...
The server is a standalone machine and is not currently on a domain. RDC is only used for management purposes.

Hi,
This certificate error is normal, because your client do not trust the certificate which is installed on the terminal server. To avoid this issue,
you can export the certificate and import this certificate into the client side (computer account).
Thanks.

L7580 net printer driver disappearing in Win 7-62 after connecting with Remote Desktop Connection

I have an Officejet Pro L7580 connected via ethernet. I've been using the driver released from Jan 2010, and whenever I connect to my Windows 7 Ultimate 64 computer via Remote Desktop Connection, the printer drivers for both the printer and the fax disappear. I have to constantly run the "add a device" window to add the printers back again.
Why do they disappear like that?
Fishanderson

OK after updating the Server and clients I am still having this issue :(
and just today after no sound problems for 6 days the sound dropped out on a couple of RDP sessions, yet the sound on the client itself worked fine when tested (minimise the RDP session).
It took the RDP sessions to be restarted to restore the sound within the session.
I have found similar (old) thread regarding this problem:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/958fd891-6f55-432b-8268-a326ac6b2b2e/sound-in-remote-desktop-session-stops-working
but no one has informed about if as solution was ever found.

Remote Desktop Connection - Authentication error

Hello,
I wish to connect to my work PC from my laptop. The remote desktop connection was working fine till yesterday, but today i receive the following error when i try to connect -
"An authentication error has occurred. The Local Security Authority cannot be contacted. Remote Computer: <name>."
I have Win 7 ultimate installed on my 32 bit system, and have tried solutions proposed in the other threads. I do not require a NLA check for connection, i have always used the remote desktop with this option unchecked. Could anyone help me with this please?
Is this a error on my Laptop, or do i need to contact the network administrators for this?

Hi!
It could be as easy as you need to change your password on your domain accout.
Are both computers connected to the same domian or is your work computer connected to a domain and your laptop connected to a workgroup?
If your password has expired, this error can occur, so I would start to check that since it stoped working over night.
Best regards
Andreas Molin

Remote Desktop Connection has stopped working

Using Build 10041. Occurs on 2 separate systems I have when trying to use Remote Desktop Connection through a 2012 R2 RDS Gateway. I am able to connect to the remote systems and access the environment for a short period prior to MSTSC.EXE
crashing. "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
Eventlog has the following:
Log Name:      Application
Source:        Application Error
Date:          3/25/2015 2:50:21 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Description:
Faulting application name: mstsc.exe, version: 10.0.10041.0, time stamp: 0x5503b1a7
Faulting module name: mstscax.dll, version: 10.0.10041.0, time stamp: 0x5503b315
Exception code: 0xc0000005
Fault offset: 0x000000000046d78c
Faulting process id: 0x2164
Faulting application start time: 0x01d06734abf028a0
Faulting application path: C:\WINDOWS\system32\mstsc.exe
Faulting module path: C:\WINDOWS\system32\mstscax.dll
Report Id: 2b084e37-d328-11e4-ab40-7c7a9191e005
Faulting package full name:
Faulting package-relative application ID:
JW

Tried this with no luck. I have the same issue as the OP. It was failing on 10041 and is still failing with an AV on 10049. See below event log entry after registering mstscax.dll and rebooting. Still failing.
Log Name:      Application
Source:        Application Error
Date:          4/11/2015 12:18:21
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Chuck1
Description:
Faulting application name: mstsc.exe, version: 10.0.10049.0, time stamp: 0x55137bff
Faulting module name: mstscax.dll, version: 10.0.10049.0, time stamp: 0x55137d3f
Exception code: 0xc0000005
Fault offset: 0x000000000046d74c
Faulting process id: 0x1870
Faulting application start time: 0x01d0748c29e55e06
Faulting application path: C:\WINDOWS\system32\mstsc.exe
Faulting module path: C:\WINDOWS\system32\mstscax.dll
Report Id: 83921b7c-e07f-11e4-960f-40f02f7ad3a4
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-11T19:18:21.000000000Z" />
    <EventRecordID>73626</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Chuck1</Computer>
    <Security />
</System>
<EventData>
    <Data>mstsc.exe</Data>
    <Data>10.0.10049.0</Data>
    <Data>55137bff</Data>
    <Data>mstscax.dll</Data>
    <Data>10.0.10049.0</Data>
    <Data>55137d3f</Data>
    <Data>c0000005</Data>
    <Data>000000000046d74c</Data>
    <Data>1870</Data>
    <Data>01d0748c29e55e06</Data>
    <Data>C:\WINDOWS\system32\mstsc.exe</Data>
    <Data>C:\WINDOWS\system32\mstscax.dll</Data>
    <Data>83921b7c-e07f-11e4-960f-40f02f7ad3a4</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>

Remote Desktop Connection With Custom Certificate on Windows 8.1 fails

I'm trying to establish a secured remote desktop connection without success.
The setting
There are some local pcs with windows 8.1 Pro and windows 7 Pro, no server-edition. I've created a self signed ca-certificate with openssl for Windows. I used this to sign custom certs for the local windows-pcs, which are installed at mmc -> certificate
snap-in for local computer -> My Certificates -> Certificates. The networkdriver has the right to read the key. The sha1-fingerprint of the custom signed certs are registered at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
-> SSLCertificateSHA1Hash = sha-1 hash of the custom local cert. Additionally the revocation-list is restrained to the local list by setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp -> UseCachedCRLOnlyAndIgnoreRevocationUnknownErrors
= 1.
The results
The connection form win 8.1 to win 7 works. The connection info confirms that it is a veryfied connection. The connection to windows 8.1 fails after entering the credentials with error: No connection possible. Network Level Authentication is set, but other
level don't work as well. The log (Event Views -> Applications and Services Logs -> Microsoft -> Windows -> TerminalServices-RemoteConnectionManager -> Admin) says "Remote Desktop Services has taken too long to load the user configuration
from server" and "The Local Security Authority Cannot Be Contacted" (error 0x80090304)
Aditional information
The connection via linux (remmina) works for win 7 and win 8.1, but I have no information about the encryption. It is the same with the Microsoft Remote Desktop Tool for Android.
Maybe it is accociatet with a different cert handling by Windows 8.1 but I couldn't find further information or a solution in the internet.
Best regards
abditus

I solved the problem!
The default openssl certificate signature algorithm is md5RSA but it doesn't work with windows 8.1.
It is at least sha1RSA needed.
By adding "default_md = sha1" to the openssl.cnf you create certs with sha1RSA and it works fine.
Beste Gegards
abditus

Remote desktop connection in windows 7 pro

I have a problem accessing remote desktop connection using windows 7 64 bit.
My remote desktop connection shell version 6.3.9600 shows the Network Level Authentication is not supported.
My other computer also win 7 pro 64 bit has a different shell version 6.2.9200 that supports Network Level Authentication.
How do I go backwards to shell 6.2.9200?
I have been trying use remote desktop using the more robust security and could not figure out why I could not log.
I have screen shots of the two shells and my system screens

Hi,
Configure Network Level Authentication
Click Start, click Run, type regedit, and then press ENTER.
In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
In the details pane, right-click Security Packages, and then click Modify.
In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
In the details pane, right-click SecurityProviders, and then click Modify.
In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.
Exit Registry Editor.
Restart the computer.
Hope this helps!
Andy Altmann
TechNet Community Support

Remote Desktop Connection no longer works.

After verifying that all Remote Desktop Connection settings and firewall settings match the requirements, I cannot connect to the host computer running Windows 8.1 Pro with Media Center from a client computer running Windows 7 Home Premium SP1 over my
home (private) network. I was previously able to connect these same two computers when the host computer was running Windows XP Pro, but now that I have upgraded its operating system to Win 8.1 Pro the connection no longer works. The Windows Troubleshooter
cannot find the problem. What is wrong?

If you turn off a firewall in a router it is still using NAT which will also act like a firewall. In my experience its better to let your router be the firewall.
On most routers that have an SPI firewall you have to setup 2 rules to allow remote connections. One would be the firewall rule and other would be the port forwarding(NAT) rule.
Are you forwarding the correct ports to your mac from the router? Does your Mac have a fixed IP address?

Remote Desktop Connection ok on work wireless but not from home

I've succesfully logged into the Win 2003 SBS (Terminal Services) from within the wireless connection at work using Mircrosoft's "Remote Desktop Connection". However when I try to do this from home I get the following error message "Either remote connections are not enabled, the computer is too busy to accept new connections, or network problems are preventing your connection. Try connecting again later or contact your administrator."
I've got the firewall on the mac on.
Now what I can't work out is why it works when at work and not from home. I have been searching for ages and can't work this out - annoying as I am sure it is very simple!
One thing I can think of is that the first time others connect via PCs they have to download the connection manager from the company web site which installs a security certificate. However this is an .exe file so cannae work on the Mac.
Do all I need to do is ask the IT administrator to email me the certificate and drop it into the keychain?
Thanks in advance.

"Now what I can't work out is why it works when at work and not from home."
Probably because, if your work is smart, they have a firewall in place, blocking external access to the ports needed for use with RDC.

Remote Desktop Connection Stopped Working when Disconnecting

Hi I have a fresh clean install of Windows 8.1. Whenever I RDP into another Windows 8 machine... upong disconnecting I get the error: "Remote Desktop Connection Stopped Working"
I have tried not mapping to remote printers, or drives (smart cards etc.) and it still persists. When I remote to Windows Server or Win 7, it does not happen.
Anyone have any ideas?
Thank you
mi

FYI, same issue here, Windows 8.1 on ThinkPad W520 (upgraded from Windows 8).
Even without Fingerprint Manager, and having uninstalled ThinkVantage Password Manager as well, still crashes. I also tried the:
Dism /Online /Cleanup-Image /RestoreHealth
but no luck, my mstsc.exe is still crashing when the remote session window is closed.
Any ideas? Happy to upload/provide more details, here's the Report.wer contents from
C:\Users\myusername\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_mstsc.exe_fe9be6b453d387663f457b9f305ac5e3ae6f5fc2_00000000_2fb47393\Report.wer
Version=1
EventType=CLR20r3
EventTime=130332895175356766
ReportType=2
Consent=1
UploadTime=130332895176424161
ReportIdentifier=1d23a02d-7507-11e3-81f8-f0def1f95c65
Response.BucketId=c93f173301a697688e31de36235ffda6
Response.BucketTable=5
Response.LegacyBucketId=-439202015
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=mstsc.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=6.3.9600.16384
Sig[2].Name=Problem Signature 03
Sig[2].Value=5215e2b5
Sig[3].Name=Problem Signature 04
Sig[3].Value=WHSOLConnector
Sig[4].Name=Problem Signature 05
Sig[4].Value=2.5.7.7
Sig[5].Name=Problem Signature 06
Sig[5].Value=4beac4d4
Sig[6].Name=Problem Signature 07
Sig[6].Value=70
Sig[7].Name=Problem Signature 08
Sig[7].Value=71
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.NullReferenceException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\WINDOWS\system32\mstsc.exe
UI[3]=Remote Desktop Connection has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\WINDOWS\system32\mstsc.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\system32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\system32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\system32\ADVAPI32.dll
LoadedModule[5]=C:\WINDOWS\system32\GDI32.dll
LoadedModule[6]=C:\WINDOWS\system32\USER32.dll
LoadedModule[7]=C:\WINDOWS\system32\msvcrt.dll
LoadedModule[8]=C:\WINDOWS\system32\ole32.dll
LoadedModule[9]=C:\WINDOWS\system32\OLEAUT32.dll
LoadedModule[10]=C:\WINDOWS\system32\SHELL32.dll
LoadedModule[11]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.16384_none_62475f7becb72503\COMCTL32.dll
LoadedModule[12]=C:\WINDOWS\system32\COMDLG32.dll
LoadedModule[13]=C:\WINDOWS\system32\SHLWAPI.dll
LoadedModule[14]=C:\WINDOWS\system32\CRYPT32.dll
LoadedModule[15]=C:\WINDOWS\system32\WINHTTP.dll
LoadedModule[16]=C:\WINDOWS\system32\credui.dll
LoadedModule[17]=C:\WINDOWS\system32\Secur32.dll
LoadedModule[18]=C:\WINDOWS\system32\CRYPTUI.dll
LoadedModule[19]=C:\WINDOWS\system32\CFGMGR32.dll
LoadedModule[20]=C:\WINDOWS\system32\WS2_32.dll
LoadedModule[21]=C:\WINDOWS\system32\NETAPI32.dll
LoadedModule[22]=C:\WINDOWS\system32\RPCRT4.dll
LoadedModule[23]=C:\WINDOWS\system32\WINMM.dll
LoadedModule[24]=C:\WINDOWS\system32\IPHLPAPI.DLL
LoadedModule[25]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[27]=C:\WINDOWS\system32\MSASN1.dll
LoadedModule[28]=C:\WINDOWS\system32\NSI.dll
LoadedModule[29]=C:\WINDOWS\system32\netutils.dll
LoadedModule[30]=C:\WINDOWS\system32\srvcli.dll
LoadedModule[31]=C:\WINDOWS\system32\wkscli.dll
LoadedModule[32]=C:\WINDOWS\system32\WINMMBASE.dll
LoadedModule[33]=C:\WINDOWS\system32\WINNSI.DLL
LoadedModule[34]=C:\WINDOWS\system32\SHCORE.DLL
LoadedModule[35]=C:\WINDOWS\system32\DEVOBJ.dll
LoadedModule[36]=C:\WINDOWS\system32\SSPICLI.DLL
LoadedModule[37]=C:\WINDOWS\system32\IMM32.DLL
LoadedModule[38]=C:\WINDOWS\system32\MSCTF.dll
LoadedModule[39]=C:\Windows\system32\nvinitx.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[41]=C:\WINDOWS\system32\CRYPTBASE.dll
LoadedModule[42]=C:\WINDOWS\system32\bcryptPrimitives.dll
LoadedModule[43]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[44]=C:\WINDOWS\system32\credssp.dll
LoadedModule[45]=C:\WINDOWS\system32\NTASN1.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\clbcatq.dll
LoadedModule[47]=C:\WINDOWS\system32\PROPSYS.dll
LoadedModule[48]=C:\WINDOWS\system32\dwmapi.dll
LoadedModule[49]=C:\WINDOWS\system32\mstscax.dll
LoadedModule[50]=C:\WINDOWS\system32\PSAPI.DLL
LoadedModule[51]=C:\WINDOWS\system32\d2d1.dll
LoadedModule[52]=C:\WINDOWS\system32\d3d11.dll
LoadedModule[53]=C:\WINDOWS\system32\MSACM32.dll
LoadedModule[54]=C:\WINDOWS\system32\VERSION.dll
LoadedModule[55]=C:\WINDOWS\system32\SETUPAPI.dll
LoadedModule[56]=C:\WINDOWS\system32\DWrite.dll
LoadedModule[57]=C:\WINDOWS\system32\bcrypt.dll
LoadedModule[58]=C:\WINDOWS\system32\ncrypt.dll
LoadedModule[59]=C:\WINDOWS\system32\pdh.dll
LoadedModule[60]=C:\WINDOWS\system32\dxgi.dll
LoadedModule[61]=C:\WINDOWS\system32\explorerframe.dll
LoadedModule[62]=C:\WINDOWS\system32\DUser.dll
LoadedModule[63]=C:\WINDOWS\system32\DUI70.dll
LoadedModule[64]=C:\WINDOWS\system32\WINTRUST.dll
LoadedModule[65]=C:\Windows\system32\WHSOLConnector.dll
LoadedModule[66]=C:\WINDOWS\system32\mscoree.dll
LoadedModule[67]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[68]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
LoadedModule[69]=C:\WINDOWS\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_88dcdb0b2fb19957\MSVCR80.dll
LoadedModule[70]=C:\WINDOWS\system32\profapi.dll
LoadedModule[71]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\mscorlib\97d2eb053ee241db571311577790ae43\mscorlib.ni.dll
LoadedModule[72]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
LoadedModule[73]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System\8b12c5fec7e8912da325ee73b380e652\System.ni.dll
LoadedModule[74]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System.Drawing\3eac16e6688dfec78565e3e71a26266f\System.Drawing.ni.dll
LoadedModule[75]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System.Windows.Forms\d78d7a76a56319e4bc1cbffa3a90a0e1\System.Windows.Forms.ni.dll
LoadedModule[76]=C:\WINDOWS\System32\Essentials\VCListener.dll
LoadedModule[77]=C:\WINDOWS\system32\MF.dll
LoadedModule[78]=C:\WINDOWS\system32\MFCORE.DLL
LoadedModule[79]=C:\WINDOWS\system32\ksuser.dll
LoadedModule[80]=C:\WINDOWS\system32\MFPlat.dll
LoadedModule[81]=C:\WINDOWS\system32\RTWorkQ.DLL
LoadedModule[82]=C:\WINDOWS\system32\AVRT.dll
LoadedModule[83]=C:\Windows\System32\MSAudDecMFT.dll
LoadedModule[84]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[85]=C:\WINDOWS\System32\perfos.dll
LoadedModule[86]=C:\Windows\System32\msxml6.dll
LoadedModule[87]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[88]=C:\Windows\System32\rasadhlp.dll
LoadedModule[89]=C:\WINDOWS\system32\WTSAPI32.dll
LoadedModule[90]=C:\WINDOWS\system32\WINSTA.dll
LoadedModule[91]=C:\WINDOWS\system32\mswsock.dll
LoadedModule[92]=C:\WINDOWS\system32\DNSAPI.dll
LoadedModule[93]=C:\Program Files\Bonjour\mdnsNSP.dll
LoadedModule[94]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[95]=C:\WINDOWS\system32\DPAPI.DLL
LoadedModule[96]=C:\WINDOWS\system32\CRYPTSP.dll
LoadedModule[97]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[98]=C:\WINDOWS\system32\schannel.DLL
LoadedModule[99]=C:\WINDOWS\system32\tspkg.DLL
LoadedModule[100]=C:\WINDOWS\system32\ncryptsslp.dll
LoadedModule[101]=C:\WINDOWS\SYSTEM32\gpapi.dll
LoadedModule[102]=C:\WINDOWS\system32\wdmaud.drv
LoadedModule[103]=C:\WINDOWS\system32\AUDIOSES.DLL
LoadedModule[104]=C:\WINDOWS\SYSTEM32\powrprof.dll
LoadedModule[105]=C:\WINDOWS\system32\msacm32.drv
LoadedModule[106]=C:\WINDOWS\system32\midimap.dll
LoadedModule[107]=C:\Windows\System32\msmpeg2vdec.dll
LoadedModule[108]=C:\WINDOWS\System32\msvproc.dll
LoadedModule[109]=C:\WINDOWS\system32\LINKINFO.dll
LoadedModule[110]=C:\WINDOWS\system32\ntshrui.dll
LoadedModule[111]=C:\WINDOWS\system32\cscapi.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Remote Desktop Connection
AppPath=C:\Windows\System32\mstsc.exe
ReportDescription=Stopped working
ApplicationIdentity=00000000000000000000000000000000

UAG SP4 and Windows 8.1 Remote Desktop Connection 8.1

Hello,
I found on the description of SP4 for UAG the following: "Remote Desktop: Forefront UAG SP4 supports the Remote Desktop Connection (RDC) 8.1 client." Does that apply to the publication of servers using "TS Client Tunneling
(Windows Vista/Windows XP)"?
When I use my Windows 8.1 32bit client to connect to the portal, I can see the published application, click on the icon that is on the portal and it start the SSL Application Tunneling and the SSL icon appears at the Taskbar. Then it opens the "Remote
Desktop Connection" client. However when I type the name or IP of the machine to what I want to connect, it fails. Is something wrong? Or this is not working on Windows 8.1? My windows 7 cliesnt have no problem to connect using this application.
Thank you!

Hi Rob,
Let's confirm some situation:
Did you mean connect to Windows 7 from Windows 8.1 computer?
Did you mean the printer connect to another Windows 8 computer at home, and shared to that Windows 8.1 or the printer connect to that Windows 8.1 directly?
Firstly double check your settings:
1. Launch Remote Desktop Connection.
2. Click Options, and then click the Local Resources
tab.
3. Under Local devices and resources, select the Printers check box.
After that make sure that the proper printer driver version is installed on the remote computer.
Meanwhile, refer to this thread to check the port:
http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/win-7-remote-desktop-and-local-printing-not/544acb1b-a259-4170-bc05-2c6dbfd0ca05
Karen Hu
TechNet Community Support

Remote Desktop Connection Manager can only open 6 sessions at a time on Server 2012

I am only able to open, and view thumbnails, for a maximum of 6 RDP sessions on my Server 2012 box at a time in Remote Desktop Connection Manager (RDCM). If I add more sessions I just get a variety of connection errors for the additional sessions. If I activate
a 7th session one of the existing 6 sessions goes off-line with a connection error message. Sometimes the error says 3334, sometimes the error says 0x8345000E, and sometimes it just says there is a connection error.
I have checked Group Policy on the server to ensure I don't have any settings restricting the number of RDP sessions.
In fact, I will often have 30 or 40 RDP simultaneous sessions opened, I am just not able to view them all in RDCM. I have seen reviews of RDCM with screenshots showing dozens of thumbnails so it seems to be something that's possible to do.
Are there any settings I should make on the server to allow RDCM to connect to more than 6 simultaneous RDP sessions?
Just to be clear, all these RDP sessions are running on the same server. Also, I am just using the trial license for Server 2012 and Remote Desktop Services right now. I don't think that should have an impact, but I wanted to be thorough.

Thanks Jakub for "corflags" info.
Unfortunatelly it doesn't work because running mRemoteNG.exe process in 64bit can't load MSTSC ActiveX component (referenced assemblies) because original files were assembled from 32bit dll [mstscax.dll]?
Error message when making RDP connection:
Could not load file or assembly 'Interop.MSTSCLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
I was able to create new AxInterop.MSTSCLib.dll and Interop.MSTSCLib.dll assemblies from 64bit dll version and now it works with "AnyCPU":-)
http://www.filedropper.com/axinteropmstsclib-mremoteng
Using AxImp.exe and TlbImp.exe didn't worked for me because it creates assemblies in wrong namespace "MSTSCLib" instead of "Interop.MSTSCLib" (AxImp.exe) and TlbImp.exe for changing namespace generated many "marshaled errors"
so final .dll wasn't working.
Adding MSTSCAX.dll reference in Visual Studio directly created correct and functional assemblies. Who don't know how to create 64bit compatible assemblies or don't have Visual Studio, feel free to check linked file.
Hope it helps
P.S. Sorry for possible technical misinterpretation, I am not programmer so creating new assemblies was trial-error process...

Using a remote desktop connection with the Macbook pro.

I use the remote desktop connection on the Macbook pro and am unable to exchange info between the mac and the remote connetion windows. For example, if I am writing an email from the remote connection and want to attach a document, photo etc. that I created on the Mac, it just doesn't work. It seems like the Mac and the desktop connection are completely seperated eventhough they are both on the screen in front of me. the systems I use for work are not Apple compatible and will not work on anything other than windows explorer and in my case the remote desk top connection. Any ideas!

Welcome to Apple Discussions
Try running in 'ClamShell' mode (MacBook Pro lid closed and using an external keyboard and mouse) with the Gateway connected and then run System Preferences/Displays, it should show then ...
My 1920x1080 monitor shows the following:

Remote Desktop Connection to Windows 8 PC from other computers crashing

Hi all.
Was hoping someone would be able to help me with an issue I'm having.
I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
never will. The computer has a single user profile that has full administrator rights.
I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me.
The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
the connection or do anything. I have to restart the computer from then to be able to use it again.
I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
to continue using it. Dead end there, it seems.
The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck.
If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
you think I can provide anything.
Thanks in advance!
rugbyreff

The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet
Hi Brandon
Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
this still hasn't helped.
If you have any other ideas I'd be very glad to hear them!
rrugbyreff
"If it's worth doing, it's worth overdoing" -- MythBusters

WIN remote desktop connection

Similar Messages

Maybe you are looking for