Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
HOWTO CUPS+Samba: printing from Windows & Linux
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, ... 9, 10, 11  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
vdboor
Guru
Guru


Joined: 03 Dec 2003
Posts: 592
Location: The Netherlands

PostPosted: Tue Jan 06, 2004 12:48 pm    Post subject: Reply with quote

Sorry for bothering you.. I've solved the problem I've just asked here.. ..and I've installed the printer in windowxp/vmware.. 8) whoa.

I had to download the file called "Adobe Universal PostScript Windows Driver Installer 1.0.6 - English", and unzip it. the cupsaddsmb -v -a command failed, because it missed a few files..

thanks for this great tutorial. :D
_________________
The best way to accelerate a windows server is by 9.81M/S²
Linux user #311670 and Yet Another Perl Programmer

[ screenies | Coding on KMess ]
Back to top
View user's profile Send private message
tj
Apprentice
Apprentice


Joined: 10 Aug 2002
Posts: 199
Location: tokyo, japan

PostPosted: Sat Jan 10, 2004 6:06 pm    Post subject: Reply with quote

this howto worked brilliantly for me first time so my eternal thanks to daff :)

that said, I now need help - my 2 gentoo boxes + 1 win2k laptop + 1 winXP laptop all play fine on this home network (using the same workgroup, not domain) - this particular gentoo box has the usb printer attached and the other comps see and print to it fine

now my question - I recently added a mac powerbook to the mix running os-x 10.2.8 - used the same workgroup and username - it sees the network and the printer but won't connect

I can mount shares as gentoo root from the powerbook but that is it, however, I have no problems mounting the win2k/XP shares from the powerbook and vice-versa

I can also browse the mac share from gentoo as a regular user but can't write files

so, my question is, what am I missing? the biggest thing is access to the printer, though music would be a (non-)essential second

all constructive suggestions appreciated

tj
_________________
I tried installing Suse Linux off the Internet. It got stuck in the middle somewhere.Installing off the Internet is for the birds.
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Sun Jan 11, 2004 12:13 am    Post subject: Reply with quote

tj wrote:
this howto worked brilliantly for me first time so my eternal thanks to daff :)

That's nice to hear :D
tj wrote:

that said, I now need help - my 2 gentoo boxes + 1 win2k laptop + 1 winXP laptop all play fine on this home network (using the same workgroup, not domain) - this particular gentoo box has the usb printer attached and the other comps see and print to it fine

now my question - I recently added a mac powerbook to the mix running os-x 10.2.8 - used the same workgroup and username - it sees the network and the printer but won't connect

I can mount shares as gentoo root from the powerbook but that is it, however, I have no problems mounting the win2k/XP shares from the powerbook and vice-versa

I can also browse the mac share from gentoo as a regular user but can't write files

so, my question is, what am I missing? the biggest thing is access to the printer, though music would be a (non-)essential second

all constructive suggestions appreciated

tj


I'm sorry, don't know much about MacOS and connecting to specific shares with it, but doesn't MacOX 10.1 (or so) has CUPS installed by default? So when you have CUPS running on the Powerbook just do a little configuration (don't know exactly what is needed for MacOS, but try starting CUPS and connecting to http://localhost:631 on the Powerbook) to it and it should see the printer on the print server (and be able to print to it).

That's at least what I've seen on the Powerbook of a guy for whom I installed a NetBSD firewall for his home network.
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.
Back to top
View user's profile Send private message
TriGuN
n00b
n00b


Joined: 18 Aug 2003
Posts: 71
Location: Boca Raton, FL

PostPosted: Sun Jan 11, 2004 3:53 am    Post subject: Reply with quote

Hmm...I can't get this to work right. Everything appears to work fine but whe n I right click on the printer, and click "connect", it asks to download the driver and then fails and says it couldn't download the driver.

I used the CUPS drivers but I found your documentation a teeny bit confusing. If ya can help out, I would greatly appreciate it, thanks. :)
_________________
-Steve Bularca-
-NeoturbineNET IRC-
http://neoturbine.net:8000/irc
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Sun Jan 11, 2004 12:15 pm    Post subject: Reply with quote

TriGuN wrote:
Hmm...I can't get this to work right. Everything appears to work fine but whe n I right click on the printer, and click "connect", it asks to download the driver and then fails and says it couldn't download the driver.

Hm, normally (if everything works correctly) when clicking "connect", Windows will download the drivers and connect quite silently, not notifying you or asking for permission at all.

Seems that something with the drivers on the server side didn't work out right, or maybe the Samba share definitions/configuration contain a flaw. It might help if you post the revlevant parts of your smb.conf ([$print], [PRINTERNAME] and [printers]).
TriGuN wrote:

I used the CUPS drivers but I found your documentation a teeny bit confusing. If ya can help out, I would greatly appreciate it, thanks. :)

Well you could tell me what part you found confusing and I can try to explain it to you as good as I can.
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.
Back to top
View user's profile Send private message
TriGuN
n00b
n00b


Joined: 18 Aug 2003
Posts: 71
Location: Boca Raton, FL

PostPosted: Sun Jan 11, 2004 8:26 pm    Post subject: Reply with quote

Code:

[print$]
   comment = Printer Drivers
   path = /etc/samba/printer
   guest ok = no
   browseable = yes
   read only = yes
   write list = @adm,steve,root
                                                                               
[HPPSC1210]
        comment = HP PSC 1210 Network Printer
        path = /var/spool/samba
        browseable = no
        public = yes
        guest ok = yes
        writable = no
        printable = yes
        printer admin = root

[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
   printer admin = root
# to allow user 'guest account' to print.
   guest ok = yes
   writable = no
   printable = yes
   create mode = 0700
# =====================================
# print command: see above for details.
# =====================================
   print command = lpr -P %p -o raw %s -r   # using client side printer drivers.
;   print command = lpr -P %p %s # using cups own drivers (use generic PostScript on clients).
# The following two commands are the samba defaults for printing=cups
# change them only if you need different options:
;   lpq command = lpq -P %p
;   lprm command = cancel %p-%j


I honestly don't know why it's not working, afaik, I did everything according to the docs :)

*edit*
It seems to work if I install the AdobePS drivers on my laptop, but since you recommend the CUPS drivers, I'd rather use those. The only thing is, I don't know how to uninstall the AdobePS drivers now :(
_________________
-Steve Bularca-
-NeoturbineNET IRC-
http://neoturbine.net:8000/irc
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Sun Jan 11, 2004 9:37 pm    Post subject: Reply with quote

TriGuN wrote:
Code:

[print$]
   comment = Printer Drivers
   path = /etc/samba/printer
   guest ok = no
   browseable = yes
   read only = yes
   write list = @adm,steve,root


This seems ok. Do you have printing = cups and printcap name = cups in your [global] section (and do you have something 'unusual' defined in there? :))?
TriGuN wrote:
Code:

[HPPSC1210]
        comment = HP PSC 1210 Network Printer
        path = /var/spool/samba
        browseable = no
        public = yes
        guest ok = yes
        writable = no
        printable = yes
        printer admin = root

This seems ok, too. Maybe you could add @adm and steve to the printer admin = entry, just for the sake of consistency.
TriGuN wrote:
Code:

[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
   printer admin = root
# to allow user 'guest account' to print.
   guest ok = yes
   writable = no
   printable = yes
   create mode = 0700
# =====================================
# print command: see above for details.
# =====================================
   print command = lpr -P %p -o raw %s -r   # using client side printer drivers.
;   print command = lpr -P %p %s # using cups own drivers (use generic PostScript on clients).
# The following two commands are the samba defaults for printing=cups
# change them only if you need different options:
;   lpq command = lpq -P %p
;   lprm command = cancel %p-%j


I honestly don't know why it's not working, afaik, I did everything according to the docs :)

The only thing I don't think I like here (which may or may not be part of the problem) is the print command = entry. As far as I know this is no needed when using Samba with CUPS for printing. Maybe try commenting that out and restarting both Samba and CUPS? But don't quote me on that, might be total BS :)
TriGuN wrote:

