Remote Desktop Connection Drops when opening a large file or Transferring a large file

I am running a Dell R720 Windows 2008 R2 Server. When I open a Large PDF or transfer a large file to the server, the server drops the remote desktop connection. I do not see any errors and no events are reported. I can access the server via
iDRAC 7 enterprise and the server is still up and functioning properly; however, the remote desktop connection can only be restored after the server is rebooted. I have read the following article below do not see any conflicts.
http://support.microsoft.com/kb/2477133/en-us
That said, the issue happens when:
1. opening a large PDF
2. Using a UNC path to transfer a large file
3. Using Hyper-V to import a .VHD (another large file)
Any help is appreciated - Thanks in advance

Hi,
Thank you for posting in Windows Server Forum.
Does this issue facing for single user or multiple users?
Have you tried on other system? IS it, facing same issue.
From description it seems network issue, please check whether there is any drop for network connection or it works on low bandwidth. You need to see there is no loss from bandwidth perspective. There are other certain reason which can drop the connection or
performance as remote desktop works on many different points.
For try you can autotune disable and check with following command.
netsh interface tcp set global autotuning=disabled
To renable follow beneath command
netsh interface tcp set global autotuninglevel=normal
When you are remote desktop to the remote server, please set the connection speed accordingly to optimize performance and might it will resolve your case of dropping connection.
More information.
Announcing the Remote Desktop Protocol Performance Improvements in Windows Server 2008 R2 and Windows 7 white paper
http://blogs.msdn.com/b/rds/archive/2010/02/05/announcing-the-remote-desktop-protocol-performance-improvements-in-windows-server-2008-r2-and-windows-7-white-paper.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Similar Messages

Remote Desktop Connection dropping

I have a RDC connection into a remote server that is on a VPN tunnel between 2 pixes.
When I have this access-list in it does not drop.
access-list 111 extended permit ip 10.10.128.0 255.255.255.0 192.9.20.0 255.255.255.0
but when I tried to tighten my access-list to
access-list 111 extended permit ip host 10.10.128.183 192.9.20.0 255.255.255.0 so that only 1 host can access the remote network the connection drops every couple of minutes and then re-establishes itself.
Any ideas?
Thanks.

Is access-list 111 used for the crypto map, or is it used for the ip access-group? If it's used for the crypto map, then did you change the access-list parameters on both sides of the tunnel?

Remote desktop connection unable to start, window stalls when opens RDC, any tips

remote desktop connection does not open, when rdc starts it stalls and can not press any button.
any ideas on how to fix?

Since this question is about a Microsoft product, you might have more luck getting suggestions if you ask in Microsoft's own forums. This forum is for Apple Remote Desktop issues and questions and so probably not the place where you'll be most likely to get assistance with this problem.
Good luck.

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

When I am using remote desktop connection from PC1 to PC2 and if Firefox has opened before remote connection I will see only black screen in Firefox window on PC2. Os WinXP prof Sp3. If I run FF on PC2 remotely, FF works perfectly.

I am using an integrated feature Remote Desktop connection on WinXP without any additional software. Connection through internal LAN, so speed is very fast.

Hi,
You can try to toggle the various options in the '''Experience''' tab of RD.

Remote Desktop Connection Manager can only open 6 sessions at a time on Server 2012

I am only able to open, and view thumbnails, for a maximum of 6 RDP sessions on my Server 2012 box at a time in Remote Desktop Connection Manager (RDCM). If I add more sessions I just get a variety of connection errors for the additional sessions. If I activate
a 7th session one of the existing 6 sessions goes off-line with a connection error message. Sometimes the error says 3334, sometimes the error says 0x8345000E, and sometimes it just says there is a connection error.
I have checked Group Policy on the server to ensure I don't have any settings restricting the number of RDP sessions.
In fact, I will often have 30 or 40 RDP simultaneous sessions opened, I am just not able to view them all in RDCM. I have seen reviews of RDCM with screenshots showing dozens of thumbnails so it seems to be something that's possible to do.
Are there any settings I should make on the server to allow RDCM to connect to more than 6 simultaneous RDP sessions?
Just to be clear, all these RDP sessions are running on the same server. Also, I am just using the trial license for Server 2012 and Remote Desktop Services right now. I don't think that should have an impact, but I wanted to be thorough.

