Are you a spammer

Please note, that the first 3 posts you make, will need to be approved by a forum Administrator or Moderator before they are publicly viewable.
Each application to join this forum is checked at the Stop Forum Spam website. If the email or IP address appears there when checked, you will not be allowed to join this forum.
If you get past this check and post spam on this forum, your posts will be immediately deleted and your account inactivated.You will then be banned and your IP will be submitted to your ISP, notifying them of your spamming. So your spam links will only be seen for an hour or two at most. In other words, don't waste your time and ours.

This forum is for the use and enjoyment of the members and visitors looking to learn about and share information regarding the topics listed. It is not a free-for-all advertising venue. Your time would be better spent pursuing legitimate avenues of promoting your websites.

Printer Driver Install Problem-[SOLVED]

Help & support for Ultimate Edition 2.7


Printer Driver Install Problem-[SOLVED]

Postby EFH » Wed Jul 28, 2010 9:24 am

I have a network attached Brother MFC-8460N printer, and am trying out Ultiame Editition 2.7 on a USB stick. I downloaded the Brother supplied brmfc8460nlpr-2.0.1-1.i386.deb file clicked on it, gdebi came up and installed it properly. I then downloaded the Brother supplied cupswrapperMFC8460N-2.0.1-2.i386-1.deb file and it failed to install. I have not figured out how to cut and paste the error from the terminal window but in gdebi-gtk window buit the relevant part of the terminal says:

/usr/local/Brother/cupswrapper/cupswrapperMFC8460N-2.0.1: 64: cannot create /share/cups/model/MFC8460N.ppd: Directory nonexistant

Looking around the file system, the "model" part of the tree does not exist, and the file manager window does not seem to have a mechanism of creating a subdirectory so that I can copy the .ppd file and run the install. I have the Brother supplied .ppd file in the download directory.

I didn't find any posts related to this problem on this forum, but on the Ubuntu forum I saw some issues with possibly not being a superuser? All I did was boot up from the USB...

I'm trying linux out for the 1st time, and trying to determine if I can get away from MS Vista. I have no clue what to do with linux problems if point and click stuff doesn't work... Help~!
User avatar
EFH
U.E. Newbie
U.E. Newbie
 
Posts: 7
Joined: Wed Jul 28, 2010 8:48 am
Operating System: Ultimate Edition 3.4 64 BIT



Re: Printer Driver Install Problem

Postby Admin-Amir » Wed Jul 28, 2010 10:07 am

Hello EFH and welcome to the U.E Forum.

First I will Advice you to Upgrade your Kernel (you have here on the forum the Guide).
Then you can install all the support packages from synaptic for your printer.
under search in synaptic=>Brother.
you will find there the packages like:

Brother -cups- wrapper-common
brother-lpr-drivers-common
Ptouch-driver

Then you will need to add support for your USB => USB mount,Mount manager.
you will need to install detection for your printer.
I will need some more info from synaptic for what you have install on support and what you did not have install.
you can add attach screen shots from the tab down here in the post (upload attachment).

please post back for me the screen shots for search in synaptic for:
USB
Printer
Admin-Amir
 



Re: Printer Driver Install Problem

Postby EFH » Wed Jul 28, 2010 4:29 pm

Thanks for the reply! Still no luck. Here is what I have done so far. I installed UE2.7 on the hard disk, so that I can ignore the USB issue and focus on just the printer installation problem. Everything was updated during the installation process.

Via Synaptic Package Manager I searched for Brother as you recommended and located and successfully installed:
brother-lpr-drivers-common
brother-cups-wrapper-common
This did not enable the network printer.

I then downloaded the driver files for the MFC-8460N from the Brother web site and attempted to install with the following results:
brmfc8460nlpr-2.0.1-1.i386.deb installed properly
cupswrapperMFC8460N-2.0.1-2.i386.deb filed to install as before - see snapshot1.png.
snapshot1.png
Snapshot1 of the failed cupswrapper install.


Per your request I have attached 3 snapshots from Synaptic Package Manager:
First is screenshot2.png, showing all of the "installed" Brother packages, even though the cupswrapper for this model of printer did not install properly.
snapshot2.png
Snapshot2 is the installed Brother packages

Next are 3 snapshots of everything that is found when searching for "printer".
snapshot3.png
Snapshot3 thru snapshot5 is of the installed printer packages

