Remote desktop connection to a windows server

Is it possible to connect to a Windows server on an iPad2 the way one can use Remote Desktop Connection on a Mac?

download and install any one of the RDC apps available on the app store.

Similar Messages

  • Remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed

    remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed each time i try to open remote connection to the server,
    does remote desktop connection manager V2.2 not compatible with windows 8.1, and if so, is there are any other compatible versions
    or what's the problem,
    Mahmoud Sabry IT System Engineer

    this issue maybe will be fix by latest version, we still waiting for it
    maybe your issue can be fix using this methods
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/61f218a5-5ef8-49da-a035-90cdd64fc9a0/problem-with-remote-desktop-connection-manager-error-3334?forum=winserverTS
    http://shawn.meunier.com/?p=1#comment-43

  • Remote Desktop Connection imac27" to Windows 7

    Remote Desktop Connection imac27" to Windows 7
    I have a two imac21" & imac 27" local network
    imac21" working fine Remote Desktop connection (imac21" to Window 7/xp/2003r2)  [OS-10.6.7 CPU-2.4Ghz core to Duo, HDD-150GB]
    imac27" could not connect remote desktop connection following message appear  (Remote Desktop 2.1.1)
    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.
    imac27"
    OS-10.6.7
    CPU-3.6 Ghz core to duo
    Ram-4GB
    HDD-1TB

    I haven't tried it with Windows 7 but am having pretty good luck with a Windows XP Professional machine. What I did was just found the IP address to the Windows machine by:
    Command Prompt, type ipconfig and locate the IP address.
    Start RD, enter the IP address of the Windows machine, if the machine has a user name and password you have to enter that and then it works.
    At least that's all I had to do. The key is knowing the IP Address and login and password of the Windows machine.

  • Remote Desktop Connection from a Windows 8.1 laptop to a work PC using Windows 7

    Hi!
    I posted this question in the MS Community forums and they redirected me here... I searched the forums here but didn't find anything that helped with my problem. So here is my original question (posted originally here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-networking/remote-desktop-connection-to-a-work-pc/5fa25045-de24-4a7c-9c8e-caf9ce17e444):
    For the past few weeks, I've been trying to set up a VPN connection to my work PC so I can work from home.
    Work PC runs on Windows 7 (I assume Pro, but I can't confirm at the moment).
    Home laptop runs on Windows 8.1 (the laptop came with Windows 8 already installed, so I assume it's the standard, or Home, edition. I manually upgraded to 8.1).
    Now, after many migraines and sleepless nights fiddling with settings, the VPN connection works. However, what prevents me from completing the connection is Remote Desktop Connection.
    Here's the error I get:
    "Remote Desktop can't find the computer "<computer name>". This might mean that "<computer name>" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to."
    Note:
    - I DO have the correct computer name. I have a working connection to my work PC from my personal desktop PC (running XP), though I sometimes need to travel and a laptop is much more practical to carry around than a PC... ;)
    The VPN Connection Wizard never asked me to enter my destination PC username and password (so my work Windows credentials). Why?
    Any ideas as to why Remote Desktop doesn't want to connect?
    Any suggestions as to what I can try to fix the problem?
    Thank you for all the help!
    Julie

    Are you able to ping the remote system by name? It sounds as though you are connecting to VPN but are unable to resolve the names of the host network. A few things that I would think of:
    If the home system is not on a domain and the work system is, you may need to use the Fully Qualified Domain Name (FQDN). For example, instead of
    computer you would enter computer.domain.com.
    You may want to check if your VPN connection is configured as a default gateway, otherwise if your home and VPN network have the same IP address range you may be experiencing a conflict.
    See the instructions provided here.
    You also may want to check the DNS settings for the VPN connection to ensure that it is finding the DNS server for the remote network and thus is able to resolve the hostname.
    You may want to try connecting Remote Desktop via IP address to determine if the issue is with name resolution (DNS) or connectivity.
    Brandon
    Windows Outreach Team- IT Pro
    The Springboard Series on TechNet

  • Remote desktop connection limit in windows 2003 administration as well as in the mixed environment of windows 2003 and 2008 servers

    RDP protocol i.e. Remote desktop connection is configured to perfrom and manage  software administration of ORACLE application and database servers which runs on windows 2003 server.   Two sessions are allowed on each of these servers for database
    administrators. The question is: 
    a) if network administrators who perform window server administration (50+) are included in
    2 sessions limit or do they manage all these servers through Console Session which is separate from the remote desktop connection limits of 2 sessions.  
    b) How is the 2 sessions  limit prescribed by microsoft (more of a licensing limit) handled in the mix environment of windows 2003 and 2008 server where all these servers are managed on the VMWARE?
    avnish sharma

    Hi Avnish,
    Thank you for posting in Windows Server Forum.
    By default any windows server will provide 2 remote session for administration purpose only. No matter which administrator is accessing that server. If you will connect the console session then 3.One server is accessed by 3 Session (console + Remote +
    Remote). When the particular server reached this limit then any working administrator will receive a message to log out as other user trying to access the session or if we had provided the setting then new user is restricted to login.
    If you want more than 2 remote desktop session than you need to purchase TS\RDS CAL, install TS\RD Licensing role, activate it first and then configure CAL on it. There are 2 types of CAL available (USER & DEVICE). You can purchase CAL according to your
    company requirements.
    Hope it helps to understand!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • TS2072 Remote Desktop Client for MS Windows Server 2003

    I need to be able to access my work server to obtain information form our Windows 2003 Server. We have our product prices and other information on servers and today I use the remote desktop client that comes with Windows 7. I was hoping to find a suitable solution to allow me to use my macbook pro with OSX 10.7.4 Software. Does anyone know how to use OSX to make a remote desktop connection as you would through windows 7. I've seen CoRD and Microsoft did have a version but it's for older versions of OSX. I could run W7 but then I would have to purcase another copy and VM if I decided to run it virtual.
    Thanks

    This is not an Apple Remote Desktop issue  - ARD is Apple's software for managing networked Macs - but CoRD and Microsoft Remote Desktop Connection for Mac should both work with Windows 2003 and both work on Mac OS X 10.7; I have used both on my systems. iTap Mobile RDP is another option, and the one I use daily since I've found it to be faster than either CoRD or Microsoft RDC, though iTap is not free.
    Regards.

  • IS at work told me I need to upggrade my home Macbook Pro operating system , 10.6.8, to a new version in order to remote desktop connect to my windows 7.1 machine at work.  I want to know if I can skip prior upgrades and go to Yosemite or if I have

    Since my work machine was upgraded to a Windows 7.1 pc, I can no longer connect remotely with my Macbook Pro with 10.6.8.  I need to know the most efficient and economical way of doing this and if I can skip versions to get where I need to be.  Supposedly, I need the very latest remote desktop connection software, and it is not compatible with 10.6.8.  Help please.
    Thanks

    Open the Mac App Store and try downloading Yosemite. If you get told it's incompatible, choose About this Mac from the Apple menu, check if the computer has at least a Xeon or Core 2 Duo(not Core Duo) CPU and 2GB of RAM, and if it does, click here and order a download code for Lion 10.7.
    Back up your data and check your applications for compatibility before upgrading. In particular, Mac OS X 10.7 and newer don't support PowerPC programs such as versions of Microsoft Office prior to 2008.
    (119310)

  • Remote Desktop Connection Problem in Windows 7 Home Premium

    First off i have changed most of my computers in the house to static IP addresses. I only configured one static IP address to the router which is my laptop out of the two computers i am working with. Desktop and Laptop. Second I have enabled the Remote Desktop
    on both computers and changed the firewall setting for the computer or the anti virus software. I tried the  netstat -a but dont understand how to read it and when I did i never saw a host or port number for 3389 at all.
    Then finally I went into the registry/regedit to try to see if I had the port number available and port 3389 was not there is just had #"2" in hexadecimal and the file says ehshell.exe which I have no clue what that means. When i click on that it
    does not have the Port Number as the Title nor the port number itself as decimal which should be 3389 as decimal data but instead it has 2 as the data for hexadecimal. I can change the data for the port numbe and change to 3389 but I can't change the title
    from ehshell.exe in the decimal value to PortNumber? The letters on my keyboard just will not coroperate or respond but it will highlight the word and thats it but not make a change to the data value ehshell.exe to something else.
    Is it supposed to do that or what I wonder does anybody have any solutions to this so I can get my Remote Desktop running as soon as possible and no I do not have an Nvidia graphics card. I dont know what the problem is so can somebody please help
    me? I need it for my Windows Server 2008 R2 class next semester and I need to be able to remote to other computers and devices. 

    Hi,
     You can search and download remote desktop client for Win7.
    http://blogs.msdn.com/b/scstr/archive/2012/03/16/download_2d00_remote_2d00_desktop_2d00_client_2d00_rdc_2d00_7_2d00_0_2d00_or_2d00_7_2d00_1_2d00_download_2d00_remote_2d00_desktop_2d00_protocol_2d00_rdp_2d00_7_2d00_0_2d00_or_2d00_7_2d00_1.aspx
    Hope this will help you. 

  • Remote desktop connections not showing in server manager 2012 for one of the session hosts

    This is a three server deployment with one server being the connection broker, gateway, licensing, etc with two session host only servers.
    rdmgr
    rd1
    rd2
    Using the server manager on the rdmgr connection broker (or any other server for that matter) yields only connections from rd2 with nothing from rd1 displaying.  
    Users can connect to rd1 without issue.
    At one point rd1 had the connection broker role installed also but high availability was not setup.  I removed the role hoping it would correct the problem but no luck.
    Any help would be appreciated.  Thanks.

    Hi,
    1. Is rd1 part of a collection?
    2. On rd1, in Computer Management, is the broker's computer account a member of the local RDS Management Servers group?
    3. If you run the below command do you get a list of sessions:
    query user /server:rd1
    4. Any errors/warnings in either the broker's or rd1's event log?
    Broker: Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-SessionBroker
    rd1: Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-SessionBroker-Client
    Both: System and other logs
    -TP

  • Dymo Labelwriter printers not working via Mac Remote Desktop connection into Windows Server 2008

    I'm having a really hard time getting Dymo labelwriters (models 335 turbo and 450 turbo) to work over a remote desktop connection and I'd appreciate any help you can offer.
    To briefly describe the situation, I'm working for a Doctor's office, moving their IT from a remotely-hosted environment where employees connect to their Windows Server 2008 virtual machines (hosted off-site) via Windows 7 machines through Microsoft's remote
    desktop software.
    The new setup will have new servers running in-house instead of remotely and will be based on Apple's Mac Mini machines running Windows 7 for some tasks through Parallels virtualization
    software running directly on each employee's Mac Mini.
    We have 3 of the Dymo 450 Turbo products and one 330 Turbo, each connected directly to a Mac Mini.
    Here's the problem: I have Microsoft's Remote Desktop software running on the Macs natively, connected to each employee's virtual machine on the remote server for now, until the time comes to make the switch to using the new in-house server. The remote desktop
    software works fine - employees are able to connect successfully and access their desktops fine. I have the "Forward Printing Devices" option checked in the Microsoft Remote Desktop app so that the hosted virtual desktops can see the local labelwriters.
    However, the Dymo Label software running on the remote server will not recognize that a labelwriter is present.
    If I go to the Printers and Devices window on the remote server, the labelwriter shows up fine, named "dymo labelwriter 450 turbo (redirected 10)" however running the Dymo Label software gives an error, "Dymo label says no printer connected:
    dymo label printer requires a dymo label printer be installed and connected ..."
    To try and narrow down the cause of the problem, on the same Mac, I ran Windows 7 via Parallels and set up a new remote desktop connection within that Windows VM. Just to be clear, instead of using the RDC software running in the Mac OS, this new connection
    is using a Windows virtual machine running on the same Mac, with the RDC being established from within that Windows VM. Again, I forward printing devices and the labelwriter shows up in Printers and Devices on the remote server as "dymo labelwriter 450
    turbo (redirected 10)" This time, the Dymo Label software recognizes the attached labelwriter and runs fine.
    I'd appreciate any advice you can give on why, as far as the remote server is concerned, a forwarded labelwriter from Microsoft remote desktop running natively on a Mac isn't recognized
    but it is if forwarded from within Windows, bearing in mind that the labelwriter shows up on the remote server in both instances and is called the same name in devices and printers.
    Sorry for the long-winded question. I hope you can help me.

    Hi,
    Thank you for posting in Windows Server Forum.
    Firstly please check whether you have driver capable for your printer with MAC MRD. Also I would like you to check with updated MRD version 8.0.9 for MAC OSX. 
    https://itunes.apple.com/in/app/microsoft-remote-desktop/id715768417?mt=12
    Because as you have commented it can work with windows RDP, so please also try to contact Dymo Labelwriter printer and inquire regarding the issue.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Remote Desktop Connection in Windows 8

    Hi, I can't seem to figure out how to make my local drives available when using the app Remote Desktop Connection on my Windows 8. All the instructions I found on Microsoft do not apply to Windows 8 http://technet.microsoft.com/en-us/library/cc728050(v=ws.10).aspx
    .  Or else I can't find this "Options" tab they're talking about. 

    The program doesn't come up in a window anything like that. It's full screen with only the option to connect to a server. And in settings there are no options that resemble that.
    Hi,
    Could you please snapshot about RDC with us? Mine is shown as below
    Yolanda Zhu
    TechNet Community Support

  • Another Windows 8.1 Remote Desktop Connection Issue

    I want to connect to my PC running Windows 8.1 from my tablet running 8.1. I have allowed RDC in the windows firewall. I open RDC on my tablet and enter my PC computer name, KENSPC, into the Computer field and get "Remote Desktop can't connect to the
    remote computer for one of these reasons:
    1) Remote access to the server is not enabled
    2) The remote computer is turned off
    3) The remote computer is not available on the network.
    I get the same message when I use the IP address for the PC.
    My PC is wired to my router and my tablet is wireless and both use my Microsoft account for credentials. I can ping the PC from the tablet, so I know the tablet can see the PC and I can open files on the PC from the tablet. I have "Allow
    Remote Assistance connections to this computer" turned on. And I have, in fact, had HP help via remote assistance. But nothing I do seems to work. The steps as specified in the Helps do not work. Any help would be appreciated.
    kenfrantz at outlook dot com

    Hi,
    According to your description,we need to know the detail edition of your remote PC.
    You can use a PC running any edition of Windows XP, Windows Vista, and Windows 7, or a PC running Windows 8, Windows RT, Windows 8.1, or Windows RT 8.1 to initiate a connection.
    But the remote PC must be running one of these Windows operating systems:
    Windows 8.1 Pro ,Windows 8.1 Enterprise ,Windows 8 Enterprise ,Windows 8 Pro ,Windows 7 Professional ,Windows 7 Enterprise ,Windows 7 Ultimate ,Windows Vista Business ,Windows Vista Ultimate ,Windows Vista Enterprise ,Windows XP Professional.
    Also, I would like to share the following article with you:
    http://windows.microsoft.com/en-us/windows/remote-desktop-connection-faq#1TC=windows-8
    http://www.microsoft.com/en-us/windows/enterprise/products-and-technologies/windows-8-1/compare/default.aspx
    Hope this helps.
    Regards,
    Kelvin Xu
    TechNet Community Support

  • Remote Desktop Connection Stopped Working when Disconnecting

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

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

  • Remote Desktop Connection Times Out With "Can't Connect" From One Specific Computer Only

    This is an odd one... I manage several servers from this computer. This particular server, 2012 Essentials, won't allow for remote desktop connections to either the server or attached workstations. I can get into the server's remote web page but when I
    attempt a remote desktop connection, it hangs on "Initiating remote connection..." and then times out with the error response that remote desktop can't connect. But... if I attempt the same connections from any other computer, I am able to get in
    and utilize remote desktop. Does this mean that there is a certificate issue with the computer unable to connect and if so, how does one remedy this? Or is it some other issue? I've attempted everything within my technical ability to no avail. Any suggestions
    are greatly appreciated.

    Hi,
    Before going further, would you please let me know the RDC version that used in the problematic computer? Was it the same with other computers?
    Please temporarily disable firewall and then check if this issue can be solved. Based on your current description, it’s hard to say the root reason of this issue.
    So, I suggest that you should check relevant log files and get some clues. It will help us to narrow down and solve your issue.
    Hope this helps.
    Best regards,
    Justin Gu

  • Remote control fails if remote desktop connection has occurred...

    Windows 7 64 bit. ZCM 11.2.
    ZENworks Adaptive Agent Version: 11.2.0.16117
    I enabled remote desktop connections to the Windows 7 PC. I can
    remote control it through ZCM without any problems. But if someone
    makes a remote desktop connection to that PC, I can no longer remote
    control it until after the PC is restarted (haven't tested further to
    see what else will fix it). When I attempt to remote control through
    ZCM, it eventually times out with this error: "Communication error.
    It is likely that some other application is running on the specified
    port."
    Any known fix or workaround for this?
    Thanks,
    Ken

    Lindsey,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://forums.novell.com/

Maybe you are looking for