Connecting to a Windows computer using Remote desktop connection

I have connected a Windows 7 computer to my network using an ethernet cable to my Time Machine which is configured as an extension to my Airport network. My Mac sees the computer as shared, and I can connect to it using the name and password so I can browse files on it etc.
Nevertheless Microsoft Remote Desktop Connection will not connect to it, saying there is a network error. It has been suggested that if I use its IP address rather than its name it may work, but how do I remotely find out what its IP address is on the Airport network? I have not found the way using Airport utility or help.
thanks in advance...

You are using the Mac version of RDC aren't you?
If so, please post questions regarding it on Microsoft's own forums for the Mac version of RDC, as Apple discussions only provide support for Apple products

Similar Messages

I am accessing a windows server using remote desktop and I am wondering if I can transfer files by sharing drives?

I am accessing a windows server using remote desktop and I am wondering if I can transfer files by sharing drives?

Probably. You may be able to use Finder > Go > Connect to server to access the server. You may be able to share folders using Remote Desktop too. Whichever one you like the best.

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

Using Remote Desktop - Windows RT 8.1

Hello,
I was directed here from the Microsoft Answers community site about my issue regarding Remote Desktop on my Surface 2 RT.
I am trying to connect my Surface 2 to my Windows 8.1 Pro desktop (it has Media Center on it as well).
The problem that keeps surfacing on the Surface 2 is the credentials. I have checked time and time again to make sure my credentials were correct every time I try to get Remote Desktop on the Surface 2 to connect to the Windows 8.1 Pro desktop - it says
my credentials did not work. Both machines are connected to my Microsoft account, and both machines use my Microsoft credentials to log in as well as sync.
I have used the Incoming Connections troubleshooter on the Windows 8.1 Pro desktop, it didn't raise any issues regarding my network connection (both the Win8.1 machine and the Surface 2 are on the same network).
If I understood the FAQ correctly, I can connect my Surface 2 RT 8.1 to a computer running Windows 8.1 Pro (but not vice versa) using Remote Desktop.
So what underlying issue could there be?

Are you able to RDP into the desktop with another machine? Is it only the Surface RT that doesn't work?

Printing to a Printer Connected to TIme Machine when using Remote Desktop

Hi,
I am having trouble printing to a printer connected to our wireless network via Time Capsule when I am on my remote desktop connection. Printing from all other programs work. I downloaded Bonjour on our Windows based server, and it did not detect any printers. When I am connected directly to the printer, I can print when using remote desktop. Any suggestions are much appreciated.
Thanks!
Mac OS X (10.5.4)

Airport Extreme/Express do emulate Jetdirect/port 9100 printing, but that isn't what they use for printing from OS X. OS X and the Bonjour/airport software use USB port redirection, a unique and separate method.
If the HP driver supports any protocol over ethernet, it would be appletalk. Does that router server use appletalk?

Not able to use remote desktop externally on a WRV200

Hello all,
Untill 5 minutes ago I wasn't able to get remote desktop to work from an extern computer to my computer which is wireless connected in our network. It worked from a network computer from the beginning.
I have port 3389 correctly forwarded to my static intern ip address (same way as i did with my ftp server which works properly, so I guess I did it wright)
Just 5 minutes ago I found out that it does work when I enable DMZ (see bottom for DMZ details).. What am I doing wrong? I prefer not to use DMZ since it will automatically forward all internet port requests which arent forwarded to any of the other computers, which makes my computer quite vulnerable, wright? (I am using the win xp firewall, but still)
Thanks in advance!
Edit 1: I have UPNP enabled
Edit 2: I have remote desktop excluded in the windows firewall, but thats logic since remote desktop does work from another network computer and with DMZ enabled
Edit 3: I'm the only one in our network who is using remote desktop
Edit 4: I also tried to forward all these ports to my pc: 22, 65301, 5631-5632
The DMZ screen allows one local PC to be exposed to the Internet for use of a special-purpose service such as
Internet gaming and videoconferencing through Software DMZ. Whereas Port Range Forwarding can only forward
a maximum of 10 ranges of ports, DMZ hosting forwards all the ports for one PC at the same time.
Message Edited by PulpVictim on 07-06-2007 02:30 AM
Message Edited by PulpVictim on 07-06-2007 02:34 AM
Message Edited by PulpVictim on 07-06-2007 02:35 AM
Message Edited by PulpVictim on 07-06-2007 02:39 AM

