Win 9x SAMBA Printing Problem

[vincewarde]

I am continuing to struggle with a strange SAMBA Printing problem. Here are the details:

1) NT based clients can log on as guests or as users and can print in either case with no problems.

2) Windows 9x clients can log in as either guest or as users and can access shares with no problems.

3) Windows 9x clients attempting to print directly to the SAMBA printer hang the print process and require a reboot

4) After capturing a printer port, the 9x clients can print by copying either a text or .prn file from the command prompt

The Linux machine is running Red Hat 7.2 and the RAW printer is the only printer installed.

Any help you can provide would be greatly appreciated!


# Samba config file created using SWAT
# from 192.168.1.104 (192.168.1.104)
# Date: 2002/08/08 09:22:39

# Global parameters
[global]
workgroup = HOME
netbios name = MICROSERVER
server string = Red Hat Linux Microserver
encrypt passwords = Yes
map to guest = Bad User
unix password sync = Yes
log file = /var/log/samba/%m.log
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
preferred master = False
local master = No
domain master = False
dns proxy = No
guest account = admin
printing = lprng

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

[LPT1]
path = /var/spool/samba
read only = No
guest ok = Yes
printable = Yes
printer name = LPT1
oplocks = No

[shares]
comment = create new shares here
path = /shares
read only = No

[data]
comment = create data directories here
path = /shares/data
read only = No
guest ok = Yes

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

 

[enigma174]

have you tried placing a 'guest only' option in the [LPT1] parameters. This forces the clients to connect as guest and can help narrow down whether it's an authentication problem.

Which machine hangs and required a reboot, the windows or the linux box??

HTH
--cb

 

[vincewarde]

The problem has been solved - LPT1 was being confused with a local port on the 9x boxes. Changing the name of the printer share solved the problem.