samba - Aug 2002 - NT, 2000, and XP can print - 9x can't!

I work exclusively in the area of small LANS (5-10 machines max) where 
security is not a major issue.  Therefore I have always created simple 
smb.conf files with share based security.  I am also a newbee to Linux - 
most of my experience has been with SAMBA.

Re: My current problem, I have set up the system with both open and root 
only shares.  All clients can view and write to the open folder shares.  I 
have also tried to make the printer available to everyone - but only the NT 
based clients (NT4.0, 2000, XP) can print!  9x clients can see the printer, 
they can connect to it and/or capture it, but no matter what settings I use 
on the client side the print process locks up.

As you might expect, I am using client side drivers.

Any help would be greatly appreciated.  The smb.conf file follows.

Thanks much!

Vince Warde

SAMBA Version 2.2.1a
Red Hat 7.2

# Samba config file created using SWAT
# from 192.168.1.51 (192.168.1.51)
# Date: 2002/08/01 07:47:12

# Global parameters
[global]
     workgroup = HOME
     netbios name = MICROSERVER
     server string = MicroServer
     security = SHARE
     encrypt passwords = Yes
     log file = /var/log/samba/%m.log
     max log size = 0
     socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
     dns proxy = No
     guest account = root
     printing = lprng

[homes]
     comment = Home Directories
     valid users = %S
     read only = No
     create mask = 0664
     directory mask = 0775
     browseable = No

[printers]
     comment = All Printers
     path = /var/spool/samba
     guest ok = Yes
     printable = Yes
     browseable = No

[webfiles]
     path = /var/www/html
     read only = No

[shares]
     path = /shares
     read only = No

[data]
     path = /shares/data
     read only = No
     guest ok = Yes

[programs]
     path = /shares/programs
     read only = No
     guest ok = Yes

-------------- next part --------------
HTML attachment scrubbed and removed
-------------- next part --------------
Vince Warde, A+ Certified Tech.
Computer Consulting and Service
VISA and M/C Accepted
3406 Bristol Ct
Cameron Park  CA  95682
vince@douloscomputer.com
http://www.douloscomputer.com
Toll Free Voice: (888) 932-3315
Fax: (707) 516-2602

On Fri, 2002-08-02 at 13:37, Vince Warde wrote:
I almost skipped your mail since my spam checker flagged
it...
> SPAM: -------------------- Start SpamAssassin results
----------------------
> SPAM: This mail is probably spam.  The original message has been altered
> SPAM: so you can recognise or block similar unwanted mail in future.
> SPAM: See http://spamassassin.org/tag/ for more details.
> SPAM: 
> SPAM: Content analysis details:   (6.7 hits, 5 required)
> SPAM: Hit! (0.5 points)  Subject has an exclamation mark
> SPAM: Hit! (1.1 points)  BODY: Contains a tollfree number
> SPAM: Hit! (3.0 points)  URI: Uses a dotted-decimal IP address in URL
> SPAM: Hit! (2.1 points)  BODY: FONT Size +2 and up or 3 and up
> SPAM: 
> SPAM: -------------------- End of SpamAssassin results
---------------------
> 
> --=====================_296186633==_
> Content-Type: text/plain; charset="us-ascii"; format=flowed
> 
> I work exclusively in the area of small LANS (5-10 machines max) where 
> security is not a major issue.  Therefore I have always created simple 
> smb.conf files with share based security.  I am also a newbee to Linux - 
> most of my experience has been with SAMBA.
> 
> Re: My current problem, I have set up the system with both open and root 
> only shares.  All clients can view and write to the open folder shares.  I 
> have also tried to make the printer available to everyone - but only the NT
> based clients (NT4.0, 2000, XP) can print!  9x clients can see the printer,
> they can connect to it and/or capture it, but no matter what settings I use
> on the client side the print process locks up.
> 
> As you might expect, I am using client side drivers.
> 
> Any help would be greatly appreciated.  The smb.conf file follows.
> 
> Thanks much!
> 
> Vince Warde
> 
> SAMBA Version 2.2.1a
this is quite old now ...
you should consider upgrading to 2.2.5 (where various printing problem
have been fixed)

      guest account = root
uh this is a BAD idea

everything else looks reasonable

you need to examine your logs (after increasing log level) to see what
is happening when the 98box tries to print.

are the permissions on /var/log/samba appropriate

did you try a map to guest = bad user parameter?

brad