Remote Desktop Connection keeps disconnecting

I have BT Hub 3 (recently upgraded to Broadband Unlimited at the end of Jan 2015).
Up until recently I was able to Remote Desktop into my work computer (via VPN tunnel) with no problems at all.
Around March 6th, I began to experience problems with the Remote Desktop Connect (RDP), in that it now makes an initial connection and then disconnects (typically within a few seconds, occasionally after a couple of minutes).
It will then cycle through a number of reconnection attempts, all with the same result, before it finally drops altogether with the message:
'The Remote Desktop Services Session has ended. Connection to the remote computer was lost, possibly to network connectivity problems'.
I have tried restoring both machines back to a date when i know the connection was working - no joy. I've also tried deleting an re-creating now VPN and RDP connections - no joy. I've researched online and tried various other things, but still have the same problem.
I've tried connecting using a laptop (via my wirelss connection) with the same result. My manager has RDP'd in from his home machines and has had no problem at all.
This leads me to consider whether the problem is with the router/BT Hub itself. I've tried the online diagnostic tools with no resolution to this problem.
Has anyone else experienced the same problem?

Oh well, I suppose that after more than 2 months of frustration with this issue, the BTCare Community is unable to help me.
I can be fairly sure that it's not my machine as it's also happened using a laptop, plus I've even reset my PC right back to its original factory state just to sure that nothing had become corrupted.
The network guys where I work have also looked at this and can find nothing at that end to cause this problem.
I've even borrowed another BT Hub and tried it through that - same problem.
So where does the answer lie? VPN issue? I've tried other VPN options - same problem. RDP problem? I've practically exhausted the list of suggested solutions that can be found by trawling the internet.
I even upgraded the broadband cable to replace the cheap old thing that has been working perfectly well in terms of broadband, again, to eliminate this as a possibility. Now I'm stumped.
To me, it looks like the problem lies between my router and the workplace network, i.e. a physical problem among the miles of lines connecting the two. Of course I don't want to shell out for a BT engineer to come out to investigate, so I thought that the combined wisdom of this community may have been able to help.
Sadly not.

Similar Messages

Remote Desktop Connection frequently disconnects

Recently that office changed their network infrastructure. Since that change the user has not been able to stay connected to RDP for more than 20 minutes or so. Sometimes it will only take a second to reconnect, other times several tries. Sometimes they will be completely kicked off the internet and need to log back into the VPN then RDP again.
What was this change?

I have a remote user who works in a sort of collaboration office. They connect to our network using a Sonicwall VPN and then RDP onto a terminal server.Recently that office changed their network infrastructure. Since that change the user has not been able to stay connected to RDP for more than 20 minutes or so. Sometimes it will only take a second to reconnect, other times several tries. Sometimes they will be completely kicked off the internet and need to log back into the VPN then RDP again.The user did not have this issue before the change. I have other remote users, who work in other offices and work from home. None have had this issue.The user is able to log into the terminal server within our network and stay connected with no issues.Our VPN does DHCP lease. The host is set to automatically obtain an IP, and when they log into...
This topic first appeared in the Spiceworks Community

Remote desktop connects, black screen, disconnects after a few seconds

I have several servers running Windows Server 2012 R2. These servers are used for testing, and are members of a domain which has two DCs, each of which are running DNS Server.
Yesterday I noticed one of the servers was having an issue with its remote desktop connection. If I try remoting into this machine, it connects to a black screen, sits there for 2-3 seconds and then promptly disconnects. No error message is given. I tried
this from a couple different Windows 7 machines, and got the same result. I tried from my wife's iMac, which runs Jump Desktop, and too was met with the same result.
I can, however, remote into this machine via RDP from my work-issued laptop, which is running Windows 8. However, I cannot remote into the problem machine via Remote Desktop Connection from one of the 2012 R2 servers--I am met with the same result as the
other machines: connect, black screen for 2-3 seconds, disconnect without error.
I can remote into all of the other 2012 R2 servers without issue from any machine, including the iMac. I am experiencing this problem on one server only.
Since it is a test server, I reinstalled Windows from scratch this morning. This meant formatting the SSD and wiping everything out. I reinstalled the drivers, joined the server back to the domain and installed all of the updates available from Windows Update.
And rebooted. And yet, the problem persists!
I tried troubleshooting the "usual suspects," like turning off Windows Firewall, disabling antivirus software (currently none installed), disabling IPv6, setting a static IP instead of using DHCP, etc. I did notice the network adapter said it was
on a Network, not a Domain Network. I corrected DNS settings, and the network reidentified itself as being on the ParietalBone.net network. And yet, the problem persists. Remote Desktop to this server still yields a black screen for 2-3 seconds, followed by
a disconnect--EXCEPT from the aforementioned Windows 8 machine.
I looked in the TerminalServices-LocalSessionManager log on the offending server, and there are no errors. I only see repeated entries that say "Session X has been disconnected, reason code 12," where X is 1 or 2. On a couple occasions, the reason
code is 11. But I don't see any errors indicating a breakdown in security negotiation.
Without any robust logs or debug details, I'm at a loss of where to look for a solution.

