When making an RDP connection to terminal servers running Windows 2000 server we find that all of our existing printer drivers are not recognized. A Windows 7 RC client PC cannot print when RDP connected to our terminal servers which are running Windows 2000 Server. When using any of the standard printer drivers that were operational under Windows XP or Vista, such as the basic HP LaserJet 4 driver, they no longer work through terminal services. Curiously these same printer drivers do properly work when RDP connected to a Windows 2003 Serverbut not to a Windows 2000 Server. The event log on the Windows 2000 terminal server shows no printer related entries at all when the Windows 7 PC makes the RDP connection. The printers checkbox is checked but printer redirection is not working. Additionally I installed the new virtual Windows XP mode package on this same Windows 7 PC and noticed that the virtual Windows XP mode session automatically added the same printers to the virtual XP mode session as exist on the Windows 7 PC without having to manually install any new drivers. And when I RDP connect from the virtual Windows XP session to my Windows 2000 Server, the printers are properly recognized and useable in my terminal services session! This seems to indicate that this is not simply a printer driver mismatch situation as the very same printer drivers match and work properly when connecting from the virtual Windows XP mode session running on the same Windows 7 PC. I also manually disabled the new default Windows 7 policy Execute print drivers in installed processes but it made no difference. Also, there is a significant performance hit when connecting to a Windows 2000 terminal server. It looks like something is out of whack with RDP connections from a Windows 7 PC to a Windows 2000 server.

There's definitely something wrong when you connect to 2000 TS machines, but there's been very few reports of it so far. Your thread and this one (http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/3ca5d000-adbb-4b1e-a735-2035bc0187c7 ) are the only two I've come across!

Connecting to a Windows 2000 system isn't going to give you the same functionality of newer operating systems. Especially any pre Windows XP systems.