IPC$ Password Problem / HELP! Can't see Unix printer shares

Geoff Lane geoff at gjctech.force9.net
Tue Feb 16 12:50:24 GMT 1999

Tony Jones related problems seeing Unix printer shares.
Nate Keegan related problems with a Linux SMB server asking for a password
for \\Server\IPC$
I'm in the process of migrating all my machines to Win95/98 and Red Hat
Linux 5.2 dual boot.  While struggling with configuring the first machine to
go that route, I encountered the problems that both Tony and Nate relate.

Huge caveat here -- I'm a total Linux novice.  What follows worked for me.
However, I may have seriously comprised security -- so YMMV.

I'm running Red Hat Linux 5.2 with Samba release 1.9.18p10 dated 20 Aug
1998.  The network is primarily peer-peer Win95/98 (i.e. no NT domain is

I found the instructions given in ENCRYPTION.txt helpful, but misleading in
how to create the smbpasswd file.  Using the mksmbpasswd.sh script (as
suggested) resulted in my being asked for a password for the IPC$ share.  I
resolved the issue by adding SMB users to the smbpasswd file by using
'smbpasswd' with the -a option.  The syntax for this is:
 smbpasswd -a -U <remote_name> username
where <remote_name> is the username by which the user connects to the SMB
share, and username is the user's name on the Linux machine.  Please try
'man smbpasswd' for more-detailed information.

The above also relates to the 'can't see printers' problem because (prior to
rebuilding the smbpasswd file) Samba logged me onto the Linux box as user
'nobody' ('nobody' had no printing rights, and couldn't browse the
printers).  However, before I could print to the Linux-hosted printer, I
also had to give all users write permissions on the print queues and the
printer device.  Printing.txt in the Samba docs gives some good debugging
information.  It also gives instructions on how to set up an SMB shared RAW
printer (that is, one that passes the Windows printer driver output directly
to the printer port).  This allows Windows users to use the more up-to-date
printer drivers and (because the dual boot box uses the same printer name
for both OSs) remote users don't need to worry about which OS is currently
running on the server.

FWIW, below are my smb.conf and printcap files.  If anyone spots errors in
these, please let me know.


Geoff Lane
Cornwall, UK
geoff at gjctech.force9.net

#===== /etc/smb.conf ====

	log file = /var/log/samba-log.%m
	lock directory = /var/lock/samba
	workgroup = workgroup
	share modes = yes
	printing = bsd
	printcap name = /etc/printcap
	load printers = yes
#	Security mode.  This sets up user-level security
#	with encrypted passwords.
	security = user
	encrypt passwords = yes
	smb passwd file = /etc/smbpasswd

	comment = Home Directories
	browseable = no
	writeable = yes

	comment = Shared file space
	path = /home/public
	read only = no
	writeable = yes
	printable = no
	public = yes

	comment = All Printers
	path = /var/spool/lpd/lp
	browseable = no
	printable = yes
	public = yes
	writable = no
	create mode = 0700

[laserjet 6p]
	path = /var/spool/lpd/lp
	printer name = lp
	writable = yes
	public = yes
	printable = yes
	print command = lpr -b -P%p %s

#========= /etc/printcap =========
# Please don't edit this file directly unless you know what you are doing!
# Be warned that the control-panel printtool requires a very strict format!
# Look at the printcap(5) man page for more info.
# This file can be edited with the printtool in the control-panel.

##PRINTTOOL3## LOCAL ljet4 600x600 a4 {} LaserJet4 Default {}
laserjet 6p:\

More information about the samba mailing list