[Samba] windows 7 and printer sharing
Christophe Baegert
On a linux server with CUPS, I installed Samba to share it with windows
computers.
I managed to share it with my Macbook on MacOS 10.4, with this address : |
smb://login:password@name _of_server/name_of_printer|
So I think my server is well configured.
BUT I don't even see my network on a Windows 7 computer (I applied the
Maybe it's because it thinks it's on a public network ?
I use Linux for 10 years, but the last Windows computer I used was using
NT4, it was in 2003, so I'm really lost with this Windows 7 !!!
What can I do ? Even if the auto-detection doesn't work, is it possible
to use a simple manual address like I do with my Macbook ?
Thanks in advance !
-----------------------------------------------------------------
This is my 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.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#
#======================= Global Settings =======================
[global]
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = XXXXXXXX
# server string is the equivalent of the NT Description field
server string = %h server
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
hosts allow = 192.168.1.
#### Networking ####
interfaces = eth0
#### Debugging/Accounting ####
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 1
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
security = share
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n
*Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
pam password change = yes
########## Printing ##########
load printers = yes
printing = cups
printcap name = cups
[printers]
comment = All Printers
browseable = yes
path = /var/spool/samba
printable = yes
guest ok = yes
read only = yes
create mask = 0700
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = yes
---------------------------------------------------------------------------------
Regards,
Chris
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Jean-Jacques Moulis
CB> Hi,
CB> On a linux server with CUPS, I installed Samba to share it with windows
CB> computers.
CB> I managed to share it with my Macbook on MacOS 10.4, with this address : |
CB> smb://login:password@name _of_server/name_of_printer|
CB> So I think my server is well configured.
CB> BUT I don't even see my network on a Windows 7 computer (I applied the
In your case I wouldn't use smb for printing.
both OSX and windows (at least recent ones) can print directly to a CUPS
server.
the main advantage of SMB printing is automatic installation of drivers.
this is worth the trouble only if you have many clients.
(and to my knowledge it doesn't work with 64bits OS)
Use http://your.cups.server/printers/your_printername
to connect to your cups server.
--
Jean-Jacques Moulis Tel: (013) 281684
ISY Fax: (013) 139282
Linköping University E-mail: j...@isy.liu.se
581 83 Linköping
Christophe Baegert
Le 05/01/2010 13:03, Jean-Jacques Moulis a écrit :
> In your case I wouldn't use smb for printing.
> both OSX and windows (at least recent ones) can print directly to a CUPS
> server.
IPP never worked on my Macbook using OS X 10.4, which works well with Samba.
But I didn't try it on the Windows 7 computer, I'll try that, if it
works, indeed, Samba isn't necessary !!! Thank you for your help.
Regards,
Chris
Lennart Sorensen
> IPP never worked on my Macbook using OS X 10.4, which works well with Samba.
Odd, given I remember Mac OS X 10.1 automatically detecting the IPP
broadcasts by cups (which cups was set to share printers with the network,
which it doesn't by default). Apple is even funding cups these days.
As long as your print server with cups is configured to share with the
local network, and not firewalling it away it should work.
> But I didn't try it on the Windows 7 computer, I'll try that, if it
> works, indeed, Samba isn't necessary !!! Thank you for your help.
I have certainly used IPP printing with windows.
use the url:
http://printerserver:631/printers/print_queue_name
And install the right driver of course.
Of course cups should be configured to handle unknown job types as raw
(which I think is normally the default these days as well).
--
Len Sorensen
Kevin Keane
Ryan Suarez
> the main advantage of SMB printing is automatic installation of drivers.
> this is worth the trouble only if you have many clients.
> (and to my knowledge it doesn't work with 64bits OS)
>
We run 64bit vista and windows clients. They work fine with samba. You
can either upload 64bit drivers to the server or take advantage of point
and print behaviour:
<snip>
"if Point and Print does not find an appropriate driver on the print
server, it will attempt to find and install a driver with the correct
file name from the local driver cab or driver store. The ability to look
in the local driver cab is new starting with Windows XP"
http://www.microsoft.com/windowsserver2003/techinfo/overview/pointandprint.mspx
</snip>
So by uploading a driver from a windows 32bit clients local repository
to the samba server, 64bit client will automatically use the same driver
from their local store. This was the easiest route for us.
Ryan Suarez
> BUT I don't even see my network on a Windows 7 computer (I applied the
What happens when you click 'start' and '\\name_of_samba_server' on
search bar?
What version of samba are you running?