*edit*
It seems to work if I install the AdobePS drivers on my laptop, but since you recommend the CUPS drivers, I'd rather use those. The only thing is, I don't know how to uninstall the AdobePS drivers now :(

Yeah well, the AdobePS drivers "only" locally set you up a generic PostScript printer, suggesting Windows that the network printer (the HPPSC1210 you have) is really directly connected to the laptop. Not quite the "right" thing when you want to use a print server (but it is quite certain that it'd work, when all else fails).

I also don't know how to uninstall those drivers, but wouldn't Windows fetch the drivers from the print server again (if they are different from the local copies it got the first time you clicked 'connect') when you do a new right-click-'connect' to the printer? Just a thought...would be interesting to know.

What is the cupsaddsmb command line and you used? Can you post it along with the output it produces?
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.
Back to top
View user's profile Send private message
TriGuN
n00b
n00b


Joined: 18 Aug 2003
Posts: 71
Location: Boca Raton, FL

PostPosted: Sun Jan 11, 2004 9:53 pm    Post subject: Reply with quote

Yeah..when I click "connect" again, It just uses the AdobePS drivers again :(

Here is the [global]:
Code:

[global]
                                                                                                         
# 1. Server Naming Options:
# workgroup = NT-Domain-Name or Workgroup-Name
   workgroup = MSHOME
                                                                                                         
# netbios name is the name you will see in "Network Neighbourhood",
# but defaults to your hostname
;  netbios name = <name_of_this_server>
                                                                                                         
# server string is the equivalent of the NT Description field
   server string = Samba Server %v
                                                                                                         
# Message command is run by samba when a "popup" message is sent to it.
# The example below is for use with LinPopUp:
; message command = /usr/bin/linpopup "%f" "%m" %s; rm %s
                                                                                                         
# 2. Printing Options:
# CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   printcap name = cups
   load printers = yes
                                                                                                         
# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx, cups
   printing = cups
                                                                                                         
# Samba 2.2 supports the Windows NT-style point-and-print feature. To
# use this, you need to be able to upload print drivers to the samba
# server. The printer admins (or root) may install drivers onto samba.
# Note that this feature uses the print$ share, so you will need to
# enable it below.
# This parameter works like domain admin group:
# printer admin = @<group> <user>
;   printer admin = @adm
                                                                                                         
# 3. Logging Options:
# this tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m
                                                                                                         
# Put a capping on the size of the log files (in Kb).
   max log size = 50
                                                                                                         
# Set the log (verbosity) level (0 <= log level <= 10)
; log level = 3
                                                                                                         
# 4. Security and Domain Membership Options:
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page. Do not enable this if (tcp/ip) name resolution does
# not work for all the hosts in your network.
;   hosts allow = 192.168.1. 192.168.2. 127.
                                                                                                         
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest
                                                                                                         
# Security mode. Most people will want user level security. See
# security_level.txt for details.
   security = user
# Use password server option only with security = server or security = domain
# When using security = domain, you should use password server = *
;   password server = <NT-Server-Name>
;   password server = *
                                                                                                         
# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
;  password level = 8
;  username level = 8
                                                                                                         
# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
# Encrypted passwords are required for any use of samba in a Windows NT domain
# The smbpasswd file is only required by a server doing authentication, thus
# members of a domain do not need one.
  encrypt passwords = yes
  smb passwd file = /etc/samba/private/smbpasswd

# The following are needed to allow password changing from Windows to
# also update the Linux system password.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
#        the encrypted SMB passwords. They allow the Unix password
#        to be kept in sync with the SMB password.
;  unix password sync = Yes
;  passwd program = /usr/bin/passwd %u
;  passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n
;*passwd:*all*authentication*tokens*updated*successfully*
                                                                                                         
# Unix users can map to different SMB User names
;  username map = /etc/samba/smbusers
                                                                                                         
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /etc/samba/smb.conf.%m

# Options for using winbind. Winbind allows you to do all account and
# authentication from a Windows or samba domain controller, creating
# accounts on the fly, and maintaining a mapping of Windows RIDs to unix uid's
# and gid's. winbind uid and winbind gid are the only required parameters.
#
# winbind uid is the range of uid's winbind can use when mapping RIDs to uid's
;  winbind uid = 10000-20000
#
# winbind gid is the range of uid's winbind can use when mapping RIDs to gid's
;  winbind gid = 10000-20000
#
# winbind separator is the character a user must use between their domain
# name and username, defaults to "\"
;  winbind separator = +
#
# template homedir determines the home directory for winbind users, with
# %D expanding to their domain name and %U expanding to their username:
;  template homedir = /home/%D/%U
#
# template shell determines the shell users authenticated by winbind get
;  template shell = /bin/bash
                                                                                                         
# 5. Browser Control and Networking Options:
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
   socket options = TCP_NODELAY
                                                                                                         
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24
   interfaces = eth0
                                                                                                         
# Configure remote browse list synchronisation here
#  request announcement to, or browse list sync from:
#       a specific host or from / to a whole subnet (see below)
;   remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
;   remote announce = 192.168.1.255 192.168.2.44

# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
;   local master = no
                                                                                                         
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33
                                                                                                         
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
;   domain master = yes
                                                                                                         
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;   preferred master = yes
                                                                                                         
# 6. Domain Control Options:
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations or Primary Domain Controller for WinNT and Win2k
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat
                                                                                                         
# Where to store roaming profiles for WinNT and Win2k
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U
                                                                                                         
# Where to store roaming profiles for Win9x. Be careful with this as it also
# impacts where Win2k finds it's /HOME share
; logon home = \\%L\%U\.profile
                                                                                                         
# The add user script is used by a domain member to add local user accounts
# that have been authenticated by the domain controller, or by the domain
# controller to add local machine accounts when adding machines to the domain.
# The script must work from the command line when replacing the macros,
# or the operation will fail. Check that groups exist if forcing a group.
# Script for domain controller for adding machines:
; add user script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false -M %u
# Script for domain member for adding local accounts for authenticated users:
; add user script = /usr/sbin/useradd -s /bin/false %u
                                                                                                         
# Domain groups:
# domain admin group is a list of unix users or groups who are made members
# of the Domain Admin group
; domain admin group = root @wheel

#
# domain guest groups is a list of unix users or groups who are made members
# of the Domain Guests group
; domain guest group = nobody @guest
                                                                                                         
# 7. Name Resolution Options:
# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast
                                                                                                         
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes
                                                                                                         
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#       Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one  WINS Server on the network. The default is NO.
;   wins proxy = yes
                                                                                                         
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
   dns proxy = no
                                                                                                         
# 8. File Naming Options:
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
;  preserve case = no
;  short preserve case = no
# Default case is normally upper case for all DOS files
;  default case = lower
# Be very careful with case sensitivity - it can break things!
;  case sensitive = no
                                                                                                         
# Enabling internationalization:
# you can match a Windows code page with a UNIX character set.
# Windows: 437 (US), 737 (GREEK), 850 (Latin1 - Western European),
# 852 (Eastern Eu.), 861 (Icelandic), 932 (Cyrillic - Russian),
# 936 (Japanese - Shift-JIS), 936 (Simpl. Chinese), 949 (Korean Hangul),
# 950 (Trad. Chin.).
# UNIX: ISO8859-1 (Western European), ISO8859-2 (Eastern Eu.),
# ISO8859-5 (Russian Cyrillic), KOI8-R (Alt-Russ. Cyril.)
# This is an example for french users:
;   client code page = 850
;   character set = ISO8859-1


And the cupsaddsmb output:

Code:

gentoo steve # cupsaddsmb -H gentoo -U root -h gentoo -v -a
Password for root required to access gentoo via SAMBA:
Running command: smbclient //gentoo/print\$ -N -U'root%######' -c 'mkdir W32X86;put /var/spool/cups/tmp/4001c5b2961fb W32X86/printer.PPD;put /usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
added interface ip=192.168.1.129 bcast=192.168.1.255 nmask=255.255.255.0
Domain=[MSHOME] OS=[Unix] Server=[Samba 2.2.8a]
NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
putting file /var/spool/cups/tmp/4001c5b2961fb as \W32X86/printer.PPD (1458.4 kb/s) (average 1458.4 kb/s)
/usr/share/cups/drivers/ADOBEPS5.DLL does not exist
/usr/share/cups/drivers/ADOBEPSU.DLL does not exist
/usr/share/cups/drivers/ADOBEPSU.HLP does not exist
 
Running command: rpcclient gentoo -N -U'root%#####' -c 'adddriver "Windows NT x86" "printer:ADOBEPS5.DLL:printer.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
cmd = adddriver "Windows NT x86" "printer:ADOBEPS5.DLL:printer.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"
result was NT_STATUS_UNSUCCESSFUL
 
Running command: rpcclient gentoo -N -U'root%#####' -c 'setdriver printer printer'
cmd = setdriver printer printer
Succesfully set printer to driver printer.
 
gentoo steve #


Hope this helps :)
_________________
-Steve Bularca-
-NeoturbineNET IRC-
http://neoturbine.net:8000/irc


Last edited by TriGuN on Wed Aug 04, 2004 3:25 am; edited 1 time in total
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Sun Jan 11, 2004 10:19 pm    Post subject: Reply with quote

Hm your [global] section looks quite ok! As for the AdobePS driver on the laptop, how do you tell they are still being used?

But as you can see, cupsaddsmb doesn't do what it should do, failing with "/usr/share/cups/drivers/ADOBEPS5.DLL does not exist". This usually means you have not installed the CUPS drivers correctly so they do not reside in /usr/share/cups/drivers and cupsaddsmb tries to use the AdobePS drivers instead (the default is to first look for the CUPS files, then for the Adobe drivers).

Have you downloaded the drivers from the CUPS web site? And installed them with the included install script?
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.
Back to top
View user's profile Send private message
TriGuN
n00b
n00b


Joined: 18 Aug 2003
Posts: 71
Location: Boca Raton, FL

PostPosted: Sun Jan 11, 2004 10:24 pm    Post subject: Reply with quote

Ah whoops. I must have skipped that step. I know the laptop is still using the AdobePS drivers because when I right click and view the printer properties, under "advanced", it says "Driver: AdobePS" :)

*edit*
Okay so I install the CUPS drivers, as shown here:
Code:

gentoo root # ls /usr/share/cups/drivers
cups5.hlp  cupsdrv5.dll  cupsui5.dll
gentoo root #


And I run the cupsaddsmb command again, and I get the same output as before:

Code:

gentoo root # cupsaddsmb -H gentoo -U root -h gentoo -v -a
Password for root required to access gentoo via SAMBA:
Running command: smbclient //gentoo/print\$ -N -U'root%####' -c 'mkdir W32X86;put /var/spool/cups/tmp/4001cd4fc4f8b W32X86/printer.PPD;put /usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
added interface ip=192.168.1.129 bcast=192.168.1.255 nmask=255.255.255.0
Domain=[MSHOME] OS=[Unix] Server=[Samba 2.2.8a]
NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
putting file /var/spool/cups/tmp/4001cd4fc4f8b as \W32X86/printer.PPD (18957.1 kb/s) (average 18959.0 kb/s)
/usr/share/cups/drivers/ADOBEPS5.DLL does not exist
/usr/share/cups/drivers/ADOBEPSU.DLL does not exist
/usr/share/cups/drivers/ADOBEPSU.HLP does not exist
 
Running command: rpcclient gentoo -N -U'root%####' -c 'adddriver "Windows NT x86" "printer:ADOBEPS5.DLL:printer.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
cmd = adddriver "Windows NT x86" "printer:ADOBEPS5.DLL:printer.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"
result was NT_STATUS_UNSUCCESSFUL
 
Running command: rpcclient gentoo -N -U'root%####' -c 'setdriver printer printer'
cmd = setdriver printer printer
Succesfully set printer to driver printer.
 
gentoo root #


*edit again*
Okay It appears I was able to get rid of the AdobePS drivers by deleting the printer from the "Printers and Faxes" on the laptop. Now when I try to connect to the print server, it says "you are about to install a printer which will automatically download a driver blah blah", so I hit OK, and then it says "the server does not have the correct driver installed blah blah"

:(
_________________
-Steve Bularca-
-NeoturbineNET IRC-
http://neoturbine.net:8000/irc


Last edited by TriGuN on Wed Aug 04, 2004 3:11 am; edited 2 times in total
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Sun Jan 11, 2004 10:41 pm    Post subject: Reply with quote

Hm. This gives me an idea: what version of CUPS are you using? If it is less than 1.1.20, please upgrade. The CUPS drivers of the new version all have a '5' in the filename, as you can see. The drivers of CUPS 1.1.19 and below don't. So the cupsaddsmb command of CUPS 1.1.19 looks for the files that are named cups.hlp, cupsdrv.dll and cupsui.dll. It can't find them, because you use the newer drivers with and older CUPS installation.

If this is not the problem, I'll have to think of something else :)

PS: -U'root%******' I hope that's not your REAL root password :)
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.


Last edited by daff on Wed Aug 04, 2004 6:28 am; edited 1 time in total
Back to top
View user's profile Send private message
TriGuN
n00b
n00b


Joined: 18 Aug 2003
Posts: 71
Location: Boca Raton, FL

PostPosted: Sun Jan 11, 2004 10:45 pm    Post subject: Reply with quote

I believe you are right my friend.

Code:

*  net-print/cups
      Latest version available: 1.1.19-r1
      Latest version installed: 1.1.19-r1
      Size of downloaded files: 3,604 kB
      Homepage:    http://www.cups.org
      Description: The Common Unix Printing System


but 1.1.19 is the stable version. I guess I'll just use ~x86 and get 1.1.20 :)
_________________
-Steve Bularca-
-NeoturbineNET IRC-
http://neoturbine.net:8000/irc
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Sun Jan 11, 2004 10:49 pm    Post subject: Reply with quote

I use 1.1.20 on my main FreeBSD box without problems at all, I believe it's fairly stable and safe to use. If you don't want to use the unstable package, you can try to find the old CUPS drivers here or here.
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.
Back to top
View user's profile Send private message
TriGuN
n00b
n00b


Joined: 18 Aug 2003
Posts: 71
Location: Boca Raton, FL

PostPosted: Sun Jan 11, 2004 10:51 pm    Post subject: Reply with quote

nah don't worry I'm compiling 1.1.20 as we speak :) and I'll let you know how everything goes :)
_________________
-Steve Bularca-
-NeoturbineNET IRC-
http://neoturbine.net:8000/irc
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Sun Jan 11, 2004 10:54 pm    Post subject: Reply with quote

Very well :) I'll be around for another hour or two I think.
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.
Back to top
View user's profile Send private message
TriGuN
n00b
n00b


