RE: [Samba] WARNING: The printer driver locationoption is deprecated

2003-03-27 Thread Peter Carpenter
Andre,

Read Chapter 6 Printing Support in Samba 2.2.x in the
Samba-HOWTO-Collection document which is in your source tree as a .pdf and
a .html and on the Samba web site.

PCC

-Original Message-
From: Andre Dieball [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 26 March, 2003 5:50 PM

Hello

After upgrade to 2.2.8-1 woody fom 2.2.7a I get (apart from other problems)
the following error message:

WARNING: The printer driver locationoption is deprecated

As I use the Samba server only for printing, I'm not sure, what this means
to me, as I have the follwoing in my smb.conf:

printer driver file = /etc/samba/printers.def

Any help is really appreciated.

Thanks a lot in advance.


Mit freundlichen Grüßen / Yours sincerely,

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


RE: [Samba] Fw: share a folder rw, but not deletable?

2003-03-26 Thread Peter Carpenter
On Wed, 26 Mar 2003, Brian Wiese wrote:

 Is there a way in UNIX to make a folder with read+write permissions for
 some group of users, but only allow them to read and write to the
 folder... not actually delete the folder itself?

In Unix the permissions (perms) of the _parent_ directory determine who
can remove a sub-directory (= folder in Windows). So you can set the perms
on a given directory wide open but restrict write access to its parent.
Maybe this is all you need?

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


RE: [Samba] Automated printer driver problems

2003-03-21 Thread Peter Carpenter
Andy,

Hmm. Looks ok to me but I'm just a user not a guru. Here's a couple of
things to try:
  - log level = 1   (for a bit of connection info in the log)
  - you have TWO printer admin commands (dunno if this hurts)

My own print setup looks like this:
...
printing = BSD
printer admin = cpadmin  === i.e. explicit unix account
show add printer wizard = yes
username map = file mapping 'administrator' to 'cpadmin'

[printers]
path = path to spool dir
guest ok = yes
guest account = guest
browseable = yes
printable = yes

[print$]
path = path to driver dir
guest ok = yes
guest account = guest
browseable = yes
read only = yes
write list = cpadmin

Hope something here gives you a bright idea. It _will_ work - eventually...

PCC

-Original Message-
From: A.J.Dawson [mailto:[EMAIL PROTECTED]
Sent: Friday, 21 March, 2003 11:17 AM
To: Peter Carpenter
Cc: [EMAIL PROTECTED]
Subject: RE: [Samba] Automated printer driver problems


Heres the smb.conf file I'm using (suitably sanitised...)

Oh, and yes, I'm a member of the group 'Archive_adm'.

Regards
Andy


#Start of smb.conf file
[global]
   # general declarations for the server
   workgroup = WORKGROUP
   server string = Server
   socket options = TCP_NODELAY
   interfaces = XXX.XXX.XXX.XXX/24
   local master = yes
   os level = 69
   domain master = yes
   preferred master = yes
   domain logons = yes
   wins server = XXX.XXX.XXX.XXX
   time server = yes
   map archive = yes
   browseable = yes
   lm announce = no

   # log file options - log by machine name, not  200k /log
   log file = /usr/local/samba/log/log.%m
   max log size = 200

   # security considerations
   security = user
   encrypt passwords = yes
   # NOTE: we need to set this to no for Win95 clients  4.00.950a
   hosts allow = XXX.XXX.XXX. 127.
   remote announce = XXX.XXX.XXX.255/WORKGROUP
   guest account = nobody
   map to guest = Never
   guest ok = no
   domain admin group = @NT_adm
   add user script = /usr/sbin/useradd -c NT_machine -d /dev/null -g
NT_machines -s /bin/false %m$
   bind interfaces only = yes
   unix password sync = yes
   # ensure password changed get pushed to the NIS database...
   passwd program = /usr/bin/passwd %u ; make -s -C /var/yp

   # New directive to try to see if XP can log on...
   nt acl support = no

   # printer defaults
   load printers = yes
   printing = BSD
   print command = /usr/bin/lpr -P%p -r %s
   lpq command = /usr/bin/lpq -P%p
   printer admin = @NT_adm
   printcap name = /etc/printcap
   printer admin = @Archive_adm

   # logon paths etc.
   logon script = scripts\%u.bat

   # Win9x profile store location
   logon home = \\server\%u\profile\win9x

   # WinNT/2K/XP profile store location
   logon drive = p:

[netlogon]
   comment = Network Logon Service
   path = /usr/local/samba/netlogon
   guest ok = no
   writable = no
   browseable = no

[homes]
   comment = %u on %L
   volume = %u on %L
   writeable = yes
   valid users = @users
   nt acl support = no
   browseable = no

[Laserjet_6MP]
   comment = Laserjet_6MP on %L
   printable = yes
   path = /var/spool/lpd/spooldir
   printer = lj_6mp
   browseable = yes
   read only = yes
   valid users = @users

[print$]
   comment = Printer driver files on %L
   path = /usr/local/samba/printer_drivers
   guest ok = no
   browseable = no
   read only = yes
   write list = @Archive_adm
   directory mask = 0755

# End of smb.conf file








On Fri, 21 Mar 2003, Peter Carpenter wrote:

 To answer the easy bit first: the printer config info is stored in the
.tdb
 files in the $SAMBA_HOME/var/locks directory. I think the most relevant
ones
 are ntdrivers.tdb ntforms.tdb ntprinters.tdb share_info.tdb. I had a
similar
 experience to you with the Access denied etc messages and eventually got
 it right by endless futzing around but still don't really know what
produced
 the breakthrough. So keep trying - it _will_ work. If you post your
smb.conf
 I'll see if I've got anything you haven't.

 -Original Message-
 From: A.J.Dawson [mailto:[EMAIL PROTECTED]
 Sent: Friday, 21 March, 2003 10:06 AM

 Hi,

 I am having a problem with automating the download of printer drivers from
 a Samba 2.2.8 server.

 We used to use the server with he following options set:

 use client driver = yes
 disable spoolss = yes

 However these options have now been removed from smb.conf.

 Following the instructions available in printer_driver2.htm (supplied in
 docs/htmldocs in the source), I can add a printer driver to the samba
 machine.  To do this, I created a user called 'root' on my Win2K machine,
 logged on as that and then installed the driver to the server following
 the instructions.

 Running rpcclient server -U root%secret -c enumdrivers gives

 session setup ok
 Domain=[DOMAIN] OS=[Unix] Server=[Samba 2.2.8]

 [Windows NT x86]
 Printer Driver Info 1:
 Driver Name: [HP LaserJet 6P/6MP - PostScript]


 Running rpcclient server -U root%secret -c enumprinters gives

 Domain=[DOMAIN] OS=[Unix

[Samba] Printing issue: lpq command

2003-03-20 Thread Peter Carpenter
Dear Samba Printing gurus,

I've got Samba 2.2.8 feeding a commercial unix print spooler where users get
differing views of print queues according to their user class. Basically
operator types see everything while lowly users can only see their own
jobs. It doesn't appear to be possible to get this effect reliably via Samba
because when an operator clicks View--Refresh his display (of 10 jobs, say)
appears not only in his own printer window but also in the monitoring window
of an ordinary user who only has one job in the queue. Equally, if the
ordinary user refreshes his view, he sees just his one job again but now so
does the operator.

While trying to improve this behaviour I set lpq cache time to zero,
thinking this would help. (It didn't.) But I made another discovery. With
the cacheing disabled each Refresh from the Windows end (NT workstation)
causes THREE calls to the lpq command script !

Finally I tried using a separate lpq command script for each user by adding
%U to the script name in smb.conf and set cache time to 2 seconds to work
round the three calls thing. This gives better performance but still the
serious crosstalk problem remains.

Anyone got any insights to offer me on any of the above?

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


RE: [Samba] How do I upgrade from 2.2.5 to 2.2.8

2003-03-20 Thread Peter Carpenter
Yep, it's real important to be able to roll back! Does anyone know exactly
which .tdb files need to be copied? I suspect some of them should NOT be
copied over. I just did an upgrade from 2.2.6 to 2.2.8 and DID copy over:
ntdrivers.tdb ntforms.tdb ntprinters.tdb share_info.tdb

did NOT copy:
brlock.tdb browse.tdb connections.tdb locking.tdb messages.tdb printing.tdb
unexpected.tdb

This seemed to work - dunno if it's optimal.

PCC

-Original Message-
From: Michael G. Noble [mailto:[EMAIL PROTECTED]
Sent: Thursday, 20 March, 2003 5:01 PM
To: Bradley W. Langhorst
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Samba] How do I upgrade from 2.2.5 to 2.2.8


I use the method of creating a complete new install directory.  If you
are going to install 2.2.8, then use the directory samba.2.2.8 as the 
base of the install.  This way you can install the new version while the
old version is still running.  When you are ready you can then stop the
old version and start the new one.  If things go really bad, you can 
just start the old version back up and work on fixing the new one with
minimal impact on the users.

Mike

On Thu, 2003-03-20 at 08:47, Bradley W. Langhorst wrote:
 On Thu, 2003-03-20 at 09:25, [EMAIL PROTECTED] wrote:
  Samba List Serve Users:
  Is there a document or web link that follow that describes the steps to
  upgrade Samba from 2.2.5 to 2.2.8?  The documentation on samba.org the I
  have read assumes that the install is a fresh install and not an
upgrade.
  Thanks so much,
  Mark Roth
  Systems Engineer
  Mylan Pharmaceuticals, Inc.
  (304) 598-5430 x6864
 I'm not aware of such a document...
 If you're using a system that handles packages (ie most linux
 distributions) then you should be able to just install the new packages.
 
 if you must install from source - (management nightmare IMHO)
 then you can remove the old samba stuff, keeping the conf file and your
 tdb files safe.  Then after you install the new samba (and before you
 start it) put the conf file and tdb files where the new samba will
 expect them (depends on the options you pass to configure...)
 
 best wishes!
 
 brad
 -- 
 Bradley W. Langhorst [EMAIL PROTECTED]
 
 -- 
 To unsubscribe from this list go to the following URL and read the
 instructions:  http://lists.samba.org/mailman/listinfo/samba
-- 
Michael G. NobleRF Magic, Inc.
Senior System Administrator 10182 Telesis Ct., 4th Floor
San Diego, CA.   92121
email: [EMAIL PROTECTED]   voice: (858) 546-2401 x207
fax:   (858) 546-2402
--
There is Sanity in my Madness!

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


RE: [Samba] performance issues

2003-03-14 Thread Peter Carpenter
Have you tried deadtime = 15 or similar in your smb.conf?

-Original Message-
From: Mark Le Noury [mailto:[EMAIL PROTECTED]
Sent: Friday, 14 March, 2003 7:31 AM
To: Samba (E-mail)
Subject: [Samba] performance issues


Hi,

I have compiled and am running samba version 2.2.7.a on Redhat linux 7.3. I
am having some performance issues with it and was wondering if I was doing
something wrong.

I have noticed that if I use samba in security = server mode, every time a
new connection is made to the server from the same client a new smbd process
is started. It also seems as if the process only ends when the client
machine is rebooted.

When I use the server in security = user mode, every time a new connection
is made from a different client a new process is started. It also only seems
to kill the process when the client is rebooted.

I end up with a lot of processes running on the fileserver and sometimes the
machine locks up and complains about the max file limit being reached. I
have found a workaround by increasing the file-max value in /proc/sys/fs.

I was just wondering if there is a way to get the processes to die as soon
as the client disconnects from the server - maybe I have omitted something
when running the configure command??

I was also wondering if it is the default behaviour of samba to spawn new
processes every time a connection is made? Is it possible to change this
behaviour?

thanks in advance,

Mark Le Noury

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


RE: [Samba] Win95 Win98 - NOT WORKING - NT,2000, XP are ok (reposted)

2003-03-14 Thread Peter Carpenter
Did you change your security setting in your new Samba e.g. from share
to domain?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Friday, 14 March, 2003 7:00 AM
To: [EMAIL PROTECTED]
Cc: John H Terpstra
Subject: Re: [Samba] Win95  Win98 - NOT WORKING - NT,2000, XP are ok
(reposted)





I tried adding the [printers] section to my conf file as John suggested, but
this didn't solve the problem.
Still able to print from NT, 2000, XP  and not from Win95, 98

just recapping - am able to print from all clients with the old version
(2.0.6)
which we are still using in production

With the new Samba (2.2.7a) the file sharing is fine, but printing only
works
for NT,2000,XP
With Win95  Win98 only, the file gets put in the spool directory but
doesn't
seem to get
sent from the spool directory to the printer. (or picked up by the printer -
however it works...)

Any idea if Win95, 98 printing is treated differently to the newer OS's ?

thanks for any thoughts.

see below for other details...

-peter.





John H Terpstra [EMAIL PROTECTED] on 13/03/2003 03:02:55 PM
On Thu, 13 Mar 2003 [EMAIL PROTECTED] wrote:

Suggest you add a [printers] entry in your smb.conf file. You should NOT
need an entry for the printer itself. My samba-2.2.x prints fine from
Win95/98/Me as well as NT4/2K/XP.

- John T.

 Hey, thanks for your efforts anyway.

 I don't know what to make of this.
 Obviously a lot of things have changed between Samba 2.0.6 and 2.2.7a,
 but I can't figure out why Win95  98 suddenly can't print.
 I think you may be right - something to do with the new Samba using the
 MS-RPCs...
 which I imagine would mean a completely different printing method.
 Do you think this would require a different printer driver on the 95/98
boxes??
From what I read, I had the impression that it should all still work.

  I'd like to hear from anyone if they are successfully printing from
Win95,
 Win98 clients
  on a   Solaris server and using HP printers.

 I'm sure many people must be successfully printing from 95/98, but maybe
this
 problem
 is specific to my particular environment ?

 I am contemplating your suggestion about the bug message.
 Maybe another day or so of frustration and I will try it.

 again - thanks muchly for your help.

 -peter.


Date: Mon, 10 Mar 2003 18:33:35 +0100
From: maraqas [EMAIL PROTECTED]

Hi Peter,
i had a long, frunstrating web surfing yesterday night, searching for
something
that could apply to your case. I didn't find much at all, sorry. The only
thing
perhaps interesting to you could be this:
http://us2.samba.org/samba/ftp/docs/htmldocs/printer_driver2.html
This doc contains a section about migrating from 2.0.x to 2.2.x
I think the problem lyes in the new way samba manages printing, that is
by listening the MS-RPCs (Remote Procedure Call) coming from the
winNT and win2000 clients. This is done thanks to spoolss, as i figured
out reading here and there across the net. Well they say spoolss supports
even win9x driver calls, even if those OSes do not actually make an RPC.
They also say that backward compat. is reached through use client
driver
and spoolss disable. With these options enabled, the samba server
should
act just like it was a 2.0.x
I think you'd need help from the samba guys themselves, so i advice
reposting this problem with a more shocking subject line (suggest to
use the keyword BUG :)) so you'll be able to capture their attention.

Really sorry not to have been useful to you...

cheers

Maq

 
 Sorry to have to repost this (didn't get any response on the first
post),
 we really need some of the fixes of the new Samba but cannot go ahead
without
 the support for the older machines.
 Need to prove that Samba is the great product that I believe it is.
 
 Hi folks - I am having printing problems with our older machines.
 
 Printing is working fine for our Windows NT, 2000 and XP clients.
 However, with windows 95  98, the print job gets put into the Samba
 spool directory (path = /var/spool/lp/tmp/samba)  but doesn't make it
to
the
 printer.
 The print files stay there in the directory - don't get removed.
 
 Samba version is 2.2.7a,  on Solaris 8
 Printers are HP printers - e.g. HP 8100dn
 
 All clients including 95/98 were happily printing on a very much older
version
  of Samba (2.0.6)
 
 printing directly from Unix to the printer is working ok
 
 Has anyone experienced this problem or have any advice on how to
 get my older boxes printing with the latest Samba?
 
 any thoughts welcome - no really - anything - please
 :-)
 
 -peter.
 
 
 (p.s. Just for a wild stab in the dark I tried setting the disable
spoolss
=
  yes
 but this stopped all printing from making it to the computer - even
from
the
 clients that
 were originally working.)
 
 
 relevant bits of conf. file included below...
 note that I don't have print command explicitly stated, but testparm
 indicates that it is configured properly...
 
 [global]
   printing = sysv

  lprm 

RE: [Samba] how to view users logged in samba server??

2003-03-13 Thread Peter Carpenter
Have you tried smbstatus?

-Original Message-
From: Diego S. Soares [mailto:[EMAIL PROTECTED]
Sent: Thursday, 13 March, 2003 12:35 PM
To: [EMAIL PROTECTED]
Subject: [Samba] how to view users logged in samba server??
Importance: High


I do not know to do. 

I have around 50 logados users and would like to know the names of who are
logados at the moment.

I thank any aid.

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


RE: [Samba] Transferring the printer database

2003-03-11 Thread Peter Carpenter
Is there a way to transfer a Samba printer database from one version to
another? I tried copying the .tdb files from v2.2.6 to v2.2.8pre1 but it
didn't seem to work. Some sort of upgrade path is needed here - it's a lot
of work to start over if you've got a lot of printers.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 11 March, 2003 2:08 AM

Will this do what you want?
# printconf-tui --Xexport  printers.xml
# printconf-tui --Ximport  printers.xml

Patrick

? Tnx for the reply but is this printconf-tui thing anything to do with
Samba?

The issue here is transferring things like driver mappings, default paper
size, default tray and so on when you change the version of Samba. (The
stuff a Windows Administrator sets in printer properties.) The driver
files themselves can be easily preserved or copied but the knowledge that
printer xyz is a HP Laserjet 4000 loaded with A4 paper in the lower tray
is stored somewhere in those mysterious .tdb files.
PCC


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


[Samba] Transferring the printer database

2003-03-07 Thread Peter Carpenter
Is there a way to transfer a Samba printer database from one version to
another? I tried copying the .tdb files from v2.2.6 to v2.2.8pre1 but it
didn't seem to work. Some sort of upgrade path is needed here - it's a lot
of work to start over if you've got a lot of printers.

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


RE: [Samba] installing printerdriver without being admin under NT

2003-03-06 Thread Peter Carpenter
The printer install feature works here with NT workstations and Samba
2.2.6 as the server. Samba is not the PDC but I don't see why that should
matter. Have you uploaded the NT printer drivers as well as the W2K drivers?

PCC

-Original Message-
From: Nicki Messerschmidt, Linksystem Muenchen GmbH
[mailto:[EMAIL PROTECTED]
Sent: Thursday, 06 March, 2003 5:25 PM
To: Jesko Schneider; [EMAIL PROTECTED]
Subject: Re: [Samba] installing printerdriver without being admin under
NT


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jesko Schneider wrote:
 i have NT and Windows 2000 Client served by a Samba PDC. This PDC is
 also CUPS-Printingserver. Now i up loaded the windows printing driver
 to the Samba-server into the print$ share.
 Under Windows 2000 i can download/install the driver with every
 PDC-account by clicking on the printershare, under Windows NT i need
 to be in the local administration group.
 Is there any possiblity to it under NT , which will give me the same
 opportunity like win2000 ? ( = download/install the driver with every
 PDC-account without being in the local admin group ???)
As far as I rember this is not possible, because in Windows NT 4 the
printer drivers are still kernel space und no normal user account has
the permissions to install printer drivers. In Windows 2000 this
bug/feature has been circumvented by moving the printer drivers to
user space... 
I think want you want is not possible, but I may be way off mark her...
*g*


Cheers
Nicki

- -- 
Linksystem Muenchen GmbH  [EMAIL PROTECTED]
Schloerstrasse 10   http://www.link-m.de
80634 Muenchen  Tel. 089 / 890 518-0
We make the Net work.   Fax 089 / 890 518-77

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.3 for non-commercial use http://www.pgp.com
Comment: Keys at: https://www.link-m.de/pgp

iQA/AwUBPmd2Y+s1nPm17iBDEQKanwCfWRRW3r2vHhEEx9/SkMKhxC+6COMAnAjr
lpaQvRmAe5h5duoD5NnnARH3
=FuI6
-END PGP SIGNATURE-

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


RE: [Samba] Adding printer stops with Operation could not be completed

2003-03-03 Thread Peter Carpenter
Tor,

For what it's worth I finally got the Add Printer wizard working with
Samba 2.2.6 at the Unix end and Windows NT as the client. But it was a hell
of a struggle! Don't know if it works with Samba 2.2.5 and/or Windows XP.
BTW I don't see an add printer command in your smb.conf extract - don't
you need that?

Regs
PCC

-Original Message-
From: Tor Bechmann Sørensen [mailto:[EMAIL PROTECTED]
Sent: Monday, 03 March, 2003 5:44 PM
To: [EMAIL PROTECTED]
Subject: Re: [Samba] Adding printer stops with Operation could not be
completed


I am still hoping that someone might have an answer to my problem, as 
stated below. Since my last post I have tried the all windows OS 
versions bundle driver from HP. It apparently installed, the 
printer property panel, sharing, additional drivers showed all 
drivers as installed (X86), but on the server actually only 
windows2k/Xp was present. In addition any computer which installed 
the printer now crashed explorer.exe every time a printing 
operation was tried. So I erased the drivers, and uninstalled the 
printer in winXP, and tried with default devmode = yes. Now printing 
doesnt cause crashing, but the printer property in windowsXP still shows 
all drivers installed, and still the win95/98 drivers are actually not 
there. I have included my previous post below, FYI.

Regards Tor Bechmann Sorensen

 When trying to add the drivers downloaded  extracted from HP 
 (lj456ps.inf from lj632en.exe) I get the following message:
 
 Unable to install HP LaserJet 5P/5MP Postscript, Windows NT 4.0 or 200, 
 Intel driver. Operation could not be completed.
 
 I also tried installing win95/98 drivers. In this case some files are 
 copied but then I get the equivalent of the above message for 95/98.
 
 I am adding them from a windows XP machine. I am loggin onto the samba 
 shares with my account which is in the staff group on the server.
 
 When I try to change some settings in the properties, like hold 
 mismatched documents I get an access denied error message.
 
 
 
 Ive set up my smb.conf like this (relevant lines only):
 
 [global]
   printer admin = @staff
 
 [print$]
 path = /var/prndrv
 guest ok = no
 browseable = yes
 read only = yes
 write list = @staff
 
 /var/prndrv looks like this  
 
 drwxrwxr-x2 root staff4096 Mar  2 03:07 W32ALPHA
 drwxrwxr-x2 root staff4096 Mar  2 03:08 W32MIPS
 drwxrwxr-x2 root staff4096 Mar  2 03:08 W32PPC
 drwxrwxr-x2 root staff4096 Mar  2 05:18 W32X86
 drwxrwxr-x2 root staff4096 Mar  1 20:43 WIN40
 
 and /var/prndrv itself has same ownership/permissions.
 
 I am using samba 2.2.5. 
 
 The host specific log noodless.log (noodless is the win client i use to 
 add the drivers from), shows no error messages. It does give a lot of 
 messages, too much to quote here, but none of them are informative to me. 
 
 Help would be appreciated
 
 Regards 
 Tor Bechmann Sorensen
 
 

-- 


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


[Samba] Separate mailing list for printing problems ?

2003-02-28 Thread Peter Carpenter
Guys,

Is there any chance of getting a separate mailing list just for Printing
issues e.g. [EMAIL PROTECTED]. Printing is a world of its own
within Samba, at least once you get past the very basic stuff. And there's
_so_ much traffic in the main samba list now...

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