Enable the logs on your router. Then try to do remote desktop. It will fail of course. After it does, view the logs, there might be ports listed in the incoming logs that you failed to forward.

Windows server 2003 Remote desktop over WAN problem.

Ok so problem is there is a 2003 windows server in my office. Any computer phone etc. can connect to it via Remote desktop if they are in the LAN network. I have port forwarded 3389 , disabled firewalls , there is no antivirus software on the server.
BUT I cannon log in over WAN. Heres the problem.
I type in the WAN ip I connect with credentials.
This is what i get:
Connecting...
Negotiating credentials...
Then it just suddenly force closes.
Also tried from a Windows 8 PC , when trying to connect it INSTANTLY throws me an error saying:
This computer cant connect to the remote computer. If the problem continues contact etc..
No matter where i try , a pc , a laptop , a phone , a tablet it just force closes. I can see that the devices are able to see the server and are trying to connect , but the connection just force closes for no reason and no error is shown. Also I dont see
anything in the event viewer on the server. The credentials are correct also. And the port is forwarded correctly.
Where could the problem be?

Hi,
Thank you for posting in Windows Server Forum.
As you have commented that you have forwarded port correctly at windows end, but still suggest you to check whether you have port forwarded on Router which you are using for WAN connections.
Can your local system can make successful ping to the remote server from WAN connections?
For testing you can telnet <router ip> 3389 and if you get blank screen then it confirm that port has been forwarded.
It might happens that there is port assignment conflict taken place, so check with “netstat –a –o” and see port 3389 is not being used by other application, if that is the case then change the port.
You can refer following article for more troubleshooting steps (Point 2)
Remote Desktop disconnected or can’t connect to remote computer or Remote Desktop server (Terminal Server) that is running Windows Server 2003
http://support.microsoft.com/kb/2477023
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Using remote desktop web access (RDWEB) with remoteapps and a traditional remote desktop

I configured windows 2012 r2 remote desktop services and remote desktop web access (rdweb) and was able to click the icon on the rdweb page to log on to a remote desktop session. When I published a remoteapp program, the remote desktop icon went away. How
do I get it back? Do I need to publish remote desktop as a remoteapp so users can both use remote apps and log on to a traditional remote desktop session?
thanks in advance for the help

Hi,
You can just publish RDC as RemoteApp and then can connect to the desired remote desktop connection. You can check the below snap.
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

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.

Agent install hang When Install by using remote desktop

Hi All
My Customer has some workstation,that were placed on branch office,occur some problem and he want to re-install.
When he using remote desktop to login/install, ZCM Agent install service will hang on "novell-rm-md-core". he test some times and get the same result.
But he call another admin install agent locally. agent install successfully.
Who have the same experience about remote install by using remote desktop(mstsc) ??
thanks
wyldkao

Originally Posted by wyldkao
Hi All
My Customer has some workstation,that were placed on branch office,occur some problem and he want to re-install.
When he using remote desktop to login/install, ZCM Agent install service will hang on "novell-rm-md-core". he test some times and get the same result.
But he call another admin install agent locally. agent install successfully.
Who have the same experience about remote install by using remote desktop(mstsc) ??
thanks
wyldkao
Windows XP right?
Then you need to install this patch before installing ZCM agent: An application that installs a mirror driver over a Terminal Services session may stop responding on a Windows XP-based computer
Thomas

Report hangs when using Remote Desktop