Joined: 18 Aug 2003
Posts: 71
Location: Boca Raton, FL

PostPosted: Sun Jan 11, 2004 11:02 pm    Post subject: Reply with quote

And it works perfectly!!! Thanks a lot man, you saved me a lot of hassle :D

I printed a test page and it even showed the cups drivers instead of the adobePS drivers, so we're sure it's not using those :)

Just curious, are printers automatically started when CUPS is started?

*edit* also, is there a way to not have to log in when I go to "\\printserver" on my laptop? :)
_________________
-Steve Bularca-
-NeoturbineNET IRC-
http://neoturbine.net:8000/irc
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Sun Jan 11, 2004 11:18 pm    Post subject: Reply with quote

Great to hear! :D

Do you mean that CUPS will turn on the printer if it is offline/powered off? I don't know, but I think not. If it's online/powered on though, it will of course load the ppd and the drivers and all.

For not having to log in: add another user on the printserver, just like the printer user I believe you created according to the guide, and give this user the same name and password as he has on your Windows system (odd that you don't have that already? That was one of the first things I did when I started using Samba). That way, Windows will send the username/password combination you use to log into your Windows system and both will match on the printserver. No need for manually supplying username and password thus.
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.
Back to top
View user's profile Send private message
TriGuN
n00b
n00b


Joined: 18 Aug 2003
Posts: 71
Location: Boca Raton, FL

PostPosted: Mon Jan 12, 2004 12:05 am    Post subject: Reply with quote

What I meant was, when you go to http://localhost:631 , and you go to printers, there is a button that says "Start Printer" or "Stop Printer". I was just wondering if it is automatically started when CUPS is started :)

And Thanks again :D
_________________
-Steve Bularca-
-NeoturbineNET IRC-
http://neoturbine.net:8000/irc
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Mon Jan 12, 2004 12:18 am    Post subject: Reply with quote

TriGuN wrote:
What I meant was, when you go to http://localhost:631 , and you go to printers, there is a button that says "Start Printer" or "Stop Printer". I was just wondering if it is automatically started when CUPS is started :)

And Thanks again :D

Uh, yeah, I think CUPS starts the printers automatically.

No problem, glad to have helped :)
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.
Back to top
View user's profile Send private message
TriGuN
n00b
n00b


