Announcement

**Snowhog** · Nov 15, 2009, 01:33 PM

Re: Kubuntu as print server, Vista client

Dated, but may provide insight - Re: Printer Sharing between Ubuntu and Vista
and the link it points to - Printer Sharing: Windows Print Server for Suse/openSUSE Linux Clients

**plant17** · Nov 16, 2009, 01:05 PM

Re: Kubuntu as print server, Vista client

Thanks Snowhog, I will look into it. It seems that my problem is Samba, but most of the how too's are written in language beyond me. I will plough on through and see what I can do.

John

**plant17** · Nov 17, 2009, 02:51 PM

Re: Kubuntu as print server, Vista client

I have looked into all the samba self helps and I feel I am doing the right thing

when I go to network on the vista PC I see my Linux machine
Select it and I see "Printers"
Select Printers and I get a long wait with and endlessly slow green bar advancing across the top address bar and nothing happens.
My Printer works properly, the CUPS printer management area at http://localhost:631 shows the printer as

DCP145C (Idle, Accepting Jobs, Shared, Server Default)

Trying to add it via he Administration tab as a windows printer is not working because I don't know how to find the device URI

I have add its locationa s usb://Brother/ DCP145C

it still doesn't work

smb://192.168.26.102/brother4800 was the example given

where can I find the IP number, the field maked Location is blank

Thanks

John

**monte48lowes** · Nov 17, 2009, 06:38 PM

Re: Kubuntu as print server, Vista client

Have you tried:

http://192.168.26.102:631 from the windows machine?

I will play with the wife's laptop here later tonight, it's running vista as well.

Mike

**plant17** · Nov 18, 2009, 10:33 AM

Re: Kubuntu as print server, Vista client

Thanks for taking the time Mike,

I think things are getting away from me a bit here. When you say try http://192.168.26.102:631, do you mean just plug it into the browser, if so I get the error message.

The connection has timed out

The server at 192.168.26.102 is taking too long to respond.

* The site could be temporarily unavailable or too busy. Try again in a few
moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

I really think my Samba is not working. All of the advice I have read on the smb.conf is completely baffling. I have a smb.conf file with so much stuff in it I don't know where to start. If you manage to get anything on your wifes Vista, just post the whole config file and I will copy it into mine. (If thats OK with you of course). The CUPS page at http://localhost:631 on the linux machine is also baffling.

Whatever the results thanks for the help.

John

**monte48lowes** · Nov 18, 2009, 09:01 PM

Re: Kubuntu as print server, Vista client

I am on the wife's laptop. I was able to add the printer and print a test page. An interesting note, while I was adding the printer the windows print dialog popped up and the title bar stated "Printer blah blah access denied".

It did print a test page. Let me go back to the desktop and check the samba config file.

Mike

**monte48lowes** · Nov 18, 2009, 09:14 PM

Re: Kubuntu as print server, Vista client

Code:

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

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

# What naming service and in what order should we use to resolve host names
# to IP addresses
;  name resolve order = lmhosts host wins bcast

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

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

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

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

########## 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
security = share
restrict anonymous = no
domain master = no
logon home = \\%25N\%25U
logon path = \\%25N\%25U\profile

#======================= 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
browseable = no
path = /var/spool/samba
printable = 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

[MUSIC]
path = /home/michael/Music
guest ok = yes

[MY PICTURES]
path = /home/michael/43/Files/P/My Pictures/
guest ok = yes
read only = no
follow symlinks = no
wide links = no

That's the whole file. Don't know how helpful that will be. I am running Jaunty on the desktop. (Too much to work with for an upgrade at this time.)

Mike

**plant17** · Nov 19, 2009, 11:51 AM

Re: Kubuntu as print server, Vista client

Thanks again Mike,

There were quite a few small differences in the smb.config so I just copied yours over.

We are getting somewhere.
Linux machine has access to Public folder on Vista PC
In Network I have my Linux machine visible
When I select it I see two icons: Printers and DCP-145C my printer, good.
Select DCP-145C and get Windows Printer installation box, inside is the green bar and "connecting to DCP-145C on Linux-Laptop, after a thoughtful paused I recieve the following message:

"Windows cannot connect to the printer. Operation could not be completed (error 0x000006be)"

According to the microsoft site:

"On a client that is running Windows Vista or Windows Server 2008, you try to connect to a print queue that is hosted on Windows Server 2003, on Windows XP, or on Windows 2000 Server. When you do this, the connection to the printer cannot be established."

Which has nothing to do with me.

There is then some more stuff that doesn't seem relavant to my case and then:

"Note The "0x000006be" error code indicates that the remote procedure call failed. "

So I tried the other icon.

It waits for ages and then, nothing.

I have decide my Samba is pretty good, but maybe the problem is printing from Windows to a CUPS printer server??

Saw Bonjour mentioned but am not sure if I need to load yet another piece of in between ware.

Your thoughts

John?

**skunk** · Nov 19, 2009, 12:18 PM

Re: Kubuntu as print server, Vista client

Originally posted by plant17

"Windows cannot connect to the printer. Operation could not be completed (error 0x000006be)"

According to the microsoft site:

"On a client that is running Windows Vista or Windows Server 2008, you try to connect to a print queue that is hosted on Windows Server 2003, on Windows XP, or on Windows 2000 Server. When you do this, the connection to the printer cannot be established."

Which has nothing to do with me.

It well may have something to do with you if the samba protocol stack is emulating the "older" SMB authentication method present in previous versions of Windows.

**skunk** · Nov 19, 2009, 12:24 PM

Re: Kubuntu as print server, Vista client

Perhaps this blog may help

http://www.builderau.com.au/blogs/co...tm?p=339270746

**plant17** · Nov 19, 2009, 01:17 PM

Re: Kubuntu as print server, Vista client

Thamks Skunk,

Been to that blog already and got no joy. I followed the following advice

If you're running a version of Vista that cannot use secpol.msc, you can edit the registry instead. Just change the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa\LMCompatibilityLevel from a 3 to a 1.

But stiil no change.

I am new to this and I am afraid:

"if the samba protocol stack is emulating the "older" SMB authentication method present in previous versions of Windows."

doesnt mean anything to me, sorry.

John

**Detonate** · Nov 19, 2009, 01:30 PM

Re: Kubuntu as print server, Vista client

Open the cups interface, select the printer and choose to "Modify" the printer. Make sure the block is checked to share the printer. Also this is an excellent example of why one should use static IP's on a network. If using DHCP. and the IP of the printer's host machine changes, you will lose your ptinter. If you Right click on the printer in the cups interface, and select properties it will show the address of the printer. Mine looks like this.

http://localhost:631/printers/Brother-HL-1240-series

When installing the printer in Windows select the option to install a network printer and use the address substituting the IP of the host computer for "localhost". Mine looks like this

http://192.168.1.10:631/printers/Brother-HL-1240-series

Windows will then find and install the printer.

I know this works in XP, but I've no experience with Vista. But it should work.

**plant17** · Nov 20, 2009, 11:46 AM

Re: Kubuntu as print server, Vista client

Thanks for your input detonate but I am afraid that nothing is working.

When I select Add a printer the Printer on the Linux machine is there, but if I try to connect I get the same old

"Windows cannot connect to the printer. Operation could not be completed (error 0x000006be)"

message.

If I try "Select a shared printer by name" and enter http/:192.168.0.158/printers/DCP145C

I get "Windows cannot connect to the printer. Make sure you have typed the name correctly, and that the printer is connected to the network"

Tried add a printer using a TCP/IP address or hostname and got a lot of stuff back saying the printer could not be found.

All becoming too difficult. Does anyone actually have a Linux computer acting as a print server to a PC with Vista Home Premium that works? If so tell me your secrets.

John

**Detonate** · Nov 20, 2009, 11:55 AM

Re: Kubuntu as print server, Vista client

Are you sure you have marked the Printer as "Shared" If so I think you may have a firewall problem. Try it with the firewall disabled.

Announcement

Kubuntu as print server, Vista client

Kubuntu as print server, Vista client

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment