Network Printing problem with terminal services

Some users are complaining that sometimes when they print, it's really slow and sometimes they don't get to finish what they were printing. Some of these users are on a network, some wired and some are using wireless. Network printing in a wireless environment on a Terminal Server can have bandwidth issues.

Please read a previous post regarding this topic. You can find it here.

Workaround for Printers that are not Redirected in a Remote Desktop Session

This article is from Microsoft Knowledgebase. It was forwarded to me by Chit De Jesus. Like other remote users she cannot print on the all in one wireless HP printer. This workaround requires you to go under the hood and get your hands dirty by going into your Windows XP registry. She tweak the Registry setting of her workstation and now the walla, the problem is gone.

I have to warn you, editing the registry of your pc might render your perfectly working windows xp unusable.

Ok here we go:
Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal Services Session.

To resolve this problem on a computer that is not running Windows Server 2003, force all ports (including DOT4) on the client computer to be filtered for redirection. To do this, add a DWORD value named FilterQueueType to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR and set its value data to FFFFFFFF.

Follow these steps, and then quit Registry Editor:

1.	Click Start, click Run, type regedit, and then click OK.
2.	Locate and then click the following key in the registry: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR
3.	On the Edit menu, point to New, and then click DWORD Value.
4.	Type FilterQueueType, and then press ENTER.
5.	On the Edit menu, click Modify.
6.	Type FFFFFFFF, and then click OK.

This enables all ports on the client to be redirected.

To work around this problem on a client computer that has a multifunction print device, change the port that the multifunction print device uses from DOT4 to an LPT port.

For example, to configure a multifunction print device to use an LPT port on a Windows XP-based computer, follow these steps:

1.	InControl Panel, openPrinters and Faxes.
2.	Right-click the local printer that is not redirected, and then click Properties.
3.	Click the Ports tab, click an LPT port, and then click Apply. The printer should now appear next to that port.
4.	Close the Printer Properties window, and then reconnect by using Remote Desktop.

Important When a multifunction printer is using a standard LPT port instead of the DOT4 port, it loses its multifunction capabilities, such as scanning, faxing, or copying. To regain the multifunction capabilities, the print device must use the DOT4 port.
To read the complete article please go to microsoft.com. Here is the complete link:
http://support.microsoft.com/kb/302361/en-us

Printing error or printing redirects to other branches

This topic has already been discussed, please read the previous post about this problem. Or go to Tags and click on Printing Problem, there are 4 post about this issue.

Understanding Printing Problems

1. Printer drivers are not written to be used on Terminal Servers
   
   Finally, though, a lot of printer manufacturers see the necessity of developing their drivers to be used on Terminal Servers. But there are still printer drivers which are written for usage on a workstation by one user at the time. Printer drivers not written for Terminal Servers are, most of the time, not capable of handling so many printing jobs. When the driver becomes overwhelmed, this can cause the spooler services to crash, or even worse the operating system will blue screen.
   
2. Printjobs use a lot of bandwidth
   
   Printjobs normally consume a large amount of bandwidth. This is not specifically related to Terminal Server environments, but most times it is a bigger issue when using Terminal Services. Because Terminal Services are used a lot when users need access from co-locations, home locations or supplier/customer offices where the bandwidth is limited to the location where the Terminal Servers are. Within environments with a small amount of bandwidth and lots of printjobs these jobs can use the full amount of bandwidth. This actually means that users are not able to work anymore because Terminal Server related traffic is brought to a stand still by the printer traffic.
   
3. Version conflicts by third party drivers
   
   Often (especially with new printers) the Windows operating system doesn’t have the driver for that printer. To use all the functionality of that printer the driver made by the manufacturer must be used. It may happen that one new driver overwrites a DLL also used by another driver. It may also happen that the printers using the pre-existing DLL do not function anymore. Therefore every new printer driver must be tested extensively before using it in a production environment.
   
4. All printer drivers need to be available on all Terminal Servers
   
   The most important rule in the Terminal Server world is that all servers hosting the same applications must be 100% identical. This rule also applies to the printer drivers. It is a difficult job to keep all related files to printer drivers identical on all servers especially if you have lots of printer drivers.

Taken from MSterminalservices.org

How do I know which printer drivers work with Terminal Services?

All of the Microsoft-supplied printer drivers are tested with Terminal Services and guaranteed to work. Before using a third-party printer driver, make sure it has been certified for Terminal Services. There is a Windows Hardware Quality Labs (WHQL) program for getting third-party printer drivers certified on Terminal Services. Please ask your printer driver vendor to secure such certification.

Now, in the Forex Cargo domain, we have noticed that the most compatible printer brand is the

1. Epson
2. Canon
3. HP

THE LIST IS ORDERED BY COMPATIBILITY.

Note: If you are going to get a new printer for use with remote desktop, get a regular printer, don't get the All in Ones. If you already have a All In One printer, there is a work around, but you have to do the adjustments manually on your end. Meaning you have to change some settings on your pc's registry which we don't recommend.

I will post the registry settings soon.

Printing Problem.

The most common problem in Terminal Services / Remote Desktop Connection is the printing problem. There are times a users can't find their specific printers or the print out prints on the wrong printer. The first thing a user should do is close the application that they are using (remittance or cargo) and log off the server.

Doing this should delete the printer initially assigned to your session and will free server resources. When you relogin the server will recreate a virtual printer for your session.

If you are still having the same printing problem please notify your administrator.

Logging Off

All users are requested to log off properly. When we say proper, all users must go through the normal procedure:

1. Click on Start
   
2. Click on Log Off

WHY IS THIS IMPORTANT?
When a user logs off, the session and other server resources are closed and released back to the server. The virtual printer that is created for that specific user is also deleted from the printer list, does minimizing printing error problems.

WHAT HAPPENS WHEN A USER DON'T LOG OFF?
When a user disconnects from a session, by just closing his/her remote desktop application. All applications that he/she is using are still up and running and are still using server resources. And with this Virtual Printer that is created for you stays in the printer list. This is not a good practice.

Disconnected Sessions are automatically ended after 10 to 15 minutes.

Idle Sessions are also automatically ended after 30 minutes.