Remote Desktop Connection 8.1 cannot pin remoteapps to taskbar?

Hi,
I recently applied kb2830477 and related patches to a windows 7 enterprise node. I also updated a Windows 8 pro node to 8.1. I'm enjoying the speed and other enhancements. There are still problems, i.e. Outlook 2010 and 2013 toast and sound don't
work.
We run RDS remote apps on production 2008 r2 and distribute via .msi files; those pin to the taskbar fine. Unfortunately the newer remote applications distributed via Control Panel > Remote app and desktop connections won't pin to the taskbar, or
at least I can't figure out how.
On Win/7 I used to drag and drop 2012 r2 remote apps from the All programs > Remote app and desktop connections to the taskbar, or alternatively send to desktop, then drag that shortcut to the taskbar. that doesn't work, I get a red-lined circle
when I hover over the taskbar.
On Win/8 I used to display all apps, then right-click and choose Pin to Taskbar; that option is no longer available.
Any thoughts? These apps still launch from the desktop, puzzled as to why they won't pin to the taskbar for easy access.
Best,
S'

Hi,
Thank you for your comment.
Just for confirmation.
When you applied KB 2830477 on your client Windows 7 system, there is prerequisites which must be installed and after that you need to install the original KB. Please check that you have installed that, because on RDC 8.1 it must work. If possible try to reinstall
by restarting system and check the result.
Prerequisites:
To apply this update, you must be running Windows 7 SP1. Additionally, the following updates must be installed:
2574819: An update is available that adds support for DTLS in Windows 7 SP1 and Windows Server 2008 R2 SP1
2857650:Update that improves the RemoteApp and Desktop Connections features is available for Windows 7
Update for RemoteApp and Desktop Connections feature is available for Windows
http://support.microsoft.com/kb/2830477
Hope it helps!
Thanks,
Dharmesh

Similar Messages

When I open Remote Desktop Connection, it reads "cannot open default.rdp". What can I do to fix this?