Joined: 18 Aug 2003
Posts: 71
Location: Boca Raton, FL

PostPosted: Mon Jan 12, 2004 2:10 am    Post subject: Reply with quote

Um...the user on laptop has a space in it [my full name] ...How do I add that in the samba config? :)

*edit*
Ah n/m. If you set security = share in [global], you won't have to log in at all either :)
_________________
-Steve Bularca-
-NeoturbineNET IRC-
http://neoturbine.net:8000/irc
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Mon Jan 12, 2004 10:38 pm    Post subject: Reply with quote

Good to know, since the system wont let you have a space in your username, and Samba, which has no problems with spaces, requires that its usernames match with the ones in the /etc/passwd file.
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.
Back to top
View user's profile Send private message
VanDan
Guru
Guru


Joined: 30 Sep 2002
Posts: 586
Location: Australia

PostPosted: Fri Jan 23, 2004 1:07 am    Post subject: Margin problems Reply with quote

I followed the instructions in the original post, and ( after adding a 'root' account on the NT4 domain controller ) the 'cupsaddsmb' thing added my printers and the downloaded CupsSamba drivers to my samba setup. Good how-to, by the way!

I then went into the network neighbourhood and clicked on my samba server, clicked 'connect' and the drivers were downloaded and the printer set up properly.