I am having trouble with Crystal Reports 11. I was wondering if there is a known issue when using it in conjuction with Remote Desktop.
Here is the scenario.
I am using Remote Desktop to connect to a server.
I am running a report using Crystal Reports 11.
The records have already been retrieved (approx. 800,000 records) and is printing - slowly.
It takes around 75 minutes for the report to print 12 pages.
If the Remote Desktop connection is closed, then re-established, the Crystal Reports pops up a message box stating "Not Supported". The pages of data the were previously printed are now blank. (For example: if it was on page 1 of 9+ it will go back to 1 of 1+ and the page will be blank.)
If I use a VPN to connect to the network, then use the Remote Desktop Connection to connect to the server, the connection will periodically disconnect and the re-establish. This does not occur when not using Crystal Reports.
Is there a problem with using Crystal Reports with Remote Desktop? Is there a better way to run my reports remotely?
Thanks for any input.
Ryan

You may be better off posting this in the Crystal Reports Design forum as that team supports issues regarding working with the CR designer:
SAP Crystal Reports
Ludek

Windows 2012 R2 - Remote Desktop Sessions, RemoteFX, GPU, Blue Screen RemoteFX adaptor

Nvidia GPU GRID K1
Host Server - Dell Power edge R720 128 gig RAM 2 Xeon E5-2640v2 2.0GHz, 20M cache 8c
Windows 2012 R2 full installation – Bios and all hardware with latest updates.
Roles - Hyper V and Remote Desktop Virtualization Host
EPT, GPU, WDDM (latest drivers) compatible for RemoteFX and fully up to date.
I have disabled the video adaptor on the motherboard.
I cannot complete with administrative permissions;
dism /online /enable-feature /featurename:Microsoft-Windows-RemoteFX-EmbeddedVideoCap-Setup-Package
Error: 0x800f080c
Feature name Microsoft-Windows-RemoteFX-EmbeddedVidoCap-Setup-Package is unknown
Question 1 - because video card on motherboard disabled, do I still need to complete this command?
VM’s
**I’m not interested in VDI but more Remote Desktop Sessions and the option to ‘pinch and zoom with Windows 8.1 tablets**
VM1 - Windows 2012 R2 configured as generation 1 that is fully patched.
This VM is able to start up and run until I add the new hardware for the RemoteFX Video adaptor from within the Hyper V settings. When I start the VM the server blue screens. I have tried multiple VM’s with 2012 but same thing
If I created the VM as Generation 2 I am able to start the VM but the RemoteFX adaptor doesn’t appear in the device manager. I have read generation 2 isn’t compatible with RemoteFX.
VM2 – *Testing purposes* - Windows 8.1 Enterprise configured as generation 1 that is fully patched.
This VM I am able to start up and run the VDI after the RemoteFX video adaptor is installed, also the correct adaptor appears in the device manager. This seems to at least work correctly but I cannot pinch and zoom and the experience is poor.
GPU summary within the Hyper V settings state there are 4 physical GPU’s all of which can be used with RemoteFX and that 1 virtual machine are using the GPU (Windows 8.1 enterprise VM)
Firewalls off, latest RDP clients
I have read you should be able to use Windows 2012 R2 and we should be able to use the sessions with pinch and zoom but now and then you come across something that tells me different.
Question 2 – I need this to work with Windows 2012 R2 so we can use Remote Desktop Sessions
and the tablets can use pinch and zoom, anyone tell me what I may be doing wrong?

Hi,
Thank you for posting in Windows Server Forum.
As per my research, you need to run the command although video adapter is disabled on motherboard. If you install the RemoteFX cap driver, the integrated video adapter is disabled while the operating system is running.
For more information you can refer beneath article.
1. RemoteFX (with Hyper-V) is a serious business tool. For games.
2. Configure RemoteFX in Hyper-V running Windows Server 2012 with low end GPU
Hope it helps!
Thanks.
Dharmesh Solanki

How to use remote desktop client in mountain lion

How to use remote desktop client in mountain lion.
I want to connect my other system(ubuntu) using mac remote desktop client, But i could not locate remote desktop client in moutain lion.

