Cannot Remote Desktop!!

I did everything right. I have a DSL subscription with a static IP address assigned by my ISP. My ADSL modem is Linksys ADSL2MUE, and the router is WRT54GS v4 using PPoE. My 2 wirelessly connected PCs are using static IP addresses, and they are happily connected to the internet. The port forwarding (for port # 3389) is properly enabled through the Applications and Gaming section on the router's web-interface for only one of the PCs' IP addresses. I only use the native Windows XP firewall, and had excepted the RDP from the blocked programs/ports.
When I externally ping that ISP-assigned static IP address I continuously get timed out, and I could never get it to create an external peacefully Remote Desktop however, I managed to Remote Desktop internally, from one of the PCs to the other.
Please help figure out what I'm missing.
Thanks
Message Edited by Ehab on 03-04-200711:56 AM

open ports 65301, 22, 5631 and 5632
Love is just a word".... It has no emotions...only thoughts, imaginations.

Similar Messages

Remote desktop connection from windows computer to TC

hi all,
what I have: I have a TC 2TB, bought it three months ago.
what I did: I have set it up at home. Using as base station for all my devices, iphone 4, ipad 2, macbook air and also other laptop. My TC is connected to ADSL modem with an ethernet cable (as expected). with port forwarding option of ADSL modem (in NAT Properties), I managed to forward any connection to TC. I have a static IP by the way.
what I can do: from work or anywhere else other than my home network, I can connect to my static IP (via "Connect to Server" option in any mac device), it pops up a user name and password window, I login with my TC user name and decive password. In an instant my TC disk is mounted on my desktop, and I can reach all my files in it as if it is an external hard disk.
what I cannot do: from a windows computer outside my network, I cannot connect to TC. I try to do this through "Remote Desktop Connection". Is this possible? If so how? Is this a problem related to network connection or TC settings?
aakibar

You cannot remote desktop into a TC..
In fact you cannot remote access a TC from windows.. sorry.. but SMB protocol is blocked on the internet.. there are work arounds but no security.. don't do it.
The only other protocol the TC offers is AFP.. there is no AFP file access software available for windows. You need to use a Mac.
The best alternative is vpn.. replace your current adsl modem router with a vpn one.. eg draytek.. then you can access your home network. Since I presume when you say you have static ip you mean public IP then vpn is easy (well once setup it is).. reliable and secure.

Cannot run more than one instance of a remote app in remote desktop services Server 2012

All,
I installed "Remote Desktop Services (RDS) Quick Start Deployment for RemoteApp, Windows Server 2012 Style" using the instructions here http://blogs.technet.com/b/yungchou/archive/2013/02/07/remote-desktop-services-rds-quick-start-deployment-for-remoteapp-windows-server-2012-style.aspx
I need to set up an image viewing program (Olyvia) to allow students using Macs and iPads access to this windows only application in order for them to get their work done. We may have 12 or more students accessing and trying to run the Olyvia application
at any one time.
All works good, except that I cannot run the Olyvia application (setup as a remoteapp program) more than one instance at a time. That is, when I start up "olyvia" on a Mac, it works great. If I leave it up and running, and then try
and start up "olyvia" on an iPad (using different accounts), I get the following error message:
"Cannot run more than one instance of this program simultaneously. Either the program is already running, or it has not been terminated completely."
I need to understand the root issue.
1. Is this a licensing issue? So, I need to add some CALs to the RDS server?
2. Is this a application issue with "olyvia"? So, no matter what I do, it is not going to be able to be used by more than one person at a time when configured as a remoteapp?
3. Did I not "publish" the application correctly?
4. Is this happening because I followed the "quick start" guide?
Appreciate any help I can get on this. We have no problem getting CALs, I just need some help with the root issue.
Thanks,
Geoff Weatherford
CVMBS, CSU

Hi Geoff,
Each application uses different techniques for determining if multiple instances are running. If you can determine what method it is using then perhaps you could use App-V or other virtualization software.
In the best case you really should direct your question to the maker of Olyvia. The reason I said that is they specifically designed their software to prevent multiple instances, so the first question is, why? Is it related to Licensing?
Compatibility? If you knew the specific reason(s) why they are doing it and the technique used then at the point using a virtualization technique may be the best option.
-TP

Cannot use Remote Desktop host on Windows 8.1 Pro, termsrv corrupted?

Hello,
Few days ago I upgraded my home desktop machine from Windows 8.1 to Windows 8.1 Professional so I can use the Remote Desktop feature.
I enabled everything needed, checked "Allow computers to connect to this computer" from the Remote Settings, forwarded the port 3389 in my rounter and allowed it in my firewall etc...
But I still can't connect to this computer from outside my home network or inside it. The error I get trying to connect is this:
(For some reason i still can't post images in this forum...) So I posted a link below to my original thread with the images
I'm trying to connect using a laptop running Windows 7 Home Premium.
After searching around I found out that the service responsible for the RDP is called "TermService", I found it on my services but was unable to start it:
(For some reason i still can't post images in this forum...) So I posted a link below to my original thread with the images
Also, notice the description of the service. So I tried to run a System File Checker on the service's DLL (sfc /scanfile=c:\windows\system32\termsrv.dll) and got this log:
2014-10-05 14:20:41, Info CBS TI: --- Initializing Trusted Installer ---
2014-10-05 14:20:41, Info CBS TI: Last boot time: 2014-10-05 13:56:05.492
2014-10-05 14:20:41, Info CBS Starting TrustedInstaller initialization.
2014-10-05 14:20:41, Info CBS Ending TrustedInstaller initialization.
2014-10-05 14:20:41, Info CBS Starting the TrustedInstaller main loop.
2014-10-05 14:20:41, Info CBS TrustedInstaller service starts successfully.
2014-10-05 14:20:41, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2014-10-05 14:20:41, Info CBS Startup processing thread terminated normally
2014-10-05 14:20:41, Info CBS Starting TiWorker initialization.
2014-10-05 14:20:41, Info CBS Ending TiWorker initialization.
2014-10-05 14:20:41, Info CBS Starting the TiWorker main loop.
2014-10-05 14:20:41, Info CBS TiWorker starts successfully.
2014-10-05 14:20:41, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:41, Info CBS Universal Time is: 2014-10-05 11:20:41.783
2014-10-05 14:20:41, Info CBS Loaded Servicing Stack v6.3.9600.17246 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17246_none_fa4ae8e99b1f603c\cbscore.dll
2014-10-05 14:20:41, Info CSI 00000001@2014/10/5:11:20:41.786 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffee15c60e5 @0x7ffeeace2e53 @0x7ffeeace24ac @0x7ff69a94d2df @0x7ff69a94dc97
@0x7fff02912225)
2014-10-05 14:20:41, Info CBS SQM: Initializing online with Windows opt-in: True
2014-10-05 14:20:41, Info CBS SQM: Cleaning up report files older than 10 days.
2014-10-05 14:20:41, Info CBS SQM: Requesting upload of all unsent reports.
2014-10-05 14:20:41, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2
2014-10-05 14:20:41, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2014-10-05 14:20:41, Info CBS NonStart: Set pending store consistency check.
2014-10-05 14:20:41, Info CSI 00000002@2014/10/5:11:20:41.801 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffee15c60e5 @0x7ffef3637fc0 @0x7ffef36380f2 @0x7ff69a94ca25 @0x7ff69a94dcae
@0x7fff02912225)
2014-10-05 14:20:41, Info CSI 00000003 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x559943db20
2014-10-05 14:20:41, Info CSI 00000004 Creating NT transaction (seq 1), objectname [6]"(null)"
2014-10-05 14:20:41, Info CSI 00000005 Created NT transaction (seq 1) result 0x00000000, handle @0x26c
2014-10-05 14:20:41, Info CSI 00000006 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2014-10-05 14:20:41, Info CSI 00000007@2014/10/5:11:20:41.999 Beginning NT transaction commit...
2014-10-05 14:20:41, Info CSI 00000008@2014/10/5:11:20:41.999 CSI perf trace:
CSIPERF:TXCOMMIT;143
2014-10-05 14:20:42, Info CSI 00000009 CSI Store 367642371808 (0x00000055993166e0) initialized
2014-10-05 14:20:42, Info CSI 0000000a [SR] Verifying 1 components
2014-10-05 14:20:42, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:42, Info CSI 0000000c [SR] Verify complete
2014-10-05 14:20:52, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:55, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:55, Info CSI 0000000d [SR] Verifying 1 components
2014-10-05 14:20:55, Info CSI 0000000e [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:55, Info CSI 0000000f Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000010 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 00000011 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000012 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 00000013 [SR] This component was referenced by [l:154{77}]"Package_3_for_KB2959626~31bf3856ad364e35~amd64~~6.3.2.0.2959626-3_neutral_GDR"
2014-10-05 14:20:55, Info CSI 00000014 Hashes for file member \??\C:\Windows\System32\termsrv.dll do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000015 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000016 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll"; source file
in store is also corrupted
2014-10-05 14:20:55, Info CSI 00000017 [SR] Verify complete
2014-10-05 14:20:55, Info CSI 00000018 [SR] Repairing 1 components
2014-10-05 14:20:55, Info CSI 00000019 [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:55, Info CSI 0000001a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 0000001b [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 0000001c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 0000001d [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 0000001e [SR] This component was referenced by [l:154{77}]"Package_3_for_KB2959626~31bf3856ad364e35~amd64~~6.3.2.0.2959626-3_neutral_GDR"
2014-10-05 14:20:55, Info CSI 0000001f Hashes for file member \??\C:\Windows\System32\termsrv.dll do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000020 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000021 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll"; source file
in store is also corrupted
2014-10-05 14:20:55, Info CSI 00000022 [SR] Repair complete
Since it's the first time I use this tool I'm not familiar with this log file, but what I managed to figure out from it is that termsrv.dll is corrupted and windows cannot repair it for some reason.
My question is:
How can I repair this file? Is this even the problem preventing me from connecting to this computer via Remote Desktop?
Here's a link to my original question which contatining the images.
http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/cannot-use-remote-desktop-host-on-windows-81-pro/e4776239-4d9e-4934-ae2d-b87cc09f7ade

managed to figure out from it is that termsrv.dll is corrupted and windows cannot repair it for some reason.
So, the next step supposedly is
using DISM.
Coincidentally I reached that page last night from
this one, which I thought gave me a better awareness of how much manual repair might be possible. E.g. maybe the WinSxS isn't quite as fragile as we are being led to believe? (It's making me feel sort of like how I used to feel about the
registry when seeing all the caveats about using RegEdit before I got used to that tool.)
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779(v=WS.10).aspx
Something else that I became aware of yesterday serendipitously is SxStrace.exe. I have never seen it used but it sounds useful. E.g. perhaps easier to interpret for supplemental clues than the ProcMon trace that I usually advocate.
Or perhaps use both and see in ProcMon when the SxStrace is writing. E.g. filter with Operation Is WriteFile.
However, what I would do first is find out what the state of your system is regarding that module. E.g. try this Powershell pipeline to list what you have.
PS C:\windows> dir -R -Fil "termsrv.dll" | sort-object FullName | ft Length, FullName -AutoSize
Note that I am giving you the whole command line, including prompt to show where the command should be started from.
C.f. another thread where doing the same diagnostic procedure seems to be finding more a problem with the Windows Update software than with the user's WinSxS cache.
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_store/windows-81-store-error-0x80070002-comprehensive/2b0ed3e1-1835-4517-97dd-0a7abb6ef74c?page=3#LastReply
HTH
Robert Aldwinckle

Remote Desktop Connection - cannot proceed because authentication is not enabled

Hello,
I try to connect via RDP from a Windows Server 2008 R2 to another 2008 R2 Server.
I always get the error message.
The connection cannot proceed because authentication is not enabled and the remote computer requires than authentication be enabled to connect.
On the target machine the Remote Settings are set to:
Allow connections from computers running any version of Remote Desktop.
Firewall is disabled on both servers.
Therefor I do not understand why I get an error message, that authentication is required.
The target box is a nearly fresh syspreped machine with all current Hotfixes installed.
I already found a lot of people having that problem by using XP (old RDP client), but no one seems to have this problem when connecting from 2008 R2 to 2008 R2.
Thank you very much in advance for every hint.
BR
Matthias

Hi Matthias,
First I would like to confirm if you have deployed RDS (Remote Desktop Services) and you got the error, if so, please check this option
TS Configuration, >> RDP-Tcp Properties >> change the Security Layer to "Negotiate"
Then Recycle the TS Gateway service.
Refer to:
Unable to connect to Server using the Remote Web Workplace (RWW) Small Business Server 2008
If this issue has nothing to do with RDS, and I suppose you used the cmd "mstsc" to remote access. This issue may also occur because of the version of mstsc, please make sure it has been upgraded to the new version.
In addition, Did you have another newer server available like Server 2012? So we can test and try to use Server 2012 to remote access Server 2008 R2, and check if the issue persists.
If there is anything else regarding this issue, please feel free to post back.
If you have any feedback on our support, please click here.
Best Regards,
Anna Wang
TechNet Community Support

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

I tried to set up a remote desktop between my macmini and my work computer. I hit cancel and now the Remote Desktop will not close. I cannot shut down my computer either. How do you close a non-responsive application. I have tried everything!

I tried to set up a remote desktop connection between my MacMini and my work computer. It was not working so I hit cancel, but then the big black screen of death came up and will not go a way. I cannot close my computer nor quit the remote desktop connection. How do you close a non-responsive application? By the way, I am new to Mac and it is not as simple as hitting the Control, Alt, Delete. Please help.

virginiafromphoenix wrote:
.......How do you close a non-responsive application?.......
Try ( alt + cmd + esc ). Gives you a menu of running applications, and a chance to "Force Quit".

Cannot connect VIA Remote Desktop to Windows 8.1 on a virtual machine

I have Windows 8.1 Enterprise running in a Hyper-V VM. For some reason I cannot connect to the VM using remote desktop. I am using a Microsoft account and remote desktop is enabled and my account has access. I am able to see the VM under
networks and access shared folders. The error I am getting is "Remote Desktop can't connect to the remote computer....".
Any ideas?

My account has access to RDP. The firewall rule to allow RDP was missing the permission for public networks. After this change the RDP client can find the computer and I can get in. Yay!
Thanks for the tip to check the firewall.

Remote Desktop cannot verify the identity of the computer because there is a time or date diffrence between your computer and remote computer

Hello.....
I'm not able to log into Windows Server 2008 r2 server thorugh Remote Desktop connection, receiving below error message.
This issue is with only three servers in the environment
"Remote Desktop cannot verify the identity of the computer because there is a time or date diffrence between your computer and remote computer......"
The date/time is correct on the server when i checked in the console session of the server
Can see below messages in event logs
Event ID 1014:
"Name resolution for the name XYZdomain.com timed out after none of the configured DNS servers responded."
Event ID 1053:
The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
Any thoughts ....

Hi,
Have you tried to connect these three servers with IP address instead of computer name or DNS name?
Check Remote Desktop Connection settings: Option-->Advanced-->Connect from anywhere-->Settings-->Connection Settings-->Select “Do not user an RD Gateway server”
For more information please refer to following MS articles:
Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer
http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/c1f64836-5606-49b0-82eb-56be7f696520
Cannot connect via Remote Desktop
http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2general/thread/5087e897-8313-468c-ad37-ef18b87d4dd6
Lawrence
TechNet Community Support

Apple Remote Desktop ARD 3.7 cannot drag files from local to remote.

Apple Remote Desktop ARD 3.7 cannot drag files from local to remote. I've been able to drag n drop folders and files from my local to the remotes for years until the update to 3.7. Anyone else experiencing this issue? I've tried changing preferences. No luck. Maybe I'm missing a setting somewhere.
I'm on 10.8.5. Remote is same with 3.7 client. This happens with multiple remotes.

Let me guess. The Get and Send clibboard contents buttons are greyed out too?
It is only affecting me on clients already upgraded to 3.7. None of the clients on older versions are affected.
ARD is also crashing a lot.
Most of the time I go to a screen share to a client it takes way too long, so I clock Stop, then try to connect again and works straight away.
Hopefully a patch will be released soon.

Apple Remote Desktop CANNOT observe/control/curtain 30" Cinema Display

Apple Remote Desktop CANNOT observe/control/curtain 30" Cinema Display. All my other pc's (G4, G3, titanium, 17" Powerbooks and Macbooks) can be observed, using identical settings. i figured out that it may be the graphics card while trying to Microsoft Remote Desktop Connect to the Macbook running XP, the system crashed due to the (well known as really bad) ATI mobility XP drivers provided by bootcamp. So i quess the problem is the dual link in my G5 running on the 30". All the other remote desktop commands run fully ok. i just cannot get visual feed.
Any thoughts??
Thank you all in advance
Dual G5, Dual G4, G3, 15" titanium, 17" Powerbook, 17" Macbook Mac OS X (10.4.7)

I've had this problem, too, recently. I have two G5s running 30" displays, I'll describe my situation - it may come down to your video card.
When I try to connect to one of the G5/30" on my network (a PowerMac 7,2, 512MB, running a GeForce6800 Ultra), it sporadically gives me the same non-visual problem you're having. But every now and then, I can connect, and can't figure out why. A lot of times in the ARD multi-observe window, it reports that this machine is maxing out the memory (98.7%, putting it in the red)
However, when I try to connect to another G5/30" on the network (a PowerMac 7,3, 512MB running an ATI Radeon 800 XT), I DO get a visual.
Maybe others know of known deficiencies in ARD/NVidia connections? Or maybe it has to do with the paltry RAM in the machine?
Mark

After MS13-098 and SecurityAdvisory(2915720), Windows Server 2003 Remote Desktop(TermService) cannot start service

I have trouble with Windows Server 2003 R2 Standard. I installed the KB2893294(MS13-098) patch, and I changed the registry that is suggested actions of Security Advisory(2915720) http://technet.microsoft.com/en-us/security/advisory/2915720
Suggested Actions:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Wintrust\Config]
"EnableCertPaddingCheck"="1"
After rebooting the event viewer(system) says:
Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
User: N/A
Description:
Cannot load illegal module: C:\Windows\system32\rdpwsx.DLL
After I cannot use Remote Desktop Connection from other client.
So I check the all security patches and other hotfixies. I checked the KB2653956 and KB958476.
But TermService do not recover the error.
And then, I delete the "EnableCertPaddingCheck" registry and reboot systems.
TermService have no error. I can use Remote Desktop Connection from other client.
After KB2893294 installed, Remote Desktop Connection cannot use from other client that "EnableCertPaddingCheck" registry set to "1".
Other Windows Server 2008 systems do not effect the KB2893294 patch. But All Windows Server 2003 systems cannot use the Remote Desktop Connections after the KB2893294 patch.

Update on this issue:
The debug team has accepted the issue and has identified it as a regression. Right now they're targeting *June* as the release date for a fix. I'm attempting to educate them that customers don't just install patches the day (or even month) they're
released and that the fix needs to be moved up in priority to give a minimum of 60 days to install the patch before the time-bomb explodes.
In the meantime, a workaround has been provided that will turn off the new functionality. Note that I have not yet had a chance to test this. It entails creating a new DWORD registry entry--UseLegacyPE--and setting it to 1.
HKLM\Software\Microsoft\Windows NT\CurrentVersion\ImageHlp\UseLegacyPE
I will update this thread when I have further information.

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

Acrobat Pro XI, Server 2012 r2 Remote Desktop, cannot print until server reboot, No Pages Selected

Ever since we migrated to terminal services (remote desktop) this problem has plagued us.
We are a terminal services environment with 25 users.
Our version of Adobe is 11.0.10
I've believe I have traced the issue to temp files in \users\username\appdata\local\temp\XX
There are [email protected] files that the system locks.
Once those files are written out and the server locks them down the user cannot print .pdf files any longer.
ALL OTHER APPLICATIONS WORK PERFECTLY!
The only way to clear the situation is to reboot the server (not optimal).
And even then the problem reappears within a day.
I have read many different versions of this problem and tried many different solutions.
I have tried having the users go the advanced tab when printing and choose "print as image"
FAIL!
I have put a acroct.ini with the following parameters in the windows directory
[WinFntSvr]
TTToSysPrintDisabled=1
T1ToTTDisabled=1
FAIL!
I have tried to remove Microsoft security updates related to this issue and 3rd party fonts.
FAIL!
I've tried the "Disable Protected Mode at Startup"
FAIL!
I have rebuilt our print server with the latest drivers.
FAIL!
Since we deal with thousands of .pdf files on a daily basis this has become CRITICAL!
Please Help!

Please see this thread: No Pages Selected RDS Server 2012r2

Mac App Store cannot update itunes, OS and remote desktop; keep saying it is updated and yet ask it ask you to update as in fact it is not updated

I search my problem on web and got no solution.
1) mac app store shows some updates needed. e.g. itunes, remote desktop.
2) I clicked "update", and it changes to "installed" within seconds and then shows I have installed the update.
3) But the problem is that the software is NOT updated and the "installed icon" changes back to "update" immediately.
4) the picture below shows what happened.
5) As you can see, the remote desktop is updated twice on Mar 3 and is version 3.8.2 v1.1 but the mac app store prompt me to update it.
6) I cannot update the new version of MAC OS too.
Solution:
1) Restart app or OS. >> Failed.
2) Rebuild spotlight >> Failed.
3) Genius bar >> No hope as the Genius bar is fully booked all the time (rumors that people are selling the timeslots, guess where am I?).
Can any one help me on that.
Thanks a lot.

I tried the debug mode in mac app store too >> Fail.
The first time I feel disapointing from apple software.

Cannot Remote Desktop!!

Similar Messages

Maybe you are looking for