Hi Andrew, desperate struggles to understand comments inline > if I have 2003 terminal servers, and do not wish them to install v2 print > drivers, how do I get the 2003 printer servers to print to printers attached > to windows 2000 printer servers which have v2 drivers installed?? Just what ARE you up to today mr lilley? :) ** Ah, you know, the usual, shuffling windows around on my screen and looking very very busy indeed. I've had XP machines printing to NT print servers, which is kinda along the lines you're getting at, I guess. When mapping the printers to the XP machine, XP would come up saying no suitable driver found, please choose, and giving me Windows' normal printer driver list.. Do you not get this? If not, have you turned off the "dont install v2 drivers" policy? ** by default, the Windows 2003 server will not allow the auto-install of the network print server's Version 2 print driver.. so the mapping of the printer connection fails completely... like I said, I did try and map to V3 driver but it falls over in a heap! > in fact, what exactly is the process, if one prints from a terminal server to > a network print server, why doesn't the print server just pass on the print > job?? I'd check you're not doing a PCL6-> PCL5 or PS (or whatever!) conversion along the way. You could also check the print processor i guess, as I wouldnt be surprised if 2003 supported a higher EMF version than 2000 did - although RAW is the default, so it ought to just work :/ ** hhhmmm... the test I did used the "HP LaserJet 5000 Series PCL 6" drivername which was exactly the same description less a space character to that of the drivername description for the version 2 driver, so I know they are both PCL 6 drivers.... anyway, I mapped the version 2 driver name to the version 3 driver in NTprint.inf. So, should I be able to use a V3 driver at the terminal server and have it pipe printstream through a version 2 driver on the printserver... that's what I wonder?? ============================================================================== This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. ============================================================================== ******************************************************** This Weeks Sponsor Emergent Online ThinCity Conference Join us at ThinCity 2004: The 1st Annual Emergent OnLine Technology Conference http://www.ThinCity.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm