PDA

View Full Version : Ubuntu Desktop and Sharing printers with XP


SawtheLight
16th January 2007, 03:53
Hi all,

I have installed ubuntu 6.10 desktop on amy home machine which when it had xp was also a wirless print server.

I have installed samba and can see the workgroup in the Network properties on the xp desktop/laptops. In ubuntu 1 have click share my printer, i have modified the smb file for cups and permission = users
What happens; (XP)
Add a new printer.
Go through wizard and input server.
eg: \\hmsrv\dj990c
A Uname/pword dialog appears. I type the username and correct password and it fails to connect. I type hmsrv\user1, & pword and fails to connect. I created a 'user' and put it in the user group.

I am missing something. but WHAT....

Thanks in anticipation.:confused: :confused:

martinfst
16th January 2007, 09:34
Did you allow the printer to be shared on your winXP system? Can you print from other windows boxes to this attached printer?

sjau
16th January 2007, 10:56
You are trying to share the printer from your ubuntu computer right?
And WinXP tries to access it through the ubuntu computer?

If so, could you please post your /etc/samba/smb.conf file?

martinfst
16th January 2007, 11:07
Right, maybe I read the post of SawtheLight incorrect. :(

Maybe the question is to use a printer on his system, which he migrated from XP to Ubuntu? In that case, installing a package like CUPS should be able to handle printers directly connected to a Linux system.

sjau
16th January 2007, 11:39
I'm not sure but I think the printer is attached to the ubuntu box and he wants to connect with winxp to it...

SawtheLight
16th January 2007, 23:24
I'm not sure but I think the printer is attached to the ubuntu box and he wants to connect with winxp to it...

Correct, thanks for the replys, i will post the conf file tonight, when i get the chance to play with it.

Printer is attached to ubuntu box, want to connect 2 winxp clients and print.
:confused:
Is there any '99% you have missed' settings which i can try? Before i tax too many brains with my ignorance.

Thanks

SawtheLight
16th January 2007, 23:27
Right, maybe I read the post of SawtheLight incorrect. :(

Maybe the question is to use a printer on his system, which he migrated from XP to Ubuntu? In that case, installing a package like CUPS should be able to handle printers directly connected to a Linux system.

I have cups installed, it is with the basic install of edgy eft; otherwise is the a 'higher' level of cups i need to connect with win xp? Although i am sure my problem is with samba permissions.

sjau
17th January 2007, 02:16
Did you use SWAT to setup samba?

(1) Install swat:

sudo apt-get install swat


(2) Add to /etc/services

swat 901/tcp #SWAT


(3) Add to /etc/inetd.conf (if necessary):

swat stream tcp nowait.400 root /usr/sbin/swat swat


Depending on your version it could also be /etc/xinted.conf instead of /etc/inted.conf

Add to /etc/xomted.conf (if necessary)

includedir /etc/xinetd.d


(4) Create/Alter /etc/xinetd.d/swat to:

# default: on
# description: SWAT is the Samba Web Admin Tool. Use swat \
# to configure your Samba server. To use SWAT, \
# connect to port 901 with your favorite web browser.
service swat
{
port = 901
socket_type = stream
wait = no
only_from = localhost
user = root
server = /usr/sbin/swat
log_on_failure += USERID
disable = no
}


(5) Restart xinetd

service xinetd restart


(6) Connect to SWAT throuth http://localhost:901
--> Root must be activated and you must login as root to get access.

SawtheLight
17th January 2007, 02:54
Thanks will try this tonight...

Is this a SAMBA config tool?
EdIT: Thanks - i can read now - YES IT IS

sjau
17th January 2007, 08:18
Did it work?
I used swat the first time I setup samba (and have ever since copied the smb.conf that it created) :)

SawtheLight
17th January 2007, 11:07
You are trying to share the printer from your ubuntu computer right?
And WinXP tries to access it through the ubuntu computer?

If so, could you please post your /etc/samba/smb.conf file?
+++ Abridged version ++++

[global]

## Browsing/Identification ###

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

# 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


# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0


; 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

# Put a capping on the size of the log files (in Kb).
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

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

# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .


# 'passwd program'. The default is 'no'.
; pam password change = no

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

# 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

# When using [print$], root is implicitly a 'printer admin', but you can
# also give this right to other users to add drivers and set printer
# properties
printer admin = @lpadmin


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

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

; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &


# 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

#======================= 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, \\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
; valid users = %S

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

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

# 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

# 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
; writable = no
; 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 = /tmp
printable = yes
public = no
writable = no
create mode = 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.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
; write list = root, @ntadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; writable = no
; locking = no
; path = /cdrom
; public = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
+++go for it - correct away+++:confused:

SawtheLight
17th January 2007, 11:10
Did it work?
I used swat the first time I setup samba (and have ever since copied the smb.conf that it created) :)

The service wont restart - unknown command???
But most was good except i had to create the swat file.

Thanks

;)

SawtheLight
17th January 2007, 11:56
I can not connect to it :mad:
Followed you instructions; all things in right place.
How do i start firefox as root
"sudo -h firefox"?

sjau
17th January 2007, 12:03
To enable root enter this in the shell:


sudo passwd root


That will then set a password for root and then you can use firefox normally (doesn't need to be started as root/sudo) and enter as login:
User: root
Pwd: the password you have entered above

SawtheLight
17th January 2007, 12:13
Firefox comesback with unable to connect????
The connection is direct in firefox network properties, although i coudnt restart the service it keeps coming up with command not found.
?? thanks for the assistance !!

SawtheLight
17th January 2007, 12:23
sudo start xinetd
replies: unknown service

sjau
17th January 2007, 16:58
My mistake, do this:


sudo /etc/init.d/xinetd restart

SawtheLight
18th January 2007, 01:46
Thanks for that i thought i had tried this........
But i will ensure i give it a go tonight.
What is really annoying, is that everything is supposed to be easy to set up but when i try nothing works. Being new to linux and not knowing the commands well, feeling like a blind man, its all frustrating. Makes me realise why windows has been so popular.:eek:

sjau
18th January 2007, 08:06
What you want to do isn't basic anymore... :)

SawtheLight
18th January 2007, 12:58
What you want to do isn't basic anymore... :)
I can tell...

BUT
with your amended instrauction i get this.
sudo: /etc/init.d/xinetd: command not found

Looks like there is no service xinetd at all.

Any ideas?:confused:

sjau
18th January 2007, 13:25
Then it's inetd I think

SawtheLight
18th January 2007, 13:47
Neither inetd or xinetd exists int the /etc/init.d folder, something is definately missing

sjau
18th January 2007, 15:06
Then reboot your machine and the altered settings will be taken care of.

SawtheLight
18th January 2007, 23:42
Done and tried....????? Maybe a corrupt installaion????

sjau
19th January 2007, 09:34
I don't know.. for me it worked perfectly without being required to reboot and stuff..