snapshot4.png

snapshot5.png


The .PPD supplied by Brother is in the download folder. Let me know if you need anything else. Thanks for the help! EFH
User avatar
EFH
U.E. Newbie
U.E. Newbie
 
Posts: 7
Joined: Wed Jul 28, 2010 8:48 am
Operating System: Ultimate Edition 3.4 64 BIT



Re: Printer Driver Install Problem

Postby Admin-Amir » Wed Jul 28, 2010 4:43 pm

Hello EFH.

Thank you for the screen shots , it looks like you have cover more that you need :D
OK , now you need to share from samba the printer on your Network.
make sure that you have the samba installed on your system , then you can make the share from there.
I just hope that the USB support was installed too.
About the PPD well yes you need to install it too.
let me know After you get the share in samba if that work for you.
BTW - You will need to get the share in Printers - there you will see the icon for the Network Printer share.
Please Upgrade your Kernel to 2.6.34 - you have Guide here in the Forum How To do it safe.

And some info for you to see the big picture of how to get it to work:

https://help.ubuntu.com/community/Netwo ... WithUbuntu
http://www.ossramblings.com/samba_push_windows_drivers
https://help.ubuntu.com/10.04/servergui ... urity.html
http://www.watchingthenet.com/enable-fi ... samba.html

Have you both "shared" and "published" the printer?

Share:
Administration > Printing > Right Click the attached printer > Properties > Policies > Check Enabled, Accepting Jobs, and Shared

Publish:
Administration > Printing > Server > Settings > Check "Publish Shared Printers connected to this system"


one thing important is to make sure that you have add to your user all the permission on all the options there:
System > Administration > Users and Groups > Manage Groups >properties > make sure you're a member on all groups.
Admin-Amir
 



Re: Printer Driver Install Problem

Postby EFH » Wed Jul 28, 2010 5:01 pm

I used Ubuntu software Center to install Samba. It complained at the end of the install about the invalid .ppd directory (same as when installing the cupswrapper) but Samba seems to be operating. When I add a share for the Brother network printer, what directory should I browse to? EFH

One other thing... the multifunction printer is directly attached to the ethernet network with a static IP address. It is not attached to any computer.

Also, how do I determine if USB was set up properly during the install? Can I assume that since I burned an .ISO image to a USB stick, booted the stick, got WiFi running, and installed from the stick to the disk, that USB support is already installed? EFH
Last edited by EFH on Wed Jul 28, 2010 5:24 pm, edited 1 time in total.
User avatar
EFH
U.E. Newbie
U.E. Newbie
 
Posts: 7
Joined: Wed Jul 28, 2010 8:48 am
Operating System: Ultimate Edition 3.4 64 BIT



Re: Printer Driver Install Problem

Postby Admin-Amir » Wed Jul 28, 2010 5:20 pm

EFH,

please look here on this page and try to follow the steps there.
http://www.uluga.ubuntuforums.org/showt ... ?p=9186842

Navigated to /var/spool and created a 'lpd' directory to correct the missing path then re-ran the driver install successfully.



Code: Select all
cd /usr/share/cups
sudo mkdir model






here you have How To - share looks like on samba:

root@Merlin:/etc/samba# uname -a
Linux Merlin 2.6.24-24-generic #1 SMP Sat Aug 22 01:06:14 UTC 2009 i686 GNU/Linux

CUPSD.CONF
LogLevel warning
SystemGroup lpadmin
Port 631
Listen /var/run/cups/cups.sock
Browsing On
BrowseOrder allow,deny
BrowseAllow all
BrowseAddress @LOCAL
DefaultAuthType none
<Location />
Order allow,deny
Allow all
</Location>
<Location /admin>
Order allow,deny
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
Order allow,deny
</Location>
<Policy default>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType none
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
BrowseLocalProtocols cups dnssd lpd smb


SMB.CONF
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# 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 most of which
# are not shown in this example
#
# 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 commentary 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 =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = BFF