I am cautiously optimistic that this may have been resolved.
The network card in the computer was only a 10/100 built-in card, so I replaced it with a 1Gbps card. Interestingly, this did NOT resolve the issue. I ran netsh to check on the state of the chimney offload, but it was already disabled.
In the network card properties, I changed the link speed and duplex from automatic to 1Gbps full, re-ran "netsh int tcp set global chimney=disabled" and rebooted. The problem persisted.
And so I went to the network card properties and set IPv4 Checksum Offload, Large Send Offload (three of these -- IPv4, v2 IPv4 and v2IPv6) and TCP Checksum Offload (IPv4 and IPv6) to Disabled. Jumbo Frames were also disabled. I rebooted again.
After the subsequent reboot, I was able to connect to this Server from machines that previously gave me difficulty. The only machine I haven't been able to test today (I'm in the office) is my wife's iMac, which is at home. However, I was able to bring this
server up via Jump Desktop on my iPad, so I'm suspecting that perhaps one of the offload options was to blame. I'm not sure why this would allow me to connect from some machines but not others. And as noted above, I have many other machines running Server
2012 R2 and they are NOT experiencing this problem. And I've not done any tinkering with network settings on any of them, so their chimney and offload settings are all in the default configuration.
Regarding the other items -- NIC team, virtual machine, etc. -- there was no NIC team, no SRIOV and no RDMA involved.
I had to turn IPv6 off on this machine, and only on this machine, because having it enabled was causing a lot more problems. DNS registration would keep failing, it couldn't pull Group Policy, it couldn't get time sync with the DC, etc. The servers are all
set up with static IPv4 addresses. The router supports IPv6 but I'm not actually using it, so disabling IPv6 wasn't a concern to me.

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 Windows 8 PC from other computers crashing

Hi all.
Was hoping someone would be able to help me with an issue I'm having.
I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
never will. The computer has a single user profile that has full administrator rights.
I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me.
The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
the connection or do anything. I have to restart the computer from then to be able to use it again.
I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
to continue using it. Dead end there, it seems.
The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck.
If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
you think I can provide anything.
Thanks in advance!
rugbyreff

The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet
Hi Brandon
Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
this still hasn't helped.
If you have any other ideas I'd be very glad to hear them!
rrugbyreff
"If it's worth doing, it's worth overdoing" -- MythBusters

HP LaserJet Pro MFP M127fn and Remote Desktop Connection

So, my pc operates on Win7-64bit. I use Remote Desktop Connection to log in to the company server, running on MS Server 2008. I purchased the HP MFP M127fn today after confirming that it is compatible with both OS listed above. I successfully installed it directly to the server via usb cord - to make sure the correct drivers downloaded to the server. I was able to test-print and print from an app while physically connected to the server. I then disconnected the printer from the server and successfully connected it to my local pc. I can test-print and print from an app on my desktop. When connect to the server via RDC, it recognizes the MFP M127fn as my default printer, and sends a print job to my local pc. I can see the job in the server print queue, I can see the print job in queue on my desktop....it spools, then says it prints, however no actual print job ever materializes.
If I select to print to the MFP M127fn fax from the server, it will open the fax window on my desktop, allow me to enter a phone number, and will dial out and send the fax. So, that driver is functioning properly.
So, my question is this: If the printer and fax claim to be successfully installed, why do I not get the print job that is sent via the server and appears in my local print queue? I get no error, either on the server side or the local desktop. They both truly think the job has printed.....but no paper ever comes out.
Our company has used several other HP printers over the years with this same set-up and have never had a problem until now. The last one was also an HP MFP - the CM1312. So, I am now completely stumped by this. I called HP support and was routed through 4 different areas before I was told that no one had a clue what the problem might be. I then called the Easy-Tech desk at Staples, where I bought the printer, and was told that it was most-likely a hardware issue and I should return the printer to swap it out for another one. If nothing would print at all, I would agree it's hardware. But, as I can print locally, I'm more-inclined to think it's driver-related......any suggestions?