Thanks Jakub for "corflags" info.
Unfortunatelly it doesn't work because running mRemoteNG.exe process in 64bit can't load MSTSC ActiveX component (referenced assemblies) because original files were assembled from 32bit dll [mstscax.dll]?
Error message when making RDP connection:
Could not load file or assembly 'Interop.MSTSCLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
I was able to create new AxInterop.MSTSCLib.dll and Interop.MSTSCLib.dll assemblies from 64bit dll version and now it works with "AnyCPU":-)
http://www.filedropper.com/axinteropmstsclib-mremoteng
Using AxImp.exe and TlbImp.exe didn't worked for me because it creates assemblies in wrong namespace "MSTSCLib" instead of "Interop.MSTSCLib" (AxImp.exe) and TlbImp.exe for changing namespace generated many "marshaled errors"
so final .dll wasn't working.
Adding MSTSCAX.dll reference in Visual Studio directly created correct and functional assemblies. Who don't know how to create 64bit compatible assemblies or don't have Visual Studio, feel free to check linked file.
Hope it helps
P.S. Sorry for possible technical misinterpretation, I am not programmer so creating new assemblies was trial-error process...

Overriding function keys when using MS Remote Desktop Connection

Is there a way when connected to a RDP client using MS Remote Desktop Connection to prevent the function keys from being intercepted and handled by OSX. For example on my iMac keyboard, function keys 7 to 12 are used to control itunes and alter the system sound volumes. Is there a way to have these keys processed by the RDP client instead, so that the remote Windows OS can handle them?
While this question currently relates to an iMac, I'll soon be using a Macbook Pro in the same scenario, and will be requiring a similar solution for that machine.

Thanks for your suggestion. Setting that option only toggles what the function keys are interpreted as in OSX, but the key presses are still not processed by the OS in the RDP session. For example, pressing F9 when the RDP window is active shows all open OSX windows in Expose, rather than having the keypress processed by the active software in the RDP session
I did try posting to the forum you mentioned yesterday, but due to server issues my post failed. I'll try again today.

"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 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

Why, when I successfully connect to Server 2012 Essentials R2 via Anywhere Access does the Remote Desktop Connection use the self signed certificate for RDP instead of the SSL certificate I installed when I set up access anywhere?

Scenario:
Windows Server 2012 R2 Essentials
I purchased an SSL Cert from GoDaddy and I managed (after some challenges) to set up Anywhere access to use that new SSL Cert. I to rebooted the server and I am able to login to Anywhere Access vis https (using the SSL certificate) from PC, Mac and iOS.
So far so good.
The problem I am having is that when I click to launch a remote desktop connection to the server RDP connection wants to use the self signed SSL certificate of the server rather than the SSL Certificate I installed into Anywhere Access. As a result, I get
a security warning like this: "The identity of the remote computer cannot be verified. Do you want to connect anyway?"
The name in the certificate appears as ACME-SERVER.ACMEDOMAIN.local instead of the SSL Certificate I installed, which is
remote.acmedomain.com
If I lick to accept, RDP does work fine, it;s just using a self signed certificate. I want it to use the trusted certificate that I purchased and installed.
My guess is that there must be an additional step to tell Anywhere Access that when it generates the RDP session that it should use the cert? OR, is this just how it works?

Because....
the server does not have a 'trusted' certificate assigned to it.
Only the RDP Gateway has the trusted certificate for the external name.
If you want to remove that error, you have to do one of the following:
Make sure your domain uses a public top level domaim, and get a public trusted certificate for your server.
So, something like,
server.domain.publicdomain.com
Or,
Install that certificate on your remote computer so it is trusted.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

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

Remote Desktop Connection and printing issues

Hi,
I am using Windows 7 on my desktop and also connected to Windows Server 2008 R2 to run applications in Windows Server. However, I noted there is problem with the printer issues. Sometimes, when I tried to print some documents using applications
in Windows Server with my local printer in my room connected to desktop, it won't work.
Moreover, I need to go to Windows Server, Component Service to restart printer spooler so it will work again. This is a pain.
I also noticed there is about 30 seconds wait to process any document to print.
Unlike if I print documents directly from my local desktop computer running Windows 7 and connected to local printer, it only takes seconds to print.
My desktop is connected to Windows Server 2008 via local area network. I should not expect such a significant delay in printing.
I also wonder why printer spooler needs to be restarted when printer is not working.
Can anyone advise me about this? Can Microsoft looks into this problem and release updates to fix the bug to improve the system?
Thanks
Regards,
Clement

Hi,
Please check if you turn on this settings:
You need to set this up just before you connect. The setting will be saved so that you won't need to change it the next time you connect.
1. Open Remote Desktop Connection by clicking the Start button, clicking
All Programs, clicking Accessories, and then clicking
Remote Desktop Connection.
2.Click Options, and then click the Local Resources
tab.
3.Under Local devices and resources, select the Printers check box.
4.Click Connect to start the session.
Make sure that you select your printer in the Print dialog box each time you print.
Karen Hu
TechNet Community Support

Remote Desktop connection and retina display

I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop. it's really important that that this staff works as good on my new computer. The problem is that when I open the connection on MacBook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, making it bigger or smaller but the display is still not great. Any suggestions or advice would be greatly appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resultion settings, still the same.
Any suggestions/help would be much appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resultion settings, still the same.
Any suggestions/help would be much appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, still the same.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, still the same.

Should I assume from your reply that the solution lies with my corporate IT?

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.

Remote Desktop Connection stopped working

I made a change to my Verizon TV and Internet package, downgrading from Ultimate HD to Extreme HD and from 35/35 to 25/25. This morning, when I ran a speed test it showed the new speed. I went out for a few hours, and when I returned, my internet connection was not working at all.
I called Verizon's support number and, after talking to two different people, one who wanted to swap out my router, and one who wanted to send a tech to check out my ONT, they finally figured out the problem was with their configuration, not any of the hardware in my house, and got me running again at the correct speed.
During the trouble shooting process, they had me do multiple soft and hard reboots of my router, they remotely rebooted it, and had me push the recessed reset button once, restoring it to factory defaults. This led to problems with my wireless devices, so I loaded a configuration file to the router that I had thankfully saved some time prior to this problem, and everything seemed to be working properly.
Then, I tried to open a remote desktop connection from one of my machines to another one, both on my internal home network, a connection that had worked flawlessly up until now, and it would not work. Moreover, trying to ping the "remote" machine from the one trying to initiate the connection gets no reply, but pings are replied to in the other direction. And, both machines can see and access each other's shared folders and files, and both can see each other in the network map in the networking and sharing control panel app.
I never made any configuration changes to either machine during the trouble shooting process, but to be sure, I used system restore on both machines and took them back to restore points made yesterday, when everything was working.
I am at a loss to understand what has gone wrong, and would appreciate any constructive and helpful suggestions as to how to remedy this situation.
ps
I am running two different web servers on the target machine, and am running stunnel on it to provide secure nntp connections to a news client that doesn't have that capability built in, and none of these servers are available from other machines. Nothing seems to be getting through to the target pc except windows network sharing!

dslr595148 wrote:
#1 In the router go to Advanced -> Universal Plug and Play OR to Advacned -> UPnP (what ever exist in your router).
#2 If you do not have at least two special computers that support Universal Plug and Play (UPnP) where you can not define the ports that they use, turn off UPnP.
A perfect example. At least two game consoles. Any two (Two Xboxes, two Playstations, One Xbox and one Playstation).
#3 If you have at least two special computers that support UPnP where you can not define the ports that they use....
Do you only use one at time or are there times when at least two are on?
#4 In the router go to Advanced -> IP Address Distribution Or to Advanced -> Private LAN
#5 What is the Starting and Ending IP Address, that is listed in there?
We have two Xboxes and a Logitech Revue. I have Windows Media Sharing enabled on three computers, and am also running a beta of Logitech Media Server on one. It is possible that there are times when two or more streaming clients are in operation, but that is a very rare occasion. Two of the computers, the ones I mention in my original post, are on almost continuously.
In Advanced -> Universal Plug and Play, both Allow Other Network Users to Control Wireless Broadband Router's Network Features and Enable Automatic Cleanup of Old Unused UPnP Services are checked, and WAN Connection Publication: is set to Publish Only the Main WAN Connection.
In Advanced -> IP Address Distribution, under Dynamic IP Range it says192.168.1.2 - 192.168.1.254. However, in Advanced -> IP Address Distribution -> Connection List I have set all the lease types to Static, because I was having problems using the Verizon web page to access my set top boxes, particularly the MRDVR. The Static IP addresses for the computers, game consoles, Bluray player etc. are in the range 192.168.1.2 - 192.168.1.12, and the set top boxes are at 192.168.1.100 & 192.168.1.101.
One thing I did not mention in my original post is that I have two unmanaged gigabit ethernet switches in my home network. There are two computers, the ones I mention in my original post, and the Logitech Revue plugged into one switch. That switch plugs into another switch which also has one pc, an Xbox, and a Bluray player plugged into it, and that switch then plugs into one of the ports on my Verizon supplied Actiontec MI424-WR Rev C, firmware version 4.0.16.1.56.0.10.14.4. All of the other ethernet ports on the router are unused. In addition, we have a laptop, a notebook, another Xbox, and a Wii that connect through the Actiontec's wireless.
I don't know if media streaming is still working and I don't really care if it is because we use it so seldomly. It never worked consistently or to our satisfaction. When we want to watch or listen to media from one computer on another, we copy it over the network from shared folders. We have a Homegroup, to which all of the computers belong. If we want to watch or listen to media on one of the game consoles, we copy it to a flash drive. The Bluray player is only connected to the network for firmware updates and for discs with network enabled content.
This same setup was operating before the problem developed, and I can't figure out what has changed to create the problem. The router configuration file that I am using is from June of 2011, and I'm pretty sure that everything was working fine then, and don't recall making any changes to the router's configuration since then.

Remote Desktop Connection Drops when opening a large file or Transferring a large file

Similar Messages

Maybe you are looking for