# server string is the equivalent of the NT Description field
server string = Merlin (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
; wins support = no

# 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

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
printing = cups
printcap name = cups
load printers = yes

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
interfaces = 127.0.0.0/8 eth0
interfaces = 192.168.1.105 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = true



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
; syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
; security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

obey pam restrictions = yes

; guest account = nobody
invalid users = root

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how nsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
; logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
; logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ Misc ############

# 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 = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
; domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
path = /var/spool/samba/
printable = yes
create mask = 0700
guest ok = yes
read only = no
valid users = root,loy
admin users = root,loy
invalid users =
guest account =
hosts allow = *

[hploy]
comment = hploy
guest ok = yes
path = /var/spool/samba
writeable = no
printer admin = loy
create mask = 0700
printable = yes
printer name = hploy


# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers/
guest ok = yes
read only = no
valid users = loy,root
admin users = loy,root
username = loy
invalid users =
guest account = l
Hosts allow = 192.168.*.*
Admin-Amir
 



Re: Printer Driver Install Problem

Postby EFH » Wed Jul 28, 2010 6:42 pm

I'm quickly getting over my head... I tried setting the symbolic links as suggest in one of the posts, and got the error in the following snapshot. I'm not sure this was relevant as it was for the scanner aspect of the multifunction printer. I'm still working on just getting it to print. Scanning is a future subject...

I have no idea what the Samba text file is in your last reply, or what to do with it.

In the system administration printing menu, I can add the printer, but get an error every time I try to print a test page. When I click the printer and look at the printer properties policies - the enabled box is not checked which explains why the printer is not being found. When I try to check the box and apply, it sits for a moment and then refreshes the window and continues to indicate that it is not enabled.

the attached snapshot show the printer policies window and the error when I tried to follow the directions in the forum. I still think the cupwrapper install problem is the real problem. Trying to enable the printer, share and so on is probably fruitless until the driver actually installs properly. How do I back this stuff out and start from scratch, and what procedures should I use?

Appreciate the help....
EFH
Attachments
snapshot6.png
User avatar
EFH
U.E. Newbie
U.E. Newbie
 
Posts: 7
Joined: Wed Jul 28, 2010 8:48 am
Operating System: Ultimate Edition 3.4 64 BIT



Re: Printer Driver Install Problem

Postby Admin-Amir » Wed Jul 28, 2010 9:47 pm

EFH,

From your attach you can see that the server was not started yet.
You need to start the server + you have to add the Network printer to the printer that you have there.
you can see that you did not published the printer on the server.
This is way it will not start for you.
The log that I have post for you was to show you how the log on your machine should look like.
to use the printer that you have now ,use the XSane.
it is visual and you can configure your printer/scanner.
Admin-Amir
 



Re: Printer Driver Install Problem

Postby EFH » Thu Jul 29, 2010 9:33 am

Got it to work as follows:

Go back to a clean system:
delete all jobs from the print queue
delete the mis-installed printer
open System/Administration/Synaptic Package Manager to do a complete removal of
brmfc8460nlpr
cupswrappermfc8460n

Download from the brother web site:
brmfc8460nlpr-2.0.1-1.i386.deb
cupswrapperMFC8460N-2.0.1-2.i386.deb

- open System/Administration/Synaptic Package Manager and install "csh"
- plug in and turn on printer
- click to install brmfc8460nlpr-2.0.1-1.i386.deb file in the download directory
- open Applications/System Tools/Konsole terminal, enter "sudo nautilus" and passowrd, click File System and browse to "usr/share/cups" directory, create a "model" directory, and keep nautilus open.
- Install the cupswrapperMFC8460N-2.0.1-2.i386.deb file. Watch in nautilus to ensure the MFC8460N.PPD file is created in there.
- open System/Administration/Printing and up comes the printer dialog box.
- click add new printer.
- click on network printer, and wit for it to scan the network and find the printer.
- 2 versions of the MFC8460N appear, select the "LPD network printer via DNS-SD", click forward and it tries to find drivers. The process fails and offers to add a .ppd file, choose this option and then click to browse for the .ppd file that was made in "usr/share/cups/model directory and the printer driver installs.
- print a test page, and it works.

It appears the Brother supplied driver won't install without the "Models" directory (and there needs to be a .ppd file in it), and the URI version of the printer is the wrong one.

Thanks for the help! Now its on to getting scanning and faxing to work...

EFH
User avatar
EFH
U.E. Newbie
U.E. Newbie
 
Posts: 7
Joined: Wed Jul 28, 2010 8:48 am
Operating System: Ultimate Edition 3.4 64 BIT


Return to Ultimate Edition 2.7

Who is online

Users browsing this forum: No registered users and 2 guests