Hi,
The M127fn uses the PCLmS printing language which is a lightweight printing language, a such is not supported for RDP printing.
As a reference you may find the following socument about Citrix, Terminal Services and RDP Printing, as you may find listed the M127 is not supported for a such:
http://h20195.www2.hp.com/v2/GetDocument.aspx?docname=4aa0-8465enw&404m=secure-erc
That is clearly not an harware issue, however I suggest returning the printer and replacing it with a different model which better feet such a task.
The M225dn as an example uses a PCL 6 print driver and should provide a better feet for RDP printing using HP UPD.
Regards,
Shlomi
Say thanks by clicking the Kudos thumb up in the post.
If my post resolve your problem please mark it as an Accepted Solution

Can 1 instance of Windows 8.1 ENTERPRISE host multiple Remote Desktop connections?

I am shopping for the components for building a machine with fair, high-performance hardware. I have Windows 8.1 Professional. I wanted to know if either Windows 8.1 Professional or Windows 8.1 Enterprise can support multiple remote connections
from users outside the local network. For example, my brother is based in San Diego, CA and has an underpowered laptop. Is there any way to make a remote connection over that much distance, from San Diego to Northern Virginia, from a RDP client running Windows
8.1 Professional to a RDP "server" Windows 8.1 Professional/Enterprise machine, and run a modern, single- or multiplayer- game over smoothly that connection? At the very least, is it possible to run common
apps (e.g. Microsoft Office 2013 IE 11, Adobe Acrobat XI) smoothly on a Windows 8.1 Pro RDP client connected to a Windows 8.1 RDP "server" located 2250+ miles away?
Would upgrading my installation from Professional to Enterprise improve the responsiveness and display quality for my remote users?
I know Windows Server R2 2012 has features specific for handling remote connections, but I am trying to keep a Windows 8.1 user experience. Still, if anyone can show some evidence that Windows Server 2012 R2 Remote Desktop Services (RDS) improves display
and responsiveness over long-distances for remote (RDS) connections, then I will shop for Windows Server 2012 R2 Standard instead. The huge drawback of Windows Server 2012 R2 Standard CALs is the enormous cost to enable 3-5
remote connections for family, non-commercial use.
Has anyone attempted to host long-distance remote access, non-commercially, for 3-5 connections? Has it worked well? What, in general, is required?
T. Webster

Hi,
It depends on the quality of the network connection to run the software smoothly throuth RDP. And I don't think the quality would be better if you upgrade to Windows 8.1 Enterprise.
Windows 8.1 allow only one session of RDP, the Remote Desktop Server in Windows other than the Windows Server edition has a limitation to allow only one concurrent user per session by default, i.e. if someone remotely connects to the computer over RDP then
whoever was logged in at that moment will be automatically logged off, even if that user is physically present at the computer. This is by design.
Regarding more information about RDP, please take a look at the following articles:
Remote Desktop app help
Remote Desktop Connection: frequently asked questions
Best regards
Michael Shao
TechNet Community Support

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

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

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

Remote Desktop Connection

I'm running bootcamp Windows 8 on a MacBook Pro and a MacMini (on home network).
I have them set up for remote access. At home on the same network, I can remote desktop to the MacMini using the local IP address with no problems.
I then wanted to access it from an external network so I enabled the default 3389 port in my firewall settings and set up this port to my MacMini in my router settings. I reserved the IP address for the MacMini as well.
I was able to successfully connect from an external network at least once but once my external IP address changed, I was no longer able to get it to work after updating the IP address. The computer is on because I can access it using TeamViewer and I use
that to check the current IP address of the MacMini when I'm trying to connect.
To get around the dynamic IP problem, I signed up for a dyndns account and set up a host name. I can use a port check and the host name ***.dyn-o-saur.com resolves to the correct IP address (i.e., the whatismyip.com result on the MacMini).
I have tried changing the port to 8888 in case TeamViewer or some other application was using 3389 but that hasn't fixed the problem either. I've checked the port (using http://www.t1shopper.com/tools/port-scan/) and I get this message:
***.dyn-o-saur.com is responding on port 8888 (ddi-tcp-1).
I have the dynUpdater v5.0.1 installed on both computers and it says the host is inactive (however since the hostname is resolving properly I assume this means the app is not working but it shouldn't be affecting my ability to connect?).
Some help please?

Hi,
Firstly, we need to refer to this article and configure the settings.
Allow Remote Desktop connections from outside your home network
http://windows.microsoft.com/en-us/windows7/allow-remote-desktop-connections-from-outside-your-home-network
From you description, I think you have done this part. However, please keep to use port 3389 and make sure that you can RDP to your Windows 8 via the
Public IP address from Internet.
Then, as you have dynamic public IP address, we need some way to track the changes of your public IP address. Yes, dyndns is one of the methods, you need to make sure that it
can resolve the host name you registered to the correct Public IP address so that you can always RDP you Windows 8 via host name when you outside your home.
If you need assistance about dyndns, please contact their support.
Thanks.
Jeremy Wu
TechNet Community Support

Remote desktop connection problem windows 8

Hi everybody,
I hope you can help us. We run a software package that uses a remote desktop connection. When the program is minimised for more than a couple of minutes, the connection disconnects and takes a while to reconnect. We've been in touch with the guys that run
the program and they've said that there's no problem on their end and that it must be on our end. It's happening with all three computers at one location and it's not happening with our two computers in our other location.
I've been in touch with the online support guys in microsoft and they couldn't help. So I'm wondering if any of you can help us (in laymans terms please!).
All our computers run Windows 8.
Thanks in advance.

Hi,
Thank you for your posting in Windows Server Forum.
Yes, you can check with 2 different settings. 1) By Collection properties (Server 2012\R2) and RDP-Tcp connection under Remote Desktop Service Manager (Server 2008 R2). 2) The other setting is related to GPO (Set time
limit for active but idle Remote Desktop Services sessions) as following path.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
User Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
You can check below link (Configuration 1) for more information.
[Forum FAQ] Restrict number of Active Sessions in RDS 2012 and 2012 R2
http://social.technet.microsoft.com/Forums/en-US/00c2252b-8ec0-489f-8da2-07a434a9b5a2/forum-faq-restrict-number-of-active-sessions-in-rds-2012-and-2012-r2?forum=winserverTS
Hope it helps!
Thanks.
Dharmesh Solanki

