[SOLVED] Trying to connect to my Linux attached Printer

Questions about cabled networking
Forum rules
Before you post please read how to get help
Indalecio
Level 1
Level 1
Posts: 7
Joined: Mon Jul 10, 2017 8:37 pm

[SOLVED] Trying to connect to my Linux attached Printer

Postby Indalecio » Mon Jul 10, 2017 9:07 pm

Linux Mint 18. I've got a Brother MFC 7360 printer thats attached to my LM18 PC. I've also got a laptop running Windows 10 which I'd like to share the printer to.

So far I've..
-Published Shared Printers attached to this system
--Allow Printing from the Internet

-Under Properties-> Policies, I've checked Enabled, Accepting Jobs, and Shared

Installed Samba
In smb.conf
set "guest ok = yes" under printers

In my windows 10 laptop, I can see my linux computer and if I type in http://10.0.0.152:631/printers/Brother-MFC-7360N,

Image

This is as far as I get. Not sure if the problem is on linux side or win10 side.

This is my smb.conf file.

Code: Select all

atoth@penguin /etc/samba $ cat 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
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# 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 = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = %h server (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

#### 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

# 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 = yes



#### 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 #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# 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

# 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 <<kahan@informatik.tu-muenchen.de> 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 unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

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

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or '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
# (this is Samba's default)
#   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

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe. 
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe. 
; add group script = /usr/sbin/addgroup --force-badname %g

############ 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

# 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

# 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

# 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
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = yes
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin
Last edited by Indalecio on Tue Jul 18, 2017 10:02 pm, edited 1 time in total.

User avatar
Pierre
Level 15
Level 15
Posts: 5871
Joined: Fri Sep 05, 2008 5:33 am
Location: Perth, AU.

Re: Trying to connect to my Linux attached Printer

Postby Pierre » Mon Jul 10, 2017 9:22 pm

is that connected via WiFi or by cable ?.
& you will need to install some extra drivers:
http://support.brother.com/g/b/download ... all&os=128

now, I'm not sure as to what order you have to install those files,
as I'm no longer using a Brother printer.

you can try the driver install first, but didn't work too well,
when I've used it, for my old Brother Printer.

so, then you will have to install the LPR,, CUPS,,
and again with the Scanner drivers.

do read their support notes:
http://support.brother.com/g/s/id/linux ... edirect=on
before you install anything.
Image
Please edit your original post title to include [SOLVED] - when your problem is solved!
and DO LOOK at those Unanswered Topics - - you may be able to answer some!.

Indalecio
Level 1
Level 1
Posts: 7
Joined: Mon Jul 10, 2017 8:37 pm

Re: Trying to connect to my Linux attached Printer

Postby Indalecio » Mon Jul 10, 2017 9:26 pm

Pierre wrote:is that connected via WiFi or by cable ?.
& you will need to install some extra drivers:
http://support.brother.com/g/b/download ... all&os=128

now, I'm not sure as to what order you have to install those files,
as I'm no longer using a Brother printer.

you can try the driver install first, but didn't work too well,
when I've used it, for my old Brother Printer.

so, then you will have to install the LPR,, CUPS,,
and again with the Scanner drivers.

do read their support notes:
http://support.brother.com/g/s/id/linux ... edirect=on
before you install anything.



Do I need to install the drivers on the Linux side or on the Win10 side? I can print just fine from the Linux side. I can scan with SANE. I'm just having problems connecting to the printer from Win10.

As to your question. The Win10 laptop is wireless, but the Linux PC is wired. Both are on the same ip network.

User avatar
Pierre
Level 15
Level 15
Posts: 5871
Joined: Fri Sep 05, 2008 5:33 am
Location: Perth, AU.

Re: Trying to connect to my Linux attached Printer

Postby Pierre » Tue Jul 11, 2017 3:30 am

yep - - that lot was for your Linux system.

so, on the win-10 - - have you used the driver disk, that came with that Printer,
- to install it's drivers ?.

typically, you tell the printers WiFi connection, the SSID & code for that IPs router,
and then the win-10 should detect that printer via the IP router.
Image
Please edit your original post title to include [SOLVED] - when your problem is solved!
and DO LOOK at those Unanswered Topics - - you may be able to answer some!.

Indalecio
Level 1
Level 1
Posts: 7
Joined: Mon Jul 10, 2017 8:37 pm

Re: Trying to connect to my Linux attached Printer

Postby Indalecio » Tue Jul 11, 2017 9:20 am

Pierre wrote:yep - - that lot was for your Linux system.

so, on the win-10 - - have you used the driver disk, that came with that Printer,
- to install it's drivers ?.

typically, you tell the printers WiFi connection, the SSID & code for that IPs router,
and then the win-10 should detect that printer via the IP router.


The printer doesn't have a WiFi connection. Its directly attached by USB to my Linux box.

User avatar
JerryF
Level 7
Level 7
Posts: 1643
Joined: Mon Jun 08, 2015 1:23 pm
Location: Rhode Island, USA

Re: Trying to connect to my Linux attached Printer

Postby JerryF » Tue Jul 11, 2017 9:36 am

Is the Linux computer, where your printer is connect to, on and running when you try to connect using Windows 10?
Don't forget to edit your original post and add [SOLVED] to the beginning of the Subject line if your problem has been fixed.
My main language is English. I speak very little Portuguese, and a whole lot of gibberish.

Indalecio
Level 1
Level 1
Posts: 7
Joined: Mon Jul 10, 2017 8:37 pm

Re: Trying to connect to my Linux attached Printer

Postby Indalecio » Tue Jul 11, 2017 9:41 am

JerryF wrote:Is the Linux computer, where your printer is connect to, on and running when you try to connect using Windows 10?