In Ubuntu 12.xx use Dash to find "Desktop Sharing" and set the preferences, including requiring a password.
Then in Ubu use System Settings > Network to determine your Ubu machine's IP address, such as 192.168.1.13.
On the Mountain Lion Mac do Finder > Go > Connect to Server and enter: vnc://192.168.1.13 or whatever your IP is. Enter the password that you used in the Ubu Desktop Sharing setup, when asked.
On the Ubu machine answer the question that pops up asking for permission to connect. Your Ubu screen will now show up on the Mac, and you can remote control it. Here I am running "Octave" (a math program) on the Ubu machine, remotely.
Works great! BTW, you can do this from an iPad too, using a VNC client such as Mocha VNC Lite. You can even run both remotes simultaneously.
Good luck.

How to enable users to access windows 2012 through remote desktop client on windows XP SP3

Hi I have just installed Windows Server 2012 and trying to give access to the users. The users are on windows XP Pro SP3 remote desktop client (Shell and control version 6.1.7600 with Remote Desktop Protocol 7.0 support).
I have enabled the windows server 2012 remote desktop users through "control panel -> systems and security -> Remote access" for the users. When I try to connect to the windows server as administrator, it is getting connected.
But when I try to connect as other users I get the following message.
"To sign in remotely, you need the right to sign in through Remote Desktop Services. By default members of the Administrators group have this right. If the group you're in does not have the right, or if the right has been removed from the Administrators
group, you need to be granted the right manually."
Is there any other setting to be done to eanble the Remote Desktop for the users.

Hi I have just installed Windows Server 2012 and trying to give access to the users. The users are on windows XP Pro SP3 remote desktop client (Shell and control version 6.1.7600 with Remote Desktop Protocol 7.0 support).
I have enabled the windows server 2012 remote desktop users through "control panel -> systems and security -> Remote access" for the users. When I try to connect to the windows server as administrator, it is getting connected.
But when I try to connect as other users I get the following message.
"To sign in remotely, you need the right to sign in through Remote Desktop Services. By default members of the Administrators group have this right. If the group you're in does not have the right, or if the right has been removed from the Administrators
group, you need to be granted the right manually."
Is there any other setting to be done to eanble the Remote Desktop for the users.
Have you tried adding those users to the "Remote Desktop Users" group? It's in Active Directory Users and Computers and it's a Built-In group. Might want to give that a try ...
- JJ

Installation issue - using a remote server without using remote desktop or citrix

Hello Experts..
We have a client who wants to install SAP Client (SAP 9 PL 11) in their local machines, but connecting to a remote server. They want to avoid connecting through Remote Desktop or Citrix.They already installed SAP clients in local pc's and when they select the server, they already configured it to a server located overseas. We succed on achieve the connection, but the performance is really poor (sometimes it takes about 2 minutes to open a simple menu in SAP).
We ran internet speed tests in the client's office and in the server, and both results were more than satisfactory. But we couldn't come up with a reason for this enviroment works properly..
The question is... Is this kind of enviroment supported by SAP?? Do you know about any alternative to connect from the local PC to a remote server without using remote desktop or citrix??
Thanks in advance...
Raúl Fragueiro

Hi,
I assumed you are using VPN connection right?
In your scenario that is normal since the GUI of SAP B1 is not built for type of connection compare
to SAP ERP GUI.
The only SAP supported type of remote connection is either Terminal Server or Citrix.
In our own scenario we are using Terminal Server and we are very satisfied. We have used
this between to different cities. This is also prevents data corruption cause by intermittent
internet connection.
Hoping you will be convinced of using Terminal Server or Citrix.
By the way, a quick question, why are you hesitant to use RDC or Citrix?
For overview, if your remote requirement is just simple and basic you may use Terminal Server.
The implementation of this is very fast and simple also, what you need is only a license.
If complex and advance features connection requirement connection use Citrix.
For better understanding you may search from the site for the difference of the two.
Thanks.
Regards,
Clint

Connecting to a Windows computer using Remote desktop connection

Similar Messages

Maybe you are looking for