Hello, Summary of question: How do we make sure the NT client downloads the right printer driver from a SuSE/SAMBA printserver when connecting to the printer ? Long essay: We've got a little PC setup to be a dedicated SAMBA print server for an HP LaserJet 6p - well at least that's the idea! We have got some way to making it all work. In a WinNT client you can browse the print server (called 'printserver') and it shows three printers (lp-ascii, lp-raw, and lp2). On 'printserver' there is a hidden share called print$ which contains the driver files for the printer. This has a sub-directory W32X86 and then all the driver files. We've also setup subdirectories called lp2, lp-raw and lp-ascii containing the same driver files as a straw-clutch The system does work after a fashion. By setting up a connection to lp2 in the login script it connects and I can print out as much text as my heart desires. However graphics causes the printer to spew out a load of PCL jibber. But on NT if I right-click on lp-raw and select install it asks for the drivers to be installed locally. Doing this I managed to print out a picture of a donkey. What is preventing it from downloading the driver from the printserver ? Thanks for any pointers. Joe Garfoot ICT Technician Corpus Christi Catholic College Leeds