Yes. Its on and the Win10 machine can see its there, but when it tries to actually connect, it fizzles.

User avatar
JerryF
Level 7
Level 7
Posts: 1643
Joined: Mon Jun 08, 2015 1:23 pm
Location: Rhode Island, USA

Re: Trying to connect to my Linux attached Printer

Postby JerryF » Tue Jul 11, 2017 9:45 am

:(
Don't forget to edit your original post and add [SOLVED] to the beginning of the Subject line if your problem has been fixed.
My main language is English. I speak very little Portuguese, and a whole lot of gibberish.

Indalecio
Level 1
Level 1
Posts: 7
Joined: Mon Jul 10, 2017 8:37 pm

Re: Trying to connect to my Linux attached Printer

Postby Indalecio » Tue Jul 11, 2017 12:48 pm

Going to try looking at the logs for my firewall on the Win10 box. See if traffic is being blocked on port 631.

Indalecio
Level 1
Level 1
Posts: 7
Joined: Mon Jul 10, 2017 8:37 pm

Re: Trying to connect to my Linux attached Printer

Postby Indalecio » Tue Jul 11, 2017 9:16 pm

Not sure of the forum policy on double-posting and don't see any references to it in the forum rules..so..

Anyway, I opened port 631 on both TCP and UDP. This didn't solve the problem and I seemed to have made a discovery. The Win10 laptop doesn't seem to see my linux box anymore. It could in the past, but that seems to be in the past when I was installing/uninstalling Samba. I also tried two of the graphical frontends(drawing a blank on their names) along with it. Currently, all I have is vanilla Samba with the two front-ends I tried uninstalled. I reverted to a back-up copy of smb.conf while I was at it.

User avatar
Pierre
Level 15
Level 15
Posts: 5871
Joined: Fri Sep 05, 2008 5:33 am
Location: Perth, AU.

Re: Trying to connect to my Linux attached Printer

Postby Pierre » Tue Jul 11, 2017 9:37 pm

does that printer have an Ethernet Port ?.

ie: to connect both PCs & the printer to the same IP Router. ..
you can your internet via this router - - right ?.

you should be able to configure both PCs to see the printer via that LAN setup.
Image
Please edit your original post title to include [SOLVED] - when your problem is solved!
and DO LOOK at those Unanswered Topics - - you may be able to answer some!.

User avatar
Arch_Enemy
Level 5
Level 5
Posts: 544
Joined: Tue Apr 26, 2016 3:28 pm

Re: Trying to connect to my Linux attached Printer

Postby Arch_Enemy » Tue Jul 11, 2017 9:47 pm

Your printer should be attaching to your WiFi box with it's own WiFi built in, and then it broadcasts every so often.
NetBios in Windows should pick up these broadcasts and should connect through the WiFi router. Your computer has nothing to do with it, UNLESS your computer is supplying DNS information.
Your WiFi router should be set up for DNS by default. If you're using your computer for DNS, turn it off and use the DNS from the router.
I had no problems connecting to my Brother printer with anything, cell phones included.

Brother's Windows drivers should be able to see the printer through the WIFi router. If not, you have to manually enter the IP address of the printer.

Also, give the printer a STATIC address either way high up in the range or way down low. Most computers attach from the lowest to the highest. My guess is your Windows computer acquired an IP address when you first attached it to the network, and is maintaining that address, and when you set up the Brother printer you had the Windows computer turned off, and the printer acquired the same address. Since the printer is always "on" (even when it appears to be off) it holds the address. When you turn the Windows computer on, since the printer is dormant in sleep mode and not broadcasting, Windows takes over the IP address and therfore can't find the printer at it's assigned address.
$0.02+a grain of salt...

User avatar
Arch_Enemy
Level 5
Level 5
Posts: 544
Joined: Tue Apr 26, 2016 3:28 pm

Re: Trying to connect to my Linux attached Printer

Postby Arch_Enemy » Tue Jul 11, 2017 9:53 pm

Alternately, make sure the printer is ON (active) and broadcasting. Then turn on the Windows computer and click START=>RUN=>CMD, and then ipconfig /release all. It will tell you all IP information has been released. Just to make sure, start printing something from somewhere else to make sure the printer is attached, and then on the Windows computer enter ipconfig /renew. It will pick an IP address somewhere else in the range. Just hope it doesn't swipe some other device's IP address!

Assigning a static IP address to the printer is better, though. Just make sure nothing else is on that address.
$0.02+a grain of salt...

User avatar
JerryF
Level 7
Level 7
Posts: 1643
Joined: Mon Jun 08, 2015 1:23 pm
Location: Rhode Island, USA

Re: Trying to connect to my Linux attached Printer

Postby JerryF » Wed Jul 12, 2017 8:05 am

Indalecio wrote:Not sure of the forum policy on double-posting and don't see any references to it in the forum rules..so..

This wasn't a double post. Any information you find is helpful and posting it is good.

A double post is the exact message posted twice. :D
Don't forget to edit your original post and add [SOLVED] to the beginning of the Subject line if your problem has been fixed.
My main language is English. I speak very little Portuguese, and a whole lot of gibberish.

Indalecio
Level 1
Level 1
Posts: 7
Joined: Mon Jul 10, 2017 8:37 pm

Re: Trying to connect to my Linux attached Printer

Postby Indalecio » Tue Jul 18, 2017 10:01 pm

Ok. After dragging my heels forever, I went out and got a cheap 4 port switch and shared my computer's ethernet connection with my printer, assigned an ip address, subnet mask and gateway to it and was able to print a test page from both my Win10 laptop and Linux box.

Marking this one as solved.


Return to “Ethernet”