However ... the margins are very wrong. Test pages on both my Laserjet 4500 and Ricoh Aficio AP3200 start *way* too far down the page, and the Laserjet4500 also starts *way* too far to the right.

I should note now that I am using the correct ppd files, downloaded from the LinuxPrinting site ( HP ) and the Ricoh site ( Aficio ). Both printers' margin setups are *perfect* under Linux - the cups test pages appear in exactly the right place.

I have looked at the ppd files that Windows is downloading, and they are the same ( respective ) ones I have working under CUPS.

There are no windows-client options for setting up the margins.

Anyone know what the problem is?
Back to top
View user's profile Send private message
daff
Apprentice
Apprentice


Joined: 02 Jul 2003
Posts: 232
Location: Vienna, Austria

PostPosted: Fri Jan 23, 2004 7:51 pm    Post subject: Re: Margin problems Reply with quote

VanDan wrote:

I have looked at the ppd files that Windows is downloading, and they are the same ( respective ) ones I have working under CUPS.

There are no windows-client options for setting up the margins.

Anyone know what the problem is?


Sounds odd, never heard of that before...you say everything works fine under Linux? Also when printing from Linux to the print server?

Can you not access any properties or printer options on the Windows clients before printing? I.e. accessing the print server via \\printserver and then opening 'Printers', right-clicking on (one of) the printer(s) and clicking 'Properties'. There's a property window with some tabs (General, Sharing, Ports, Advanced, etc). Opening 'Advanced' and there 'Printing Defaults'. Again an 'Advanced' button, and there are at least some options to configure (Paper size maybe).

