Printing from WinXP to Samba/Linux (Continuing from getting it to print to begin with -- lol)



Okay...

So we have the Photosmart D5160 working and printing -- and on demand, at
that, with no special requirements. It mounts thumbdrives and SD cards
through the printer as /dev/sda1 and it will talk with our new Kodak
Easyshare C7-hundred-something with no problems.

So it's great.

I can even map the printer in Windows XP as \\ip-address\printername
through CUPS/Samba on the linux box, but I can't print to it. I get an
error, or at least I used to until I tried doing it tonight (and of
course, no error, it just sits there with the document in the queue (and
the printer is not paused)).

/etc/cups/cupsd.conf shows the following (I didn't see anything else that
would prevent network use but will gladly post the entire file if
necessary)

# Show shared printers on the local network. Browsing On BrowseOrder
allow,deny
BrowseAllow @LOCAL

/etc/samba/smb.conf (commented lines removed) Follows.

Any help appreciated, as always...

=====================================================================
[global]
printing = cups
printcap name = cups
load printers = yes
guest account = samba-user
security = share
workgroup = MSHOME
server string = Samba %v at %h
hosts allow = 192.168.10. 127.
interfaces = 192.168.10.9
syslog only = no
syslog = 0;
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096
SO_RCVBUF=4096
encrypt passwords = true
wins support = yes
os level = 34
domain master = yes
local master = yes
preferred master = yes
name resolve order = lmhosts host wins bcast
dns proxy = yes
preserve case = yes
short preserve case = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
max log size = 1000

[homes]
comment = Home Directories
browseable = no
read only = no
create mask = 0755
directory mask = 0755

[printers]
comment = All Printers
browseable = yes
path = /home/smbprint
printable = yes
public = yes
writable = yes
create mode = 0700
guest only = yes
use client driver = yes
; above line suggested by tldp howtos - win + debprint
guest account = smbprint

[pub]
comment = share directory 3775 root:src
browseable = yes
create mode = 0640
directory mask = 0750
writable = yes
locking = yes
path = /gen-sambashare
public = yes

[cdrom]
comment = Samba server's CD-ROM
writable = no
locking = no
path = /cdrom
public = yes
preexec = /bin/mount /cdrom
postexec = /bin/umount /cdrom
=====================================================================

--
CJ Chitwood, posting a long time ago as Circuit Breaker
To reply via e-mail, sink theship.

.



Relevant Pages

  • samba and cups
    ... I have a probleme with printing from windows-Machines to Printers connect at ... I have a cups-server vor the network printer and different cups-server for ... BrowseOrder allow,deny ...
    (Debian-User)
  • Re: Locking linked Word documents
    ... printing" under Tools/Options/Print to control this issue. ... > The slides aren't given to the printing company - only the document. ... The Word doc will prompt to ask if you want to update the ... the commercial printers could print ...
    (microsoft.public.office.misc)
  • Re: Access 97 vs Later Version
    ... are off-topic and there are printing newsgroups. ... Accept that as a limitation of Windows or Printers, then you can move on to ... No-one reasonably uses dot matrix nowadays so ... > There is an official report. ...
    (microsoft.public.access.devtoolkits)
  • Comparing different models
    ... Recto-verso printing will be rarely used, since the photocopier's recto-verso can be used instead. ... BTW, last time I carefully dived into devices specs, world was divided between ink jet printers with a printing resolution roughly equal to 300 dpi, and laser printers with a printing resolution going from 600 to 1200 dpi for the most expansive models. ...
    (comp.periphs.printers)
  • Re: Lexmark Inkjets and TS
    ... Some day we may indeed have to go with one of the third pary printing ... Microsoft should really solve this ... > printers are harder and harder to find. ... > The best compatibity list is here: ...
    (microsoft.public.windows.terminal_services)