Remote Desktop Connection stop working after upgrade from 10.5.8 to 10.6.1

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

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

Installed the RDS 2012 Server License per user CAL (5pcs) after not allow over two users remote desktop connection problem

I have successfully to installed the RDS 2012 Server R2 per user CAL (5pcs) Open License after is found not allow over two users to remote desktop connection on this Server problem, I try to uninstall the license and then (internet on-line & telephone
call Microsoft Activate Center get the activate key) to reinstall is still same of the result on below problem.
Select a user disconnect so that you can sign in.
There are too many users signed in
User1 Active
User2 Active
() Force disconnect of the user

Hi,
In addition you can also refer following article for RDL configuration.
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
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]

Remote Desktop Connection - viewing screen

Hi, I just installed Remote Desktop Connection on my Imac at home so I can access my work PC. Everything works fine but my image I view is only about 5" x 6". It seems like a waste of the 27" screen. Does anyone know how I can increase the size of this so I can access the whole screen?
Thanks

Hi and welcome to Discussions,
personally I use Screen Sharing for accessing my work PC but I think this also applies to RDC.
What you get on your iMac is the screen resolution of your work PC when using RDC.
Since the 27" iMac has such a high resolution natively (2560x1440) the RDC window might be quite small when your work PC uses a resolution of 1280x1024 (as an example).
You might try to raise the resolution of your Work PC (should be possible through RDC when the resolution change on your Work PC is appliable without a restart of it) but eventually might come to a barrier when reaching the highest resolution possible on your Work PC.
Also keep in mind that the higher the resolution of the Work PC is, the more data has to be transfered which might slow down your RDC connection to a crawl.
Regards
Stefan

Trouble Printing to Network Printer via Remote Desktop Connection

Specs:
Macbook Pro, early 2013,
Mavericks (10.9.2),
Microsoft Remote Desktop Connection v.8.0.5 (latest),
Connecting to Windows Server 2008 standard
Printer, HP LaserJet P2035n, connected via the network
When on the Mac connected to the server, the printers from the Mac are redirected so you're supposed to be able to print from Remote Desktop to the HP printer. However, when you select something to print, the job goes to the print and keeps printing over and over and over again until you cancel the print job, which it usually allows you to do, or turn off the printer, which you have to do when it won't let you cancel the job.
Any advice on how to get the printer connection running normally?

What you haven't told us is what method you use to connect/setup the printer on Windows. There are two ways - Bonjour for Windows (free software from Apple), and TCP/IP raw port 9100. If you have a problem using one, try the other.

Remote Desktop Connection for Mac to Windows - logout error

Hello
I'm trying to use Remote Desktop Connection (RDC) to get from my Mac into a MacMini running Windows XP Professional. I can log into the Windows computer, but once I put in my password and click OK, it logs out of the Windows machine. Is there some sort of sharing preference or configuration that I'm missing that's making this happen?
I want to be able to use RDC to access the Windows machine and keep everything up still on the Windows machine.
Thanks

Since RDC is not an Apple product, you'll probably want to use a forum dedicated to Microsoft's Mac products such as <http://www.microsoft.com/mac/community/community.aspx?pid=newsgroups> rather than an Apple forum
Be sure to search the forum first in case someone has already had a similar question answered.

Remote Desktop Connection keeps disconnecting

Similar Messages

Maybe you are looking for