That's all I can think of ATM.

Maybe someone else knows more?
_________________
Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.
Back to top
View user's profile Send private message
Ateo
Advocate
Advocate


Joined: 02 Jun 2003
Posts: 2019
Location: Earth

PostPosted: Tue Jan 27, 2004 12:37 am    Post subject: Reply with quote

Thanks for post a MOST useful printing HOWTO....

Regards
Back to top
View user's profile Send private message
TriGuN
n00b
n00b


Joined: 18 Aug 2003
Posts: 71
Location: Boca Raton, FL

PostPosted: Wed Jan 28, 2004 5:16 am    Post subject: Reply with quote

Okay, well, I sold that computer, and I'm trying to setup this again on my new server. Unfortunately, it doesn't work. Linux to linux printing does work, just not windows to linux (from my laptop).

the laptop just complains about the server not having the correct drivers installed blah blah.

My SMB.conf: http://steve.neoturbine.net:8000/smb.conf

eh? :(

*edit*
The cupsaddsmb command did not report anything particularly bad, and it did copy the 3 cups drivers to /usr/share/cups/drivers, and yes, I am using cups 1.1.20 :)

Here's the cupsaddsmb output:

Code:

neoturbine root # cupsaddsmb -a -v
Password for root required to access localhost via SAMBA:
Running command: smbclient //localhost/print\$ -N -U'root%<censored>' -c 'mkdir W32X86;put /var/spool/cups/tmp/40181d62afad6 W32X86/hp_psc_1210.ppd;put /usr/share/cups/drivers/cupsdrv5.dll W32X86/cupsdrv5.dll;put /usr/share/cups/drivers/cupsui5.dll W32X86/cupsui5.dll;put /usr/share/cups/drivers/cups5.hlp W32X86/cups5.hlp'
added interface ip=192.168.1.10 bcast=192.168.1.255 nmask=255.255.255.0
Domain=[MSHOME] OS=[Unix] Server=[Samba 2.2.8a]
NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
putting file /var/spool/cups/tmp/40181d62afad6 as \W32X86/hp_psc_1210.ppd (19093.8 kb/s) (average 19095.7 kb/s)
putting file /usr/share/cups/drivers/cupsdrv5.dll as \W32X86/cupsdrv5.dll (8553.1 kb/s) (average 8872.6 kb/s)
putting file /usr/share/cups/drivers/cupsui5.dll as \W32X86/cupsui5.dll (8245.9 kb/s) (average 8596.4 kb/s)
putting file /usr/share/cups/drivers/cups5.hlp as \W32X86/cups5.hlp (13899.0 kb/s) (average 8684.8 kb/s)

Running command: rpcclient localhost -N -U'root%<censored>' -c 'adddriver "Windows NT x86" "hp_psc_1210:cupsdrv5.dll:hp_psc_1210.ppd:cupsui5.dll:cups5.hlp:NULL:RAW:NULL"'
cmd = adddriver "Windows NT x86" "hp_psc_1210:cupsdrv5.dll:hp_psc_1210.ppd:cupsui5.dll:cups5.hlp:NULL:RAW:NULL"
result was NT_STATUS_UNSUCCESSFUL

Running command: rpcclient localhost -N -U'root%<censored>' -c 'setdriver hp_psc_1210 hp_psc_1210'
cmd = setdriver hp_psc_1210 hp_psc_1210
Succesfully set hp_psc_1210 to driver hp_psc_1210.

neoturbine root #


:(
_________________
-Steve Bularca-
-NeoturbineNET IRC-
http://neoturbine.net:8000/irc


Last edited by TriGuN on Wed Jan 28, 2004 8:59 pm; edited 3 times in total
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3, ... 9, 10, 11  Next
Page 2 of 11

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum