Remote Desktop Connection no longer works.

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

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

Similar Messages

Remote Desktop Connection no longer working

Hi, I really hope someone can please help me. I just switched from Comcast to FIOS and I can no longer remote desktop to work - so I'm not getting paid until I can get it fixed.
The way that I was doing it before was to connect with a regular Microsoft VPN (I have Windows XP Professional), and then I would use Remote Desktop Connection to log into the work PC. Since I switched to FIOS it no longer works on either my laptop with wireless or my desktop which is connected to the router.
The VPN seems to be connecting OK; it says it is and it is sending/receiving a small bit of data. But when I open the the RDC and try to connect using the PC name it says that the computer cannot be found. I tried to connect to the IP address of it (after connecting through the VPN) and then it says it's found but cannot connect.
There is another location to which I log in using a Cisco VPN and then Remote Desktop - that still works just fine. Nothing at work has changed; everyone else can log in with no problems, including everyone else with FIOS.
I honestly have no ideas at all; this is not my area of expertise to say the least. If anyone could help I would REALLY appreciate it!
Thanks much!
Solved!
Go to Solution.

It is a new Actiontec router.
I finally got it resolved; one of my coworkers suggested checking to make sure that the IP addresses were not in conflict, and they were. So, if anyone else has this problem, what happened was that the new router was assigning IP addresses to my PC's at home in the 192.168.1.x range, which was also the server at work's IP address.
So the really dumbed down version (for people like me!) is to open a command prompt on your desktop, run ipconfig /all, and then it will tell you your internal IP address. (I was getting thrown off because the ROUTER'S IP address, which is the one you can look up online, was different). If the PC's IP is almost the same as the server IP address, then you have to change the IP range on your router to something like 192.168.114.x. There's directions if you google the router specs; I had to change it in three places on the router software; the router IP, the begin range and the end range.
Thank you, jumpin68ny, for starting to help me. Hopefully now this may help someone else!

"remote desktop connection has stopped working" When printing from remote desktop connection

I have been having a issue when using a windows 7 machine. I have Remote Desktop to a session on Windows2008 R2, I am using the local printer resources to redirect the printing. However everytime i try to print it crashes the remote desktop application.
Gives me "remote desktop connection has stopped working." I have 4 other computers connected and printing with no issues what so ever. This only happens when i print. It does print by the way just the application crashes.
-I have also updated the printer drivers to newest possible thru the manufactorer website. The printer is a Brother MFC-8890DW. Windows 2008 R2 is up to date for the RDS server. 3 other machines are able to Remote in and print. The user is able to print using
diffrent machines just not the Windows 7 machine.

Hi,
Happy to hear that you resolved your issue. For another issue which you are facing here trying to provide some suggestion.
As you have commented that you are facing issue with second screen resolution on wide screen. The setting which I am suggesting can only applies when you are using multi-monitor Remote Desktop connections. If you are making Connections using a single
monitor do not use this setting.
So for this you can try to apply “Limit maximum display resolution” setting in group policy, where you can mention the width & height for the screen to display. The setting can be applied on below mentioned
path.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
Meanwhile sharing article with you for more information.
Remote Session Environment
http://technet.microsoft.com/en-us/library/ee791847(v=ws.10).aspx
Hope it helps!
Thanks.

Remote Desktop Connection has stopped working

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

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

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

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

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

Remote Desktop Connection ok on work wireless but not from home

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

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

"Remote Desktop connection has stopped working." problem in Windows 8

here is the event log. Only happens on a few of our servers
Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1
Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505ab405
Exception code: 0xc0000005
Fault offset: 0x0000000000002acd
Faulting process id: 0x13c4
Faulting application start time: 0x01cdbd0d09091fcd
Faulting application path: C:\Windows\System32\mstsc.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 4d923a55-2900-11e2-be73-cc52af4d02a3
Faulting package full name:

Your Ricoh printer drivers cause the crashes:
* Exception Analysis *
*** ERROR: Symbol file could not be found. Defaulted to export symbols for RC5BE130.DLL -
FAULTING_IP:
ntdll!memcpy+21a
000007f8`1fed2acd f30f6f4402f0 movdqu xmm0,xmmword ptr [rdx+rax-10h]
EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 000007f81fed2acd (ntdll!memcpy+0x000000000000021a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000bd9e440c
Attempt to read from address 00000000bd9e440c
DEFAULT_BUCKET_ID: INVALID_POINTER_READ
PROCESS_NAME: mstsc.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000bd9e440c
READ_ADDRESS: 00000000bd9e440c
FOLLOWUP_IP:
RC5BE130!PrinterProperties+2a1ea
00000000`71c4c46a 8b442430 mov eax,dword ptr [rsp+30h]
DETOURED_IMAGE: 1
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
APP: mstsc.exe
FAULTING_THREAD: 0000000000001198
PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ
BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ
LAST_CONTROL_TRANSFER: from 0000000071c4c46a to 000007f81fed2acd
STACK_TEXT:
000000bb`ba9cf248 00000000`71c4c46a : 000000bb`00000040 000000bb`ba9cf618 000000bb`bd7a1458 00000000`00000000 : ntdll!memcpy+0x21a
000000bb`ba9cf250 00000000`71c4bf68 : 000000bb`b45ccc40 000000bb`bae6e7c8 000000bb`bd7a1458 00000000`00000000 : RC5BE130!PrinterProperties+0x2a1ea
000000bb`ba9cf2a0 00000000`71c4b2f9 : 000000bb`bd7a1458 000000bb`bd7a1458 00000000`00000000 00000000`71c10000 : RC5BE130!PrinterProperties+0x29ce8
000000bb`ba9cf380 00000000`71c2a08a : 000000bb`bd7a1458 000000bb`bd7a1458 00000000`00000000 00000000`02000000 : RC5BE130!PrinterProperties+0x29079
000000bb`ba9cf3d0 00000000`71c283de : 000000bb`ba9cf618 000000bb`badfb050 000000bb`00000000 00650074`00730079 : RC5BE130!PrinterProperties+0x7e0a
000000bb`ba9cf440 00000000`71c2209d : 00000000`00000000 000000bb`ba9cf618 00007989`001a0019 000007f8`169fafa0 : RC5BE130!PrinterProperties+0x615e
000000bb`ba9cf550 000007f8`169e5ea0 : 00000000`00000000 000000bb`ba9cf618 000000bb`bd7a1458 000000bb`bd7a1458 : RC5BE130!DrvDocumentPropertySheets+0x1d
000000bb`ba9cf580 000007f8`169e6b9f : 000000bb`00000000 000000bb`ba9cf670 00000000`00000000 00000000`00000004 : winspool!DocumentPropertySheets+0xb0
000000bb`ba9cf5f0 000007f8`169e6aa5 : 00000000`00000002 000007f8`ffffffff 00000000`00000000 00000000`00000000 : winspool!DocumentPropertiesWNative+0xcf
000000bb`ba9cf680 000007ff`f4f3dc32 : 00000000`00000000 000000bb`b93f3990 00000000`000004d4 000000bb`ba9cf790 : winspool!DocumentPropertiesW+0x7d
000000bb`ba9cf6e0 000007ff`f4f9a09b : 00000000`00000000 000000bb`ba9cf7b0 00000000`00000000 000000bb`b93c7530 : mstscax!CTSClientPrintDriver::DocumentPropertiesW+0x37e
000000bb`ba9cf730 000007ff`f4f994d4 : 000000bb`b93c7530 000007f8`00000000 00000000`00000000 000000bb`00000000 : mstscax!CStubITS_PrintDriver<ITS_PrintDriver>::Invoke_DocumentPropertiesW+0x12b
000000bb`ba9cf7e0 000007ff`f4f8ff0c : 000000bb`b93c7530 000000bb`b93f29e0 000000bb`b94060d0 00000000`00000000 : mstscax!CStubITS_PrintDriver<ITS_PrintDriver>::Dispatch_Invoke+0x68
000000bb`ba9cf840 000007ff`f4f95a84 : 000000bb`b93c7530 00000000`00000000 000000bb`b93c7530 000000bb`b93cccc0 : mstscax!CStub<IMMClientNotifications>::Invoke+0x64
000000bb`ba9cf8b0 000007ff`f4f94310 : 000000bb`b93cccc0 000000bb`b93c7530 000000bb`ba9cf930 000000bb`b693b3c0 : mstscax!CRIMStreamStub::OnDataReceived+0x98
000000bb`ba9cf8e0 000007ff`f4f18c5a : 000000bb`b93cccc0 000000bb`b93f4cd8 000000bb`b93f4b10 000000bb`b93f4cd8 : mstscax!CRIMObjManager::OnDataReceived+0x150
000000bb`ba9cf960 000007ff`f4f20132 : 000000bb`b93c6908 00000000`00000000 000000bb`b93c6908 00000000`00000e28 : mstscax!CDynVCChannel::HandleAsyncCall+0x12e
000000bb`ba9cf9b0 000007ff`f4ed94e7 : 000000bb`b93f36a0 000000bb`b93c68c0 00000000`00000000 000000bb`b93f40d0 : mstscax!CDynVCThreadPoolThread::ThreadPoolEntry+0x102
000000bb`ba9cfa00 000007ff`f4c5aba9 : 000000bb`b7ddeb58 00000000`00000000 000007ff`f4b50000 00000000`00000000 : mstscax!CTSThread::TSStaticThreadEntry+0x33b
000000bb`ba9cfa90 000007f8`1e41167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!PAL_System_Win32_ThreadProcWrapper+0x25
000000bb`ba9cfac0 000007f8`1fef3501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
000000bb`ba9cfaf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: rc5be130!PrinterProperties+2a1ea
FOLLOWUP_NAME: wintriag
MODULE_NAME: RC5BE130
IMAGE_NAME: RC5BE130.DLL
DEBUG_FLR_IMAGE_TIMESTAMP: 4bd67428
STACK_COMMAND: ~18s; .ecxr ; kb
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_RC5BE130.DLL!PrinterProperties
BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_READ_DETOURED_rc5be130!PrinterProperties+2a1ea
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/ntdll_dll/6_2_9200_16420/505ab405/c0000005/00002acd.htm?Retriage=1
Followup: wintriag
0:018> lmvm RC5BE130
start end module name
00000000`71b00000 00000000`71cdd000 RC5BE130 (export symbols) RC5BE130.DLL
Loaded symbol image file: RC5BE130.DLL
Image path: C:\Windows\System32\spool\drivers\x64\3\RC5BE130.DLL
Image name: RC5BE130.DLL
Timestamp: Tue Apr 27 07:20:40 2010 (4BD67428)
CheckSum: 001E2D52
ImageSize: 001DD000
File version: 0.3.0.0
Product version: 1.0.0.0
File flags: 1 (Mask 3F) Debug
File OS: 40004 NT Win32
File type: 2.1 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: RICOH CO., LTD.
ProductName: RICOH RPCS Printer Driver
InternalName: RC5BE130.DLL
OriginalFilename: RC5BE130.DLL
ProductVersion: 1.0.0
FileVersion: 7.6.9
FileDescription: RICOH RPCS Printer Driver
LegalCopyright: Copyright(C) 1999-2010 RICOH CO., LTD.
so check for a printer driver update and what you can also do is to avoid mapping your printer to the Remote Desktop. Maybe this also fixes the issue.
"A programmer is just a tool which converts caffeine into code"

Remote Desktop Connection not working

I am able to remote desktop connect to my home computer from work; however, I can't remote desktop connect to my work comptuer and server. I believed it has something to do with my Linksys E3000 access point settings but I'm not sure where to look for and verify. I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network. I also VPNP in to my work place so that it has the same IP address as at work and still, remote desktop connection from home to work is not working. Any suggestion is much appreciated.

thebluemamba_24 wrote:
Connecting from home to your remote desktop server has nothing to do with your router. Certain ports are needed to be opened from the server’s end in order to host an application. Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work. In case it will not work, then contact your IT guy.
If you read my previous post it said:
"I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network."
I think my above statement answers your question of "Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work." However, your statement prompts me think of something else. What I have tried is bring my laptop to work and tried connect via RDC to the server and it works but it just not working when trying at home. What I have not done is instead of brining my laptop to work and try RDC there, perhaps I should I try it on a friend's or relative's network and see if I can do RDC to my server at work. If this does not work as well, then, could it be that at work there is something something outside RDC coming? But even if this is so, why can't VPN work?

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

Trouble with Remote Desktop Connection to work PC

Note that I am trying to log into my work PC from my mac at home. My company recently announced we could log in from home with a mac into our work PC. they can't get it to work so I thought I'd try here. We use a mobile site on Safari to obtain a network connection - it launches a program called network connection and I appear to have that network connection (although very little data is being sent and received). I am then supposed to launch a program called Remote Desktop Connection (this program was installed from steps I ran through the first time I logged in through the mobile site, it is version 1.0.3), but when I do, it will not connect and the error message is that remote connection is not enabled, network is too busy, etc). However, the guys at the support desk using PCs can log into my work computer. The only info that's mandatory to input on the Remote Desktop Connection is my work computer name. I don't think this is the issue, because if I purposefully use an incorrect name for my work computer, the error message is different, stating it can't find my (work) computer. I also installed the most recent version of Java for 10.3.x The only issues I can think of are a) this won't work with 10.3.9, although I doubt this is it as the Remote Desktop Connection program appears a few years old, OR there is some firewall issue on my mac. I doubt that this is it, as I assume the mac's firewall protections are to prevent others from remotely logging into my mac, not prevent me from using my mac to remotely log into my work PC. Also, I don't use any third party firewall or other protection stuff on my mac other than whatever comes stock. if you've read this far, thanks, and any comments appreciated! am trying to log in using my dual 1.8 g5 with 1.5g memory using 10.3.9

Are you by any chance with a major retailer? My company just did the same thing. We used to connect via a Virtual Drive connection, but they took that away and went to RDC.
I had problems at first logging in as well. It was acting as if my password was wrong, but I knew that wasn't the case. I finally typed the password in the UserName area and found the problem!
I had two special Characters followed by a capital letter. For instance !@Axxxxxxxx. When I typed the password, I would push and hold the 'shift' key for the first three letters. When typing that in the "user name" field, it showed as !2axxxxxxx. You have to release the 'shift' key and repress it for each letter.
I hope this helps you!

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 to VM does not work after sysprep

Hello altogether.
Often asked, but never answered with an applicable solution!
What shall
we
do if
we
get no access to a Azure VM via Remote Desktop
Connection?
Everything went well: access to the VM via RDC was working perfectly!
Then
the idea came into
our
mind to create an image of the VM by use of the Azure Management Portal.
We
found that
we
had to apply “sysprep”
on the VM.
We
did it.
Then we did not take the image and decided to go on with the VM.
But if we start the VM we get no access via RDC!
We tried to find a solution by reviewing the already published contributions by other Azure
users. But none of the replies marked as answered supply with a qualified solution.
So can one provide a really applicable solution to us on how to arrange the further use of the VM?
Thank you in advance.

There is an issue right now where the VM may start unexpectedly after you have run sysprep and selected the shutdown option (which is normally what you should do).
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/fafb9ee6-1e57-46ba-8440-27467ad986cf/image-capture-issue-vm-unexpectedly-started-after-guestinitiated-shutdown?forum=WAVirtualMachinesforWindows
But regardless of that issue - you can't use that deployed instance of the VM after you've run sysprep on it. It needs to stay shutdown, then you select Capture to create an image from it.
If you start it back up, either intentionally, or it is started unexpectedly because of the issue above, it will be sitting at the first interactive screen of setup. RDP is not working at that point, and since there is no console access to an Azure VM, there
is no way to get past that prompt.
For other scenarios, you might be able to attach the OS disk of that VM as a data disk to another VM, and while you could do that in this case too, there is no supported method for disabling sysprep at that stage of setup.
So while you could attach it to another VM to get data off of it (you would have to remove the VM first), the VHD is no longer in a supported state to use as a VM itself.
Thanks,
Craig

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)

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 not working in windows 7 Pro x64 bit sp1 3389 port not working

i have still facing same problem in last two week in my system RDC not working . i have installed in my system windows 7 x64 bit Pro sp1 then i check 3389 port working or not in my system use the command netstat -a -o command in
command prompt but this is my bad luck its not woking in my machine after i have decide to change RDC listening port via registry i have change it 3389 to 3391 after restart my system, and
after again testing using same command but no any change again rdc not listening . After i have search this issue on search engine google bing and microsoft , i have found more solutions but i have try one
uninstalled two microsoft updates first is kb KB2621440 second is KB2667402 and after again restart my system and again installed KB 2667402 But not change i have already enabled Remote Desktop connection in windows 7 and select the option
any version computer running , i have try three and four time enable disable remote desktop connection in my machine . but not change i have all windows firewall disable and uninstalled anti virus they intalled in my machine , and using the Mcafee
stinger tools to scan my machine to remove virus but stinger is not found any thread in system. ihave already run this command in my system sfc /scannow Please Can you help me to fix this issue.

Hi,
When you try to start the Remote Destop Connection, what errors it showed out?
Could the other PCs connect this PC with the RDC?
So you have read this blog?
RDP connections might fail due to a problem with KB2621440 - MS12-020
Did you reinstalled the KB2621440?
Besides, did you follow this guide to enable the RDC connection?
Connect to another computer using Remote Desktop Connection
And also this guide?
Why can’t I connect using Remote Desktop Connection?
Please take a check with those settings again.
Best regards
Michael Shao
TechNet Community Support

Remote Desktop Connection no longer works.

Similar Messages

Maybe you are looking for