Hi, when I open RDP on my iMac, it reads "cannot open default.rdp" and it never saves my preferences or connections. It resets after each launch.
How do I go about fixing this?
UPDATE and FIX
I went to the Finder menu, clicked on GO, held down Option (Alt) to bring up the Library.
In the Library, I browsed to Preferences, found the com.microsoft.rdp plist and deleted it. Then I emptied my Trash. If you get an error saying rdp plist is in use and cannot be deleted, quit out of RDP or reboot the machine (if quitting RDP doesn't work).
Also, there was a permissions issue. I browsed to the Applications folder, located the Microsoft Office folder, right clicked the folder (or CTRL click) and selected GET INFO. First--In order to make any changes, authenticate with admin privileges using the lock icon (put in your username and password). From there (under Sharing & Permissions), I made sure my username (account currently logged in) and everyone had Read & Write privileges, then I clicked on the little gear icon (drop-down) and selected Apply to Enclosed items.
Voila!
This worked for me.

Actually, I still receive an error when I try to save the connections.
I get an error that reads
"Make sure that you have permission to write to the location where you want to save the file"
Any help with this would be great!
ah, RDP on a mac

Remote Desktop Connection using the WRT54GC

I replaced a wired router with a Linksys WRT54GC wireless router. Connected to the wired router was a wireless router configured as an access point. I have 2 laptops and I successfully connected to the Internet from both. I was also able to connect to one of the laptops through the wireless access point using Remote Desktop Connection. The only difference between the configuration with the previous router and the Linksys is that the laptop with the Remote Desktop software (the host) was hard wired. Using the Linksys I can successfully access the Internet from both laptops. I can also get to the host computer over the LAN using Remote Desktop Connection. I CANNOT however access the host computer outside the LAN. I configured the router correctly using port forwarding and a 3389 port. I checked "enabled" and entered the IP Address of the host laptop (the one with the Remote Desktop Function). I disabled all security in the router. I have a dynamic address through dyndns.org and have setup the DNS portion of the router accordingly. Can you explain why I can no longer access my home computer remotely using Remote Desktop with the Linksys.

Are you able to access Remote Desktop Connection directly connecting to the modem.

Remote Desktop Connection won't work from Leopard to Windows XP

Hi, folks:
I'm unable to connect to my work XP computer via my home iMac (Leopard 10.5.7) using Microsoft's Remote Desktop Connection for Mac. The XP settings are correct, I'm connected on my work network VPN, and I don't believe I have any router firewalls causing the problem --- the reason I know this is because I also have an MacBook running Tiger (10.4.11) and it has been connecting to my work PC without any problems. So, this must be a Leopard firewall setting?
As far as that goes, on my iMac I've got Screen Sharing, Remote Login and Internet Sharing turned on. Again, work network VPN is on.
I'm getting this error from Remote Desktop Connection:
"The Mac cannot connect to the Windows-based computer
This problem can occur if:
- The Windows-based computer is not set up to accept remote connections
- The Windows-based computer is not turned on
- The Mac, or the Windows-based computer is experiencing network problems
Try connecting to the Windows-based computer again, or contact your administrator"
Anyone know of a fix? I'd greatly appreciate it!
Thanks.

What Firewall setting do you have on your Mac? Try setting it to allow all connections. At least as an experiment.
Do you have any Proxies set in System Preferences -> Network -> Advanced -> Proxies? If yes, then is it possible that "Bypass" list is not covering the XP system.

Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.

I had a Windows 2008 server which was upgraded to 2012. Now RDC doesn't work and I get the following message:
Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.
RDC works on the server because I can reach it via other windows machines, just not my Mac any more. I suspect it is a certificate issue but I can't find it in my key chain.
Any suggestions?

Hi,
You might want to follow the below Thread which best suits the current scenario
https://social.technet.microsoft.com/Forums/itmanagement/en-US/2bc873ed-6c11-4767-8ce3-4df8549aff20/remote-desktop-connection-cannot-verify-the-identity-of-the-computer-that-you-want-to-connect-to?forum=winservergen
Hope this helps !
Regards,
Sowmya

Windows 7 remote desktop connection cannot logoff the local user

Windows 7 remote desktop connection cannot logoff the local user
Remote Desktop connection:
(This experience is from Windows 7 remote to Windows Embedded Standard 7 computer)
I used Remote Desktop to try to log on to a Windows 7 (WES7E) computer and someone is already logged on locally (Console Session), I saw a message like this:
"Another user is currently logged on to this computer. If you continue, this user has to disconnect from this computer. Do you want to continue?"
I click on Yes.
Then I saw "Please wait for [username] to respond". No action from the logged-on local user, I waited for 30 seconds, then I was able to login the computer and at the same time was able to disconnect the logged-on local user.
Question:
1. "Another user is currently logged on to this computer..." message doesn't show me the actual logged-on user name. Is there any way to show the user name in this pop-up message?
2. After waiting for 30 seconds, I was able to login the computer and the logged-on local user is disconnected, however this local user is never been logged-off. I wanted to logoff the local user (with Console Session) when I made the connection remotely
to the computer from remote desktop (Just like Windows XP) Is there any group policy can change the behavior?
The policies I have looked at are:
Local Computer Policy | Computer Config | Admin Templates | Windows Components | Remote Desktop Services|Connections|Deny
logoff of an administrator logged in to the console session => disabled
Regards,
Mei Davis

Hi ,
These behavior is by design. There is no way to change that. Thank you for your understanding.
Best Regards.
Tracy Cai
TechNet Community Support

Since upgrade to Windows 8, cannot save .rdp files under the Remote Desktop Connection application on the Desktop

Since I upgraded to Windows 8, I am no longer able to save individual Remote Desktop Connection files as .rdp files. I am talking about the traditional Remote Desktop Connection application on the Desktop that was in previous Windows versions, not the
Remote Desktop App from the Windows 8 store.
When I try to click on the Save button I get "An error occurred while saving to file"
When I try to click on the Save As button I get "Unable to open connection file" with the file address being where I tried to save it with the file name at the end.
Also when I upgraded to Windows 8, my .rdp files disappeared from my Documents folder.
I need to create different .rdp files for different programs that my employees get into on my server. Now I have to hand type all the info each time into the Programs tap on the Remote Desktop Connection window, because I can't save to an
.rdp file.
I like the Remote Desktop App from the Windows store but it won't let me designate specific programs to use using standard dos notation (ie c:\program files\ etc..). It just goes to my server desktop.
I want to promote Windows 8 to my employees but I need either .rdp files for the traditional Remote Desktop Connection or the ability to open specific programs using dos notation in the Windows Store Remote Desktop App.

I know this is an old post but others might still be having the problem. Here's what I did.
Create a new text file and open it in notepad. Copy the below into it and edit for your environment. (IP, screen size).
screen mode id:i:2
desktopwidth:i:1920
desktopheight:i:1080
session bpp:i:24
auto connect:i:0
full address:s:192.168.x.x
compression:i:0
keyboardhook:i:2
audiomode:i:2
redirectdrives:i:1
redirectprinters:i:1
redirectcomports:i:1
redirectsmartcards:i:1
displayconnectionbar:i:1
username:s:USERNAME
domain:s:DOMAIN
alternate shell:s:
shell working directory:s:
disable wallpaper:i:1
disable full window drag:i:1
disable menu anims:i:1
disable themes:i:1
bitmapcachepersistenable:i:1
use multimon:i:0
winposstr:s:0,3,0,0,800,600
audiocapturemode:i:1
videoplaybackmode:i:1
connection type:i:7
networkautodetect:i:1
bandwidthautodetect:i:1
enableworkspacereconnect:i:0
allow font smoothing:i:0
allow desktop com:0
disable cursor setting:i:0
redirectclipboard:i:1
redirectposdevices:i:0
drivestoredirect:s:*
autoreconnection enabled:i:1
authentication level:i:2
prompt for credentials:i:0
negotiate security layer:i:1
remoteapplicationmode:i:0
gatewayhostname:s:
gatewayusagemethod:i:4
gatewaycredentialssource:i:4
gatewayprofileusagemethod:i:0
promptcredentialonce:i:0
gatewaybrokeringtype:i:0
use redirection server name:i:0
rdgiskdcproxy:i:0
kdcproxyname:s:
You don't need to worry too much about what's in here. Save the text file as
filename.rdp then rightclick on the file and select edit. The familiar GUI rdp session editor will open. You can make changes in the GUI and
save or save as a different session.
Hope this helps.

Server 2012 R2 Remote Desktop Connection Broker

I have installed RDS on a server named PLUTO on which Windows 2012 R2 datacenter is in. There is a domain controller (domain name: AGROSY) running on a Linux server. We have used Samba 3.6.6 to control the file sharing system.
When I attempt to install RDS in Server Manager, it states as following: could not retrieve the deployment information from RD connection broker server pluto.AGROSY.
Then, I searched a lot of solutions, e.g. and tried as following:
Enter-PSSession -ComputerName pluto --> which works;
but Enter-PSSession -ComputerName pluto.AGROSY --> which gives the error message as: Enter-PSSession : Connecting to remote server pluto.AGROSY failed with the following error message : WinRM cannot process the request. The following
error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request.
If I ping the pluto.AGROSY, it works as well.
I have no idea how it can be solved, please help me out. Thanks a lot!

Hi,
Thanks for your comment. Sorry for late reply.
Initially please enable the PowerShell remoting in your case.
Enable-PSRemoting
http://technet.microsoft.com/en-us/library/hh849694.aspx
For FQDN name, please see that RDCB is properly configured and also certificate which you have used for RDS environment must be trusted with its private key and must match the FQDN name of the server. Did you seen the certificate has been properly used and
configured. You can go through following article for certificate and also for configuring RDCB role.
Configuring RDS 2012 Certificates and SSO
Configuring HA for the Remote Desktop Connection Broker in a 2012 RDS Farm
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Server 2012 RTM Remote Desktop Connection Broker Role Won't Install

Hey guys,
I have been searching for and trying fixes for this for 3 days, and I've gotten no where. Thanks in advance for trying to help me out.
Here's the situation:
I have a brand new installation of the Windows Server 2012 Datacenter 64-Bit RTM from MSDN. This is my one and only server (just my personal one for home), so I'm using this single server to run all of the services that I need. After a fresh
installation, I added the AD and DNS roles and promoted the server to the PDC. Then I go to add the Remote Desktop Virtualization Services (the VM virtualization role). The installation fails, but I can't find any explanation as to why.
I've wiped out the OS and reinstalled from scratch at leat 15 times, trying various combinations, fixes, approaches, etc. including powershell, Remote Desktop Services Deployment, standard role-based deployment, etc.
Using the role-based deployment, I can get every 'Remote Desktop Services' component to install except the Remote Desktop Connection Broker. I've tried enabling RDMSUI_TRACING, but didn't get any information at all as to why it's failing. I also
cannot find RDMSDeploymentUI.txt log.
I've also tried to deploy this using Powershell using this command:
New-SessionDeployment [-ConnectionBroker] <string> [-WebAccessServer] <string> [-SessionHost] <string>
That particular item does provide some error messages, but they seem to complain about the Session Host not being able to install due to not being able to find the connection string key in the registry for the Windows Internal Database. However, I can
get the session host and every other component to install using role-based deployment, except the Connection Broker.
I've run an SFC scan, which found no issues. I've also tried applying the one update available in Microsoft Update, and tried it without applying that update (reinstalling between attempts of course).
I'm completely at a loss. Has anyone encountered this before? Any suggestions would be greatly appreciated. Is there a powershell command for just installing the Connection Broker that might provide some additional error information, or any
information at all?
I would greatly appreciate any help anyone could offer. I'm willing to try anything. Thanks for taking the time to read this.
Sincerely,
Dominick

Also Found this:
1. You try to install the Remote Desktop Connection Broker (RDCB) on a server that also has the Active Directory Domain Server (domain
controller) role installed. This configuration is not supported by Microsoft. You need to install the RDCB on a server that does not have this role installed. See: Remote Desktop Services role cannot co-exist with AD DS role on Windows Server 2012 http://support.microsoft.com/kb/2799605
2. If you don’t have the Active Directory Domain Service install, this issue might be caused by the Windows internal database (WID) that
the connection broker installs and the Windows Update KB2821895. If you have KB2821895 installed, unfortunately you can not uninstall this KB. Try to install the Remote Desktop Connection Broker (RDBC) role on a server that does not have this Windows update.
Note: There is currently no official communication from Microsoft that here is an issue with RDBC and KB2821895. However, try the RDBC installation
without this KB and see what happens.
For more information, Refer below link...
http://fabrikam.wordpress.com/2013/07/15/connection-broker-installation-failedremote-desktop-deployment-issues/

Remote Desktop Connection Server 2012 Clients only using on DC as Logon Server.

I am using Server 2012 and have an RDC Server running on a VM. Originally I had ordered the licensed version as Essentials was provided to me which does not allow for a full domain environment, which is required for the RDC server. Anyway, I
used Eval versions to get started, not thinking or realizing that the DC would never be able to get Activated since it is an Eval. So after 4 days I have finally, loaded Server 2012 on a new VM, promoted to DC, Transferred FSMO roles...DNS is up and
replicating across both DC's. The Eval keeps shutting off and was going to demote it and remove, but whenever it is shutdown the Clients receive a "No Logon Servers are available " error. I start up the old DC and it works. I doublechecked
all of the roles have been moved, I checked the RDC gateway, everything points to the same Domain information, but when I check an account using 'CMD set' it shows the old DC as the Logon Server. Is there something I am missing in the RD Gateway or somewhere
else. Is there a way to force it to use the new DC? I have tried setting the options in remote desktop connection to use a particular TS Gateway setting and it doesnt seem to work. Can someone please help me think about this and offer a
suggestion or let me know if you need more info. I can figure nothing else out at this point.
Thanks so much in Advance.
-T

it sounds like your clients / rdc servers may still be pointing to the old DC for DNS.
Can you check you have updated DNS on the clients to talk to your new domain controller.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
The new DC is the only DNS server listed on the RDC Server and is the only DNS listed for the clients other than the gateway which have as a secondary. If I change the static on the old DC I cannot login, as soon as I put it back, I can login and it
shows that DC as the logon server.
I did a simple recursive test on both DNS servers....The new Domain Controller passes, the Old One which I am trying to remove, does not.
I will reply with any other updates as I continue to look into this and thanks for the suggestions.
So I also Pinged the domain from the RDC Server as suggested and it replies back with the old DC IP.
Not sure why.

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 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 with WRT54G from Novice

Well, I’m usually pretty good at using Google and forums to eventually figure out how to fix my problem but this one absolutely has me stumped and I’m hoping someone out there has an answer for me. For the record, I have probably a beginner/intermediate knowledge of computers so if you know the answer to my problem, try to explain it simply! ****TO ANYONE WHO TAKES THE TIME TO READ THIS THING AND CAN OFFER SOME ADVICE-THANK YOU!!!!***
THE PROBLEM
I would like to be able to use Remote Desktop to log into either of my home computers from basically any computer on the internet.
THE SETUP
I have two computers, whose names are LAPTOP and DESKTOP that are both running Windows Vista Ultimate. Both of the computers are connected to a Linksys WRt54G Router ; one wired, the other wirelessly. The Linksys router is then connected to a Westell DSL Modem that connects to AT&T’s internet service.
SETTINGS
My DSL service only provides me with a dynamic IP address so I signed up with no-ip.com. Through that site, I bought a domain name and downloaded their small program that runs in the background of my desktop computer. The program checks what my IP address is every couple of seconds and if it changes, it notifies their server so that anyone who types in my domain name is directed to the new IP address.
ROUTER (Firmware 4.20.6)
Basic Setup Page: The Router Name is just the model number, the Server Name is my DSL provider and the Domain Name is the name I chose and registered with No-IP.com. (www.mydomainname.com, for example.) DHCP Server is ENABLED. DDNS Service is DISABLED. Under Advanced Routing, it is set in GATEWAY mode.
Security Page: Firewall Protection is ENABLED. Block Anonymous Internet Requests is NOT checked. Filter Multicast, Filter Internet NAT Redirection and Filter IDENT ARE checked.
Applications and Gaming Page: I chose two port numbers, one for each computer that I want to connect to. On the first line, I have Application: RDP, Port Range: 49200 to 49200, Protocol: Both, IP Address (The IP address of the computer I want to connect to) and the Enable box IS checked. [I did the same thing with the second line for the other computer, but with a different port number and that computer’s IP address)
Administration Page: Access Server is HTTP, Wireless Access Web is ENABLED, Remote Management is ENABLED through Port 8080, and UPnP is ENABLED.
WINDOWS VISTA SETTINGS
First, I went to the Remote Desktop Settings of the target computer and ENABLED Remote Desktop Connection and allowed computers running any version of Windows. I also confirmed that the box labeled “Allow This Computer To Be Controlled Remotely” WAS checked. I then made sure that I had a user name, it had a password associated and that it had Administrator priveledges. I went back to the Remote Connections screen and added the user name as being allowed to connect. (I think this is redundant since it’s both the owner of the computer and has Administrator Status.)
Next, per Randomly Googled Internet Advice, I went into the registry and changed the port number that Remote Desktop listens for incoming connections to Port 49200 to match the router settings. [Registry Entry that I modified was: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp]
Finally, I went to the Windows Firewall and Added (opened) port 49200 for use as a Remote Connection. I kept the protocol as TCP and confirmed the scope was set for Any Computer.
CURRENT STATUS
If I go to Explorer and enter my IP address with a colon and the specify port 8080, I can get the login screen for the router. Same thing happens if I just enter my domain name and port 8080. However, if I switch the 8080 port and use one of the ports I chose (49200), it cannot connect, either using the Public IP address or the domain name. (I’m trying to connect using a wireless card and not connected to my local network so I know it’s the same as if I was anywhere else.)
I’m not sure why it won’t let me connect; it feels like the router will not allow the connection to pass through it to the port I’m asking it to forward to. I’m guessing someone out there who took the time to read it is shaking their head at all the information I provided and knows the one dumb thing I missed!
Thanks again!

I'm attempting to do the same thing with my home network. the only differences are that i have cable internet from comcast and i'm running vista business. my router is the wrt54gs. i'm assuming that the web page is similar for adjustmants. To be honest i cannot figure out how to do a remote destop too. so i went to www.logmein.com and installed the program. once installed to to every computer you want to have access too and log into the website. then click on the add computer icom. full control app sharing etc... even better when you connect you have the option to deactivate the local host mouse and screen to prevent anyone seeing what your doing.
If you resolve the router issue would you let me know. plz thanks
Forest

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 stop working after upgrade from 10.5.8 to 10.6.1

I too could not connect to a W2K3 server with RDC 2.0.1 after upgrading from Mac OS X, 10.5.8 to 10.6/10.6.1. I have another Mac which is on 10.5.8 and connect fine with the same version of RDC 2.0.1 as well as other PC with Terminal Service Clients.
There is no change on the server side. I have uninstalled and reinstalled RDC 2.0.1 several time and it did not resolve the issue. To rule out firewall/network, I tested with another remote desktop application called CoRD (for Mac) on the same laptop running SL 10.6.1 and it connected to the same W2K3 server fine.
One thing that is worth mentioning (in my case), when it does not connect, RDC totally quit (not running anymore. Not minimize, no cannot connect error message, no little dot on the Dock for RDC, nothing) right after I put in the credential in. When looking at the log entries that are related to RDC in the Console application, I see the following
machine 10.6.1. with RDC 2.0.1 (non-working)
9/22/09 1:17:16 PM [0x0-0x3a03a].com.microsoft.rdc[468] objc[468]: Class NLAssertionHandler is implemented in both /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/Netlib.framework/Versions/12/Netlib and /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL . One of the two will be used. Which one is undefined.
On the 10.5.8 machine with RDC 2.0.1 (working), I see the following entries
9/22/09 1:13:23 PM [0x0-0x24f24f].com.microsoft.rdc[5502] objc[5502]: Class NLAssertionHandler is implemented in both /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/Netlib.framework/Versions/12/Netlib and /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL . Using implementation from /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL .
9/22/09 1:13:39 PM Remote Desktop Connection[5502] * _NSAutoreleaseNoPool(): Object 0x16a25c20 of class NSCFArray autoreleased with no pool in place - just leaking
Stack: (0x9277af4f 0x92687432 0x93062bf5 0x926ce0fb 0x9723dff5 0x9268d52c 0x92fd447a 0x92fd4753 0x92fd4a48 0x930375da 0x530bac 0x4831a2 0x483750 0x483c0b 0x47a811 0x4796ac 0x485dad 0x47d475 0x5099dc 0x574c70 0x4ade03 0x4ae65d 0x4ae6f7 0x4ac8dd 0x53260c 0x534187 0x4ae76a 0x4ae7d0 0x4ae88e 0x493925 0x4ae13d 0x533b1a 0x53da6c 0x94a48057 0x934b3155 0x934b3012)
Any help would be appreciated

Doing some more troubleshooting after my post above as I saw a couple of entries referencing Stop Light keep popping up in the log of the Console. I removed Stoplight and Cocoa Gesture (for good meausre) and RDC 2.0.1 started working. I think it is Stop Light which causes RDC stop working, but I don't have to time right now to put Cocoa Gesture back to confirm that. I might if I have the time or post here if you have Stop Light installed as well and removing it resolved the RDC issue for you.

Remote Desktop Connection 8.1 cannot pin remoteapps to taskbar?

Similar Messages

Maybe you are looking for