Find the answer to your Linux question:
Results 1 to 2 of 2
I have a Canon MX 870 Wireless printer that works with Windows XP. My linux box was able t detect the same printer with USB cable connected., and also was ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Newbie
    Join Date
    Aug 2009

    Unable to connect to my Canon MX870 WinXP Wireless printer with linux

    I have a Canon MX 870 Wireless printer that works with Windows XP. My linux box was able t detect the same printer with USB cable connected., and also was able to print from Linux. Linux box is using Samba.. When I try to print without USB cable or in the wireless mode, I get. Message "connecting", but It never seems to connect, and no page prints. Here is the output of smbclient -L mywindowsxpcomputername -N

    frank frank # smbclient -L franksdesktop -N
    Domain=[FRANKSDESKTOP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
    	Sharename       Type      Comment
    	---------       ----      -------
    	IPC$            IPC       Remote IPC
    	print$          Disk      Printer Drivers
    	SharedDocs      Disk      
    	CanonMX8        Printer   Canon MX870 series FAX
    	Printer3        Printer   Microsoft Office Document Image Writer
    	Printer4        Printer   Canon MX870 series Printer
    	Printer5        Printer   Broderbund PDF Creator
    	Printer2        Printer   Microsoft XPS Document Writer
    	Printer         Printer   PaperPort Image Printer
    Domain=[FRANKSDESKTOP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
    	Server               Comment
    	---------            -------
    	Workgroup            Master
    	---------            -------
    I hope this does not reveal any info that comprimises security on XP system.

    And here is where I am least confident I have configured correctly. /etc/samba/smb.conf

    This is the main Samba configuration file. You should read the
    # smb.conf(5) manual page in order to understand the options listed
    # here. Samba has a huge number of configurable options (perhaps too
    # many!) most of which are not shown in this example
    # For a step to step guide on installing, configuring and using samba, 
    # read the Samba-HOWTO-Collection. This may be obtained from:
    # Many working examples of smb.conf files can be found in the 
    # Samba-Guide which is generated daily and can be downloaded from: 
    # Any line which starts with a ; (semi-colon) or a # (hash) 
    # is a comment and is ignored. In this example we will use a #
    # for commentry and a ; for parts of the config file that you
    # may wish to enable
    # NOTE: Whenever you modify this file you should run the command "testparm"
    # to check that you have not made any basic syntactic errors. 
    #======================= Global Settings =====================================
       printcap name = cups
       printing      = cups
    # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
       workgroup = PATINOHOME 
    # server string is the equivalent of the NT Description field
       server string = Samba Server
    # Security mode. Defines in which mode Samba will operate. Possible 
    # values are share, user, server, domain and ads. Most people will want 
    # user level security. See the Samba-HOWTO-Collection for details.
       security = user
    # 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
       hosts allow = 192.168.1. 192.168.2. 127.
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
       load printers = yes
    # you may wish to override the location of the printcap file
    ;   printcap name = /etc/printcap
    # on SystemV system setting printcap name to lpstat should allow
    # you to automatically obtain a printer list from the SystemV spool
    # system
    ;   printcap name = lpstat
    # It should not be necessary to specify the print system type unless
    # it is non-standard. Currently supported print systems include:
    # bsd, cups, sysv, plp, lprng, aix, hpux, qnx
    ;   printing = cups
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    ;  guest account = pcguest
    # 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
    # Use password server option only with security = server
    # The argument list may include:
    #   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    # or to auto-locate the domain controller/s
    #   password server = *
    ;   password server = <NT-Server-Name>
    # Use the realm option only with security = ads
    # Specifies the Active Directory realm the host is part of
    ;   realm = MY_REALM
    # Backend to store user information in. New installations should 
    # use either tdbsam or ldapsam. smbpasswd is available for backwards 
    # compatibility. tdbsam requires no further configuration. If you're 
    # migrating from < samba 3.4, you'll have to convert your old user 
    # passwords to the new backend with the command:
    # pdbedit -i smbpasswd:/var/lib/samba/private/smbpasswd -e
    ;   passdb backend = tdbsam
    # 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.
    # Note: Consider carefully the location in the configuration file of
    #       this line.  The included file is read at that point.
    ;   include = /etc/samba/smb.conf.%m
    # 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 = 
    # Browser Control Options:
    # 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
    # Enable this if you want Samba to be a domain logon server for 
    # Windows95 workstations. 
    ;   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 roving profiles (only for Win95 and WinNT)
    #        %L substitutes for this servers netbios name, %U is username
    #        You must uncomment the [Profiles] share below
    ;   logon path = \\%L\Profiles\%U
    # 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 default is NO.
       dns proxy = no 
    # These scripts are used on a domain controller or stand-alone 
    # machine to add or delete corresponding unix accounts
    ;  add user script = /usr/sbin/useradd %u
    ;  add group script = /usr/sbin/groupadd %g
    ;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
    ;  delete user script = /usr/sbin/userdel %u
    ;  delete user from group script = /usr/sbin/deluser %u %g
    ;  delete group script = /usr/sbin/groupdel %g
    #============================ Share Definitions ==============================
       comment = Home Directories
       browseable = no
       writable = yes
    # Un-comment the following and create the netlogon directory for Domain Logons
    ; [netlogon]
    ;   comment = Network Logon Service
    ;   path = /var/lib/samba/netlogon
    ;   guest ok = yes
    ;   writable = no
    ;   share modes = no
    # Un-comment the following to provide a specific roving profile share
    # the default is to use the user's home directory
    ;    path = /var/lib/samba/profiles
    ;    browseable = no
    ;    guest ok = yes
    # NOTE: If you have a BSD-style print system there is no need to 
    # specifically define each individual printer
       comment = All Printers
       path = /var/spool/samba
       browseable = no
    # Set public = yes to allow user 'guest account' to print
       guest ok = no
       writable = no
       printable = yes
       public    = yes
       printer name = Printer4 
    # This one is useful for people to share files
    ;   comment = Temporary file space
    ;   path = /tmp
    ;   read only = no
    ;   public = yes
    # A publicly accessible directory, but read only, except for people in
    # the "staff" group
    ;   comment = Public Stuff
    ;   path = /home/samba
    ;   public = yes
    ;   writable = yes
    ;   printable = no
    ;   write list = @staff
    # Other examples. 
    # A private printer, usable only by fred. Spool data will be placed in fred's
    # home directory. Note that fred must have write access to the spool directory,
    # wherever it is.
    ;   comment = Fred's Printer
    ;   valid users = fred
    ;   path = /homes/fred
    ;   printer = freds_printer
    ;   public = no
    ;   writable = no
    ;   printable = yes
    # A private directory, usable only by fred. Note that fred requires write
    # access to the directory.
    ;   comment = Fred's Service
    ;   path = /usr/somewhere/private
    ;   valid users = fred
    ;   public = no
    ;   writable = yes
    ;   printable = no
    # a service which has a different directory for each machine that connects
    # this allows you to tailor configurations to incoming machines. You could
    # also use the %U option to tailor it by user name.
    # The %m gets replaced with the machine name that is connecting.
    ;  comment = PC Directories
    ;  path = /usr/pc/%m
    ;  public = no
    ;  writable = yes
    # A publicly accessible directory, read/write to all users. Note that all files
    # created in the directory by users will be owned by the default user, so
    # any user with access can delete any other user's files. Obviously this
    # directory must be writable by the default user. Another user could of course
    # be specified, in which case all files would be owned by that user instead.
    ;   path = /usr/somewhere/else/public
    ;   public = yes
    ;   only guest = yes
    ;   writable = yes
    ;   printable = no
    # The following two entries demonstrate how to share a directory so that two
    # users can place files there that will be owned by the specific users. In this
    # setup, the directory should be writable by both users and should have the
    # sticky bit set on it to prevent abuse. Obviously this could be extended to
    # as many users as required.
    ;   comment = Mary's and Fred's stuff
    ;   path = /usr/somewhere/shared
    ;   valid users = mary fred
    ;   public = no
    ;   writable = yes
    ;   printable = no
    ;   create mask = 0765
    In the following Cups printer setup for this printer I did the following.:

    Add Printer
    Local Printers: 	SCSI Printer
    Discovered Network Printers: 	
    Other Network Printers: 	Internet Printing Protocol (http)
    Internet Printing Protocol (ipp)
    LPD/LPR Host or Printer
    Internet Printing Protocol (https)
    Windows Printer via SAMBA
    AppSocket/HP JetDirect
    Backend Error Handler
    I chose Windows Printer via SAMBA

  2. #2
    Linux Newbie
    Join Date
    Aug 2009
    Solved. The main problem I think was in the CUPS page. Or where I was making a mistake just after the following CUPS menu choices.

    dd Printer
    Local Printers: 	SCSI Printer
    Discovered Network Printers: 	
    Other Network Printers: 	Internet Printing Protocol (http)
    Internet Printing Protocol (ipp)
    LPD/LPR Host or Printer
    Internet Printing Protocol (https)
    Windows Printer via SAMBA
    AppSocket/HP JetDirect
    Backend Error Handler
    I chose Windows Printer via Samba but did not know how to enter the correct address., in the next step. Since I am connected through a router, (Netgear), I logged into my Netgear router setup page, to see what ip address was for my XP computer. I also knew from: smbclient -L mycomputersxpname -N, that my pritner was called Printer4. I also had not created a print user as suggested by cups. I don't know if that also contributed to the problem. So here is the entry that worked.:
    smb://198.168.x.x/Printer4 . My test page from cups is clear but slightly off center. In other words is is not a perfect page, but I am pleased with just being able to connect to my wireless printers. Several links, I found made it sound much more complicated that it was. Either Gentoo is getting more user friendly and or easier or I am getting better, or both. For my particular Canon MX 870, I had to emerge, samba, Gutenprint, and Cups. At first I also thought I would need a wireless card n my Gentoo box or computer, but had my netgear router do the wireless connection for both my Linux box as it was already doing for my Windows XP computer.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts