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.

Similar Messages

Problems conencting via Remote Desktop Connection to a server

hello! i have a problem connecting to one of our servers via Remote Desktop Connection. The story goes like this: the server works fine, i can connect using my credentials with no problems, the firewall is up. But, when i restart the server, after loading
windows, the server wont respond. I try to ping its IP Address and no respond. The only way so far to fix this bug is to log on localy (without remote) and disable the Windows firewall. Instantly the server starts to respond and i can connect to it via remote
desktop conenction. If i restart the server, the problem appears again and the solution to it this time is to enable the windows firewall back again. This enable/disable firewall thing doesnt seem right. Does anyone have any idea?
thank you!

Hi Dede,
Your box is up to date with windows updates.
Witch windows server are you using?
Maybe review the firewall exceptions.
Att,
Nicolas Rojas

L7580 net printer driver disappearing in Win 7-62 after connecting with Remote Desktop Connection

I have an Officejet Pro L7580 connected via ethernet. I've been using the driver released from Jan 2010, and whenever I connect to my Windows 7 Ultimate 64 computer via Remote Desktop Connection, the printer drivers for both the printer and the fax disappear. I have to constantly run the "add a device" window to add the printers back again.
Why do they disappear like that?
Fishanderson

OK after updating the Server and clients I am still having this issue :(
and just today after no sound problems for 6 days the sound dropped out on a couple of RDP sessions, yet the sound on the client itself worked fine when tested (minimise the RDP session).
It took the RDP sessions to be restarted to restore the sound within the session.
I have found similar (old) thread regarding this problem:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/958fd891-6f55-432b-8268-a326ac6b2b2e/sound-in-remote-desktop-session-stops-working
but no one has informed about if as solution was ever found.

Remote Desktop Connection fails

I have a new Server 2012 R2 essentials install. I have tried connecting with remote desktop connection but have no success.
I can connect to the server at the local desktop. From any other computer on the network it fails.
I have checked a plethora of things I found on the internet but with no luck.
I have tried to connect by ip address, no luck.
I can ping the server just fine.
I cant find anything of help in the event viewer logs.
Any help appreciated.

Did you get any error message when failed to connect the server via remote desktop connection? Please use an administrator account to connect the server via remote desktop connection and check if the same issue still exist.
Remote Desktop goes to: Initiating connection for about 15 seconds, then I get:
Remote Desktop cannot connect to the remote computer for one of these reasons:
1. Remote access to the severe is not enabled.
2. The remote computer is turned off.
3. The remote computer is not available on the network.
In the Windows Server 2012 R2 Essentials, please follow the path: Control Panel-> System-> Change settings-> System Properties-> Remote and check if select "Allow remote connections to this computer" option.
I checked, it was already set.
In addition, please also open Group Policy Editor and follow the path: Computer Configuration-> Windows Settings-> Security Settings-> Local Policies-> User Right Assignment-> Allow log on through Remote Desktop Services. Add that correct
user or group, then check if this issue still exist.
I checked, it was already set.

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

Remote Desktop Connection certification issue with Win Server 2008 R2

When connecting to Windows 2008 server R2, from Windows 7, Vista and Mac OS 10.6.7 via Remote Desktop Connection, i am getting a 'Server Name on the Certificate is Incorrect' error.
if i click connect, i can still connect to the machine, due to a 3rd party managing the server, this doesn't look very professional on my part...
The server is a standalone machine and is not currently on a domain. RDC is only used for management purposes.

Hi,
This certificate error is normal, because your client do not trust the certificate which is installed on the terminal server. To avoid this issue,
you can export the certificate and import this certificate into the client side (computer account).
Thanks.

Would anyone know a way to get ASIO4all to operate through the Remote Desktop Connection Application?

Sound problem... when I try to use FL Studio via Remote Desktop Connection with a Windows XP laptop.

Hi Crimsonrain,
What is the model number of your router?

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

Printing on my mac whilst connected to windows 2003 remote desktop connecti

Hi, please can somebody help. I have a MacBook Pro and i am connecting to a windows 2003 server using microsoft remote desktop connection. I need to print on the printer connected to my mac. How do I get windows to see the printer that is connected to my Mac?

Hi, please can somebody help. I have a MacBook Pro and i am connecting to a windows 2003 server using microsoft remote desktop connection. I need to print on the printer connected to my mac. How do I get windows to see the printer that is connected to my Mac?
It looks like you have to have a postscript printer (i.e. a laser printer). I have been trying to solve this problem for some time with no luck so far.
Dual 2 ghz G5 Mac OS X (10.4.8)

Easy print not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1

Easy print is not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1 . Printers dont get redirected when you connect to the terminal server. The server we are connecting to has Windows 2008 server. On 32 bit Windows
7 and windows XP clients Easy print is working fine and printers get redirected in terminal server.

I am having the exact same problem. Windows 7 works fine, but 8.1 will not redirect printers. Others said to check local policy terminal services settings and my setting are all set as they should.
I think Windows 8.1 is not telling the terminal server what printers it has.

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

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!

Trouble Printing to Network Printer via Remote Desktop Connection

Similar Messages

Maybe you are looking for