Can't print anymore through my linux box

[ardian]

I cant't print from xp computers to my redhat 7.3 box printers anymore. I can login from xp to linux computer and see the shared directories and printers but when I try to print from notepad I recieve the message "A StartDocPrinter call was not issued". At the begining I was able to print perfectly and i didn't make any major change till then just installed and started telnet services in my linux box. I can still print from linux box to the local printers but not from the net. My smb.conf file looks like this if that can help

# Global parameters
[global]
workgroup = NET
netbios name = NET
server string = Samba Server
encrypt passwords = Yes
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*success fully*
unix password sync = Yes
log file = /var/log/samba/%m.log
max log size = 50
os level = 33
preferred master = True
domain master = True
dns proxy = No
hosts allow = 192.168.10. 127.
printing = lprng

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

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

[tmp]
comment = Temporary file space
path = /tmp
read only = No
guest ok = Yes

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

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

Please can someone help me with that. I'm new in linux and i am becoming affectionated with it but I have to restart to xp every two minutes for my friends to print.

[Rickead2000]

could you post the last few lines from your log files in /var/log/samba/ just after a failed printing attempt.

Linux will usually document quite clearly any failures and problems its experiences in its log files.

The file could be quite large, we're only interested in the last 5 - 10 lines, or anything that looks suspect.

[ardian]

In the location mentioned I found some log files with other network computer names. Here are some lines of those files:

[2003/10/13 22:10:15, 0] tdb/tdbutil.c:tdb_log(475)
tdb(/var/cache/samba/printing.tdb): rec_read bad magic 0xd9fee666 at offset=4868

or from another file

[2003/10/05 09:51:01, 0] lib/util_sock.c:send_smb(688)
Error writing 4 bytes to client. -1. (Connection reset by peer)
[2003/10/09 00:35:25, 0] smbd/service.c:make_connection(248)
a3 (192.168.10.64) couldn't find service ::{2227a280-3aea-1069-a2de-08002b30309d}
[2003/10/09 00:35:33, 0] smbd/service.c:make_connection(248)
a3 (192.168.10.64) couldn't find service ::{2227a280-3aea-1069-a2de-08002b30309d}

I hope for someone those lines means something :)
Thank you for your help Rickead2000

[Hayl]

are you using CUPS printers on the Linux box?

can you print from another Linux box over the network?

[adikgede]

Try adding the line use client driver = yes to your printer definition in smb.conf


# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
printable = yes
use client driver = yes


Dont forget to restart the service after you make changes to the configuration