Terminal Server. Windows cannot connect to the printer. Error 0x00000002

A few days ago I had a customer with a problem that was as follows:

• In a RDS Farm (Terminal Server) some users cannot print to any printer
• It was only happening in one server of the Farm
• some users logged in on the same server had no problem at all and could print to their preferred printer. The error was 0x00000002
• Some users reported that they didn’t get their printer(s) mapped by Script when they logged in to that specific RDS server
• The Terminal Servers were in Windows Server 2008 x86

Let´s see how to resolve this:

Working with NLB - RDP Not Working with Black Screen. Some Considerations

Windows Network Load Balancing (NLB) is a feature that distributes network traffic among multiple servers or virtual machines within a cluster to avoid overloading any hosts and improve performance. The Network Load Balancing feature uses the TCP/IP networking protocol to route traffic to different hosts based on a user's settings and a proprietary Microsoft distribution algorithm. The feature is available in Microsoft Windows Server 2008, 2008 R2, 2012 and 2012 R2 operating systems.

Network Load Balancing can also ensure network traffic is re-routed to remaining hosts if one or more hosts within the cluster fail unexpectedly. A Network Load Balancing cluster can scale up to 32 servers/nodes.

We can use NLB when configuring Terminal Servers High Availability. Let's take for instance the picture below:

All the Internal Users and possible External Users can use the VIP Address of the NLB to reach one of the Terminal Servers. If one Server is Down, the NLB automatically redirects all the requests to the remaining one. The same happens with WebServers.
 

Let's see some of the most common problems and considerations: