Ok...I'm stuck.
Environment:
Suse 8.0, with Samba 2.2.3a, no domain controller (workgroup only).
Client machine is NT4 Workstation, SP5.
Access to disk shares is fine, no problems, using encrypted PWs.
I'm trying to set up a [print$] share, as described in chapter 6 of the
Samba-HOWTO-Collection.
The symptom that I get is that when I attempt to load the driver to the
print$ share, I get a "copy error" on the NT machine, which seems to
indicate a problem with the source. Yet, I can install the driver from
this location directly on the NT machine without a problem. When this
appears, no files are put in the print$ share.
It looked to me like a permissions problem, so that is how I have been
approaching it, but to no avail. The location for print$ is
/etc/samba/drivers, owned by root:root, with 777 access, including the
parent directories.
I though perhaps the ownership by root was as issue, so I also tried a
directory owned by ldieter:users, which is how I am connecting (ldieter is
an admin account on the NT box), but saw the same problem.
The relevant part of my smb.conf is below...any help would be greatly
appreciated.
Regards,
-Lloyd
# Global parameters
[global]
workgroup = LANGROUP
interfaces = 192.168.5.2/24
security = SHARE
encrypt passwords = Yes
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
printcap name = cups
character set = ISO8859-15
os level = 2
printer admin = @ntadmin, ldieter
printing = cups
use client driver = Yes
[printers]
path = /var/spool/samba
printer admin = root
guest ok = Yes
hosts allow = 192.168.5.
printable = Yes
browseable = No
[printer$]
comment = Printer Drivers
path = /etc/samba/drivers
write list = root, @ntadmin, ldieter
guest ok = Yes
browseable = yes
readonly = yes
--
-----------------------------------------------------------------
Lloyd Dieter - Senior Technology Consultant
Synergy, Inc. http://www.synergyinc.cc ldieter@snrgy.com
Main:585-389-1260 fax:585-389-1267
-----------------------------------------------------------------
Lloyd Dieter <dieter@snrgy.com> wrote:> Message: 8 > Date: Fri, 15 Nov 2002 06:41:50 -0500 > From: Lloyd Dieter <dieter@snrgy.com> > To: samba@lists.samba.org > Organization: Synergy, Inc. > Subject: [Samba] Problem with print$ > > Ok...I'm stuck. > > Environment: > > Suse 8.0, with Samba 2.2.3a, no domain controller (workgroup only). > > Client machine is NT4 Workstation, SP5. > > Access to disk shares is fine, no problems, using encrypted PWs. > > I'm trying to set up a [print$] share, as described in chapter 6 of the > Samba-HOWTO-Collection.Maybe you should *really* use for the share [print$], not [printer$] in your smb.conf...... ;-)> The symptom that I get is that when I attempt to load the driver to the > print$ share, I get a "copy error" on the NT machine, which seems to > indicate a problem with the source. Yet, I can install the driver from > this location directly on the NT machine without a problem. When this > appears, no files are put in the print$ share. > > It looked to me like a permissions problem, so that is how I have been > approaching it, but to no avail. The location for print$ is > /etc/samba/drivers, owned by root:root, with 777 access, including the > parent directories. > > I though perhaps the ownership by root was as issue, so I also tried a > directory owned by ldieter:users, which is how I am connecting (ldieter is > an admin account on the NT box), but saw the same problem. > > The relevant part of my smb.conf is below...any help would be greatly > appreciated. > > Regards, > > -Lloyd > > # Global parameters > [global] > workgroup = LANGROUP > interfaces = 192.168.5.2/24 > security = SHARE > encrypt passwords = Yes > socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY > printcap name = cups > character set = ISO8859-15 > os level = 2 > printer admin = @ntadmin, ldieter > printing = cups > use client driver = Yes > > [printers] > path = /var/spool/samba > printer admin = root > guest ok = Yes > hosts allow = 192.168.5. > printable = Yes > browseable = No > > [printer$] > comment = Printer Drivers > path = /etc/samba/drivers > write list = root, @ntadmin, ldieter > guest ok = Yes > browseable = yes > readonly = yes >
Yes, tried that too...no joy. On Fri, 15 Nov 2002 15:31:24 +0100 "Kurt Pfeifle" <kpfeifle@danka.de> wrote:> > Maybe you should *really* use for the share [print$], not [printer$] > in your smb.conf...... ;-) > > > The symptom that I get is that when I attempt to load the driver to > > > > # Global parameters > > [global] > > workgroup = LANGROUP > > interfaces = 192.168.5.2/24 > > security = SHARE > > encrypt passwords = Yes > > socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY > > printcap name = cups > > character set = ISO8859-15 > > os level = 2 > > printer admin = @ntadmin, ldieter > > printing = cups > > use client driver = Yes > > > > [printers] > > path = /var/spool/samba > > printer admin = root > > guest ok = Yes > > hosts allow = 192.168.5. > > printable = Yes > > browseable = No > > > > [printer$] > > comment = Printer Drivers > > path = /etc/samba/drivers > > write list = root, @ntadmin, ldieter > > guest ok = Yes > > browseable = yes > > readonly = yes > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >-- ----------------------------------------------------------------- Lloyd Dieter - Senior Technology Consultant Synergy, Inc. http://www.synergyinc.cc ldieter@snrgy.com Main:585-389-1260 fax:585-389-1267 -----------------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1> Message: 10 > Date: Fri, 15 Nov 2002 10:54:35 -0500 > From: Lloyd Dieter <dieter@snrgy.com> > To: samba@lists.samba.org > Subject: Re: [Samba] Problem with print$ > Organization: Synergy, Inc. > > On Fri, 15 Nov 2002 15:31:24 +0100 "Kurt Pfeifle" <kpfeifle@danka.de>wrote:> >> >> Maybe you should *really* use for the share [print$], not [printer$] >> in your smb.conf...... ;-) >> >> Yes, tried that too...no joy.Well, maybe you should also 1)Ensure the directories below /etc/samba/drivers exist (specifically W32X86) and are writeable 2)Read the extensive documentation on this in the samba-HOWTO-Collection 3)Turn on logging and see if samba is picking up problems 4)Choose a distro which does most of this for you BTW, your 'readonly' option should be 'read only'. Have you run 'testparm' ?>> > The symptom that I get is that when I attempt to load the driver to >> > >> > # Global parameters >> > [global] >> > workgroup = LANGROUP >> > interfaces = 192.168.5.2/24 >> > security = SHARE >> > encrypt passwords = Yes >> > socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY >> > printcap name = cups >> > character set = ISO8859-15 >> > os level = 2 >> > printer admin = @ntadmin, ldieter >> > printing = cups >> > use client driver = Yes >> > >> > [printers] >> > path = /var/spool/samba >> > printer admin = root >> > guest ok = Yes >> > hosts allow = 192.168.5. >> > printable = Yes >> > browseable = No >> > >> > [printer$ >> > comment = Printer Drivers >> > path = /etc/samba/drivers >> > write list = root, @ntadmin, ldieter >> > guest ok = Yes >> > browseable = yes >> > readonly = yes- -- |----------------Registered Linux User #182071-----------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE92K1/rJK6UGDSBKcRAneLAKCIFiPVqkg1AFBMh0NLga4/+yLGkgCdFa35 WCePxNj5eQSVnFni8EqT724=MufH -----END PGP SIGNATURE-----