** Proudly presenting: I’ve reported this issue together with Citrix Support to Microsoft, now there is a fix available, cool! **
Consider the following scenario:
- You create a Terminal Services session to a terminal server that is running Windows Server 2008.
- You connect to more than 100 print queues in the Terminal Services session.
- You try to use a print queue to print some documents. The print queue is not one of the first 100 installed queues.
For example, you try to print some documents to the 101st print queue.
In this scenario, you cannot use the print queue to print documents. Additionally, you receive the following error message:
Windows cannot print due to a problem with the current printer setup.
Note: After this issue occurs, one of the registry items under the following registry subkey has the winspool,Ne-01 value:
This issue occurs because the maximum number of ports that can be generated is a hardcoded value of 100.
When more than 100 print queues are created, the print spooler service does not recognize the newly created NE ports. Therefore, you receive the error message that is mentioned in the “Symptoms” section.
** Update 12-10-2011
We are heard, Microsoft released another fix in this case. http://support.microsoft.com/kb/2620656
Invalid redirected printers may be available in a Remote Desktop Services session that connects to a RD Session Host server that is running Windows Server 2008 R2
Exactly what I have been reporting:
This issue occurs because the Print Spooler adds a registry entry for each redirected printer under the following registry subkey for the user, and for all users logged on to the RD Session Host server: