No subject

Drivers are stored in the print$ share.  Under this share there are
5 folders, each for a different architecture.  Under these folders
may be some subfolders (e.g. print$\W32X86 has folder "2" and "3" under it).
The client goes to install a shared printer and will access these
folders and pull out the appropriate file.

Drivers are added likewise by going to the shared printer, getting
properties,
and selecting "add drivers" from advanced (done from a windows machine).

This is the nice, oversimplified, way it seems to work.  But I haven't
needed
more detail then that to get my system to work.

 -Larry Engleman
 The Burgiss Group
 201-795-5144


-----Original Message-----
From: Frank Ling [mailto:ling at atd.ucar.edu]
Sent: Friday, July 26, 2002 2:45 PM
To: samba at lists.samba.org
Subject: [Samba] Windows NT/2000/XP printer driver downloading


Hi,

I am new to the Samba world. I have a question regarding the Windows
NT/2000/XP automatically printer driver downloading.

Do we, the Sysadmins, have to set up different printer entries in
smb.conf to tell the Windows NT/2000/XP end users to use different
printer drivers for their systems? Or Does the Samba have the capability
of automatically identifying client OS, then download different printer
drivers for Win NT/2000/XP accordingly, even each printer has only one
entry in smb.conf? I assume that the printer drivers for Windows
NT/2000/XP will be stored on /etc/local/samba/printers/W32X86 directory.

After checking with your discussion about this issue, it seems to me
that Samba uses cookies to identify the client OS. But my understanding
could be wrong.

Currently we have Samba 2.2.3-pre on Solaris 8, and we are testing Samba
2.2.5 for Solaris 8 on another machine.

Thanks for your help.

Frank Ling
Systems Administrator
UCAR/NCAR/ATD



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba