LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 03-06-2010, 10:41 AM   #1
spiderdan
LQ Newbie
 
Registered: Mar 2010
Posts: 6

Rep: Reputation: 0
Samba windows workgroup printer issues


Asked this question on another forums but no one replied with an answer. Thought I'd give a second shot. I am using Fedora 12 and Samba and have been having trouble getting the computers in my windows workgroup to play nice with the new linux box. Samba is version 3.4.5-55.fc12. Basically, I am having two issues. When I first boot my computer, if I try to access it from another computer in the workgroup, I will get a message to the extent of the network location could not be accessed. If I change Samba's authentication mode from share to something else, then change it back to share, it works. My other problem is this, and I'm not entirely sure its possible. This computer is set to dual boot to both windows and fedora. I would like the other pcs to be able to use the printer attached to it in the same manner regardless of which os I'm running at the time. In theory, this should be as simple as making sure the addresses are the same, I think. Linux uses a slightly different name for the printer than windows. Windows is hp psc 1200 series. Linux is psc-1200-series. I have been looking online for a way to change the printer name. This is the closest thing I could find.

Code:
[hp psc 1200 series]
	security = server
	path = /var/spool/samba
	printer name = hp psc 1200 series
	writable = yes
	public = yes
	printable = yes
;	browseable = yes
adding that to my smb.conf caused the windows pc to see the new printer, but it did not mistake it for the printer on my windows boot. I tried installing the linux printer (not the one I added) on my windows box just to see if it worked, but it needed the drivers installed manually and default drivers are not included with windows, so I would have had to use my hp disks, which weren't available at the time. I have already changed my hostname to match that of my windows boot, so that much should be the same. What else do I need to do to get the other computers to see this printer the same in windows and fedora? Thanks!
 
Old 03-08-2010, 01:14 AM   #2
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 411

Rep: Reputation: 42
Go ahead and post the global section of your smb.conf file as well. There are a lot of things that can go wrong there. You need to have your workgroup name set among other things.

I'm not familiar with "server" security, I use "user." One thing at a time.

Also, the setting, in this section:
Quote:
hp psc 1200 series]
security = server
path = /var/spool/samba
printer name = hp psc 1200 series
writable = yes
public = yes
printable = yes
; browseable = yes
Add this to make the clients use their own driver so the print server isn't brought down with driver processing. It will simply become a pass through to the printer with no intervening processing.
Code:
	use client driver = yes
On other thing to note is that "browseable" is commented out. A semi-colon is a comment, as well as a hash. I don't think that's what you were shooting for here. But maybe it is? I'd think you want the users to be able to easily find it on the network.

Also, you may need to run checkpc -f to make sure your print queues are ready with proper permissions.
 
Old 03-14-2010, 04:18 PM   #3
spiderdan
LQ Newbie
 
Registered: Mar 2010
Posts: 6

Original Poster
Rep: Reputation: 0
meetscott, thank you for your reply and I apologize for taking so long to get back to this thread. I made the changes you suggested in my smb.conf and my printer now shows up as ready on the windows boxes on my network and they will try to print. I even noticed that a file briefly appeared in my /var/spool/samba folder when I tried to print on another machine. This file, however, would briefly disappear and never print. As far as I can tell my print queue is clear and I was unable to do the checkpc -f you suggested. I have no trouble printing from this pc locally. Also, I am still having to change my Samba server settings from share to some other type and then back to share to make this pc detectable on the network.

Code:
;smb.conf
[global]

# ----------------------- Network-Related Options -------------------------
#
# workgroup = the Windows NT domain name or workgroup name, for example, MYGROUP.
#
# server string = the equivalent of the Windows NT Description field.
#
# netbios name = used to specify a server name that is not tied to the hostname.
#
# interfaces = used to configure Samba to listen on multiple network interfaces.
# If you have multiple interfaces, you can use the "interfaces =" option to
# configure which of those interfaces Samba listens on. Never omit the localhost
# interface (lo).
#
# hosts allow = the hosts allowed to connect. This option can also be used on a
# per-share basis.

# hosts deny = the hosts not allowed to connect. This option can also be used on
# a per-share basis.
#
	workgroup = labarowskinet
	server string = Samba Server Version %v

;	netbios name = MYSERVER

;	interfaces = lo eth0 192.168.12.2/24 192.168.13.2/24
;	hosts allow = 127. 192.168.12. 192.168.13.

# --------------------------- Logging Options -----------------------------
#
# log file = specify where log files are written to and how they are split.
#
# max log size = specify the maximum size log files are allowed to reach. Log
# files are rotated when they reach the size specified with "max log size".
#

	# log files split per-machine:
	log file = /var/log/samba/log.%m
	# maximum size of 50KB per log file, then rotate:
	max log size = 50

# ----------------------- Standalone Server Options ------------------------
#
# security = the mode Samba runs in. This can be set to user, share
# (deprecated), or server (deprecated).
#
# passdb backend = the backend used to store user information in. New
# installations should use either tdbsam or ldapsam. No additional configuration
# is required for tdbsam. The "smbpasswd" utility is available for backwards
# compatibility.
#

	security = share
;	passdb backend = tdbsam


# ----------------------- Domain Members Options ------------------------
#
# security = must be set to domain or ads.
#
# passdb backend = the backend used to store user information in. New
# installations should use either tdbsam or ldapsam. No additional configuration
# is required for tdbsam. The "smbpasswd" utility is available for backwards
# compatibility.
#
# realm = only use the realm option when the "security = ads" option is set.
# The realm option specifies the Active Directory realm the host is a part of.
#
# password server = only use this option when the "security = server"
# option is set, or if you cannot use DNS to locate a Domain Controller. The
# argument list can include My_PDC_Name, [My_BDC_Name], and [My_Next_BDC_Name]:
#
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
#
# Use "password server = *" to automatically locate Domain Controllers.

;	realm = MY_REALM

;	password server = <NT-Server-Name>

# ----------------------- Domain Controller Options ------------------------
#
# security = must be set to user for domain controllers.
#
# passdb backend = the backend used to store user information in. New
# installations should use either tdbsam or ldapsam. No additional configuration
# is required for tdbsam. The "smbpasswd" utility is available for backwards
# compatibility.
#
# domain master = specifies Samba to be the Domain Master Browser, allowing
# Samba to collate browse lists between subnets. Do not use the "domain master"
# option if you already have a Windows NT domain controller performing this task.
#
# domain logons = allows Samba to provide a network logon service for Windows
# workstations.
#
# logon script = specifies a script to run at login time on the client. These
# scripts must be provided in a share named NETLOGON.
#
# logon path = specifies (with a UNC path) where user profiles are stored.
#
#

;	domain master = yes
;	domain logons = yes

	# the following login script name is determined by the machine name
	# (%m):
;	logon script = %m.bat
	# the following login script name is determined by the UNIX user used:
;	logon script = %u.bat
;	logon path = \\%L\Profiles\%u
	# use an empty path to disable profile support:
;	logon path =

	# various scripts can be used on a domain controller or a stand-alone
	# machine to add or delete corresponding UNIX accounts:

;	add user script = /usr/sbin/useradd "%u" -n -g users
;	add group script = /usr/sbin/groupadd "%g"
;	add machine script = /usr/sbin/useradd -n -c "Workstation (%u)" -M -d /nohome -s /bin/false "%u"
;	delete user script = /usr/sbin/userdel "%u"
;	delete user from group script = /usr/sbin/userdel "%u" "%g"
;	delete group script = /usr/sbin/groupdel "%g"


# ----------------------- Browser Control Options ----------------------------
#
# local master = when set to no, Samba does not become the master browser on
# your network. When set to yes, normal election rules apply.
#
# os level = determines the precedence the server has in master browser
# elections. The default value should be reasonable.
#
# preferred master = when set to yes, Samba forces a local browser election at
# start up (and gives itself a slightly higher chance of winning the election).
#
;	local master = no
;	os level = 33
;	preferred master = yes

#----------------------------- Name Resolution -------------------------------
#
# This section details the support for the Windows Internet Name Service (WINS).
#
# Note: Samba can be either a WINS server or a WINS client, but not both.
#
# wins support = when set to yes, the NMBD component of Samba enables its WINS
# server.
#
# wins server = tells the NMBD component of Samba to be a WINS client.
#
# wins proxy = when set to yes, Samba answers name resolution queries on behalf
# of a non WINS capable client. For this to work, there must be at least one
# WINS server on the network. The default is no.
#
# dns proxy = when set to yes, Samba attempts to resolve NetBIOS names via DNS
# nslookups.

;	wins support = yes
;	wins server = w.x.y.z
;	wins proxy = yes

;	dns proxy = yes

# --------------------------- Printing Options -----------------------------
#
# The options in this section allow you to configure a non-default printing
# system.
#
# load printers = when set you yes, the list of printers is automatically
# loaded, rather than setting them up individually.
#
# cups options = allows you to pass options to the CUPS library. Setting this
# option to raw, for example, allows you to use drivers on your Windows clients.
#
# printcap name = used to specify an alternative printcap file.
#

;	load printers = yes
	cups options = raw

;	printcap name = /etc/printcap
	# obtain a list of printers automatically on UNIX System V systems:
;	printcap name = lpstat
;	printing = cups

# --------------------------- File System Options ---------------------------
#
# The options in this section can be un-commented if the file system supports
# extended attributes, and those attributes are enabled (usually via the
# "user_xattr" mount option). These options allow the administrator to specify
# that DOS attributes are stored in extended attributes and also make sure that
# Samba does not change the permission bits.
#
# Note: These options can be used on a per-share basis. Setting them globally
# (in the [global] section) makes them the default for all shares.

;	map archive = no
;	map hidden = no
;	map read only = no
;	map system = no
;	encrypt passwords = yes
;	guest ok = no
;	guest account = nobody
;	store dos attributes = yes


#============================ Share Definitions ==============================

[homes]
	comment = Home Directories
	browseable = no
	writable = yes
;	valid users = %S
;	valid users = MYDOMAIN\%S

[printers]
	comment = All Printers
	path = /var/spool/samba
	browseable = no
;	guest ok = no
;	writable = No
	printable = yes

[hp psc 1200 series]
	security = user
	path = /var/spool/samba
	printer name = hp psc 1200 series
	writable = yes
	public = yes
	printable = yes
;	browseable = yes
	use client driver = yes

# Un-comment the following and create the netlogon directory for Domain Logons:
;	[netlogon]
;	comment = Network Logon Service
;	path = /var/lib/samba/netlogon
;	guest ok = yes
;	writable = no
;	share modes = no

# Un-comment the following to provide a specific roving profile share.
# The default is to use the user's home directory:
;	[Profiles]
;	path = /var/lib/samba/profiles
;	browseable = no
;	guest ok = yes

# A publicly accessible directory that is read only, except for users in the
# "staff" group (which have write permissions):
;	[public]
;	comment = Public Stuff
;	path = /home/samba
;	public = yes
;	writable = yes
;	printable = no
;	write list = +staff
 
Old 03-14-2010, 11:45 PM   #4
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 411

Rep: Reputation: 42
I took the liberty of cleaning things up a bit for clarity. I removed sections you weren't using at all and the descriptive comments that weren't important. This is anything that starts with a semicolon ( or a hash (#).

Quote:
Originally Posted by spiderdan View Post
Code:
[global]
	workgroup = labarowskinet
	server string = Samba Server Version %v
	# log files split per-machine:
	log file = /var/log/samba/log.%m
	# maximum size of 50KB per log file, then rotate:
	max log size = 50

	security = share

;	load printers = yes
	cups options = raw

;	printcap name = /etc/printcap
	# obtain a list of printers automatically on UNIX System V systems:
;	printcap name = lpstat
;	printing = cups

[homes]
	comment = Home Directories
	browseable = no
	writable = yes
;	valid users = %S
;	valid users = MYDOMAIN\%S

[printers]
	comment = All Printers
	path = /var/spool/samba
	browseable = no
;	guest ok = no
;	writable = No
	printable = yes

[hp psc 1200 series]
	security = user
	path = /var/spool/samba
	printer name = hp psc 1200 series
	writable = yes
	public = yes
	printable = yes
;	browseable = yes
	use client driver = yes
I'm not sure which printing system you are using, but based on the "cups options = raw", I'm guessing cups. Which means you need to add this:
Code:
	printing = cups
So go ahead and uncomment that. Otherwise I think it defaults to the old lp unix print system. I'm not sure, I can't remember.

I would also add:
Code:
	hosts allow = 192.168.0.
This would mean that only computers on that network would be able to use samba services. A little more secure in case you make a firewall mistake sometime ;-)

Comment out "writable = yes". You don't need it. In fact it should probably be "writable = no" or nothing (commented out), which mean the same thing.

You can delete the whole "[printers]" section. It's meaningless. You only need the "[hp psc 1200 series]". One or the other in your case, I'm assuming.

Uncomment "load printers = yes".

Let's see where we end up after some of these changes. You are close. I think the biggest thing is the "printing = cups" is missing.

Post back and let us know how it goes :-)
 
Old 03-15-2010, 03:14 PM   #5
spiderdan
LQ Newbie
 
Registered: Mar 2010
Posts: 6

Original Poster
Rep: Reputation: 0
Thanks for the continued help meetscott! I am indeed using cups. I made the changes you suggested (minus the hosts allow. I figure I'll do that t the end.) but I'm afraid this issue still persists. One thing I've noticed, when I use the samba graphical configuration by going to System->Administration->Samba, some settings I have changed in the smb.conf file, namely browseable = yes and printing = cups are commented out. I have checked for and deleted backups in /etc/samba but this doesn't seem to be how its recovering these settings. This is not a huge deal as I could just avoid graphical configuration but, as I have said, I often have to change my type from share, to some other type, then back to share. This seems hit or miss in itself. I had to do it once today but after that the computer was detected on the network fine on boot. Also, files are no longer appearing in /var/spool/samba. This worked once today. Coincidentally, it was right after I changed the share type. I haven't been able to get it to work since. Hope this makes some sense as I'm struggling to figure it out myself. Not much consistency.

Code:
[global]

	workgroup = labarowskinet
	server string = Samba Server Version %v
	# log files split per-machine:
	log file = /var/log/samba/log.%m
	# maximum size of 50KB per log file, then rotate:
	max log size = 50
	security = share
;	load printers = yes
	cups options = raw

;	printcap name = /etc/printcap
	# obtain a list of printers automatically on UNIX System V systems:
;	printcap name = lpstat
	printing = cups

[homes]
	comment = Home Directories
	browseable = no
	writable = yes
;	valid users = %S
;	valid users = MYDOMAIN\%S

#[printers]
#	comment = All Printers
#	path = /var/spool/samba
#	browseable = no
#;	guest ok = no
#;	writable = No
#	printable = yes

[hp psc 1200 series]
	security = user
	path = /var/spool/samba
	printer name = hp psc 1200 series
;	writable = yes
	public = yes
	printable = yes
	browseable = yes
	use client driver = yes
 
Old 03-15-2010, 04:04 PM   #6
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 411

Rep: Reputation: 42
Quote:
Originally Posted by spiderdan View Post
Thanks for the continued help meetscott! I am indeed using cups. I made the changes you suggested (minus the hosts allow. I figure I'll do that t the end.) but I'm afraid this issue still persists. One thing I've noticed, when I use the samba graphical configuration by going to System->Administration->Samba, some settings I have changed in the smb.conf file, namely browseable = yes and printing = cups are commented out. I have checked for and deleted backups in /etc/samba but this doesn't seem to be how its recovering these settings. This is not a huge deal as I could just avoid graphical configuration but, as I have said, I often have to change my type from share, to some other type, then back to share. This seems hit or miss in itself. I had to do it once today but after that the computer was detected on the network fine on boot. Also, files are no longer appearing in /var/spool/samba. This worked once today. Coincidentally, it was right after I changed the share type. I haven't been able to get it to work since. Hope this makes some sense as I'm struggling to figure it out myself. Not much consistency.

Code:
[global]

	workgroup = labarowskinet
	server string = Samba Server Version %v
	# log files split per-machine:
	log file = /var/log/samba/log.%m
	# maximum size of 50KB per log file, then rotate:
	max log size = 50
	security = share
;	load printers = yes
	cups options = raw

;	printcap name = /etc/printcap
	# obtain a list of printers automatically on UNIX System V systems:
;	printcap name = lpstat
	printing = cups

[homes]
	comment = Home Directories
	browseable = no
	writable = yes
;	valid users = %S
;	valid users = MYDOMAIN\%S

#[printers]
#	comment = All Printers
#	path = /var/spool/samba
#	browseable = no
#;	guest ok = no
#;	writable = No
#	printable = yes

[hp psc 1200 series]
	security = user
	path = /var/spool/samba
	printer name = hp psc 1200 series
;	writable = yes
	public = yes
	printable = yes
	browseable = yes
	use client driver = yes
This isn't as bad as you think, but I'd stay off the graphical tools until you get things working because it appears to be tweaking too many things at once. In fact, it seems to be messing things up for you.

Looking at your file, the behavior you describe is to be expected. You switched the printer security to "user", while the global is "share". This means "user" is overriding "share" from the global settings. Without setting the "users" you will not be able to access these printers. Don't worry about "user". Just delete this line:
Code:
security = user
In the "global" section, uncomment "load printers = yes". Restart Samba. Try it again.
 
Old 03-15-2010, 04:36 PM   #7
spiderdan
LQ Newbie
 
Registered: Mar 2010
Posts: 6

Original Poster
Rep: Reputation: 0
Thanks again meetscott! The good news is I'm seeing a file again in /var/spool/samba. The bad is that my printer is still sitting idly.

Code:
[global]
	workgroup = labarowskinet
	server string = Samba Server Version %v
	log file = /var/log/samba/log.%m
	max log size = 50
	security = share
;	passdb backend = tdbsam
;	realm = MY_REALM
;	password server = <NT-Server-Name>
;	domain master = yes
;	domain logons = yes
	load printers = yes
	cups options = raw
;	printcap name = /etc/printcap
	# obtain a list of printers automatically on UNIX System V systems:
;	printcap name = lpstat
	printing = cups

[homes]
	comment = Home Directories
	browseable = no
	writable = yes
;	valid users = %S
;	valid users = MYDOMAIN\%S

#[printers]
#	comment = All Printers
#	path = /var/spool/samba
#	browseable = no
#;	guest ok = no
#;	writable = No
#	printable = yes

[hp psc 1200 series]
	path = /var/spool/samba
	printer name = hp psc 1200 series
;	writable = yes
	public = yes
	printable = yes
	browseable = yes
	use client driver = yes
EDIT: BTW, the service I am restarting is smb. Can't imagine samba as being anything else on the list but thought I should verify this is indeed the right service.

EDIT2: When I logged in today, I noticed my computer was not showing up under network. Normally I would open the samba configuration and change the mode to user then back to share and that would fix the issue, but I am avoiding the graphical configuration as it will mess up my settings made with gedit. I tried using gedit (as root of course) to change the mode to user, restart smb, then change back to share and restart smb again, but this did not seem to work. I appreciate any help anyone can give on this issue.

Last edited by spiderdan; 03-16-2010 at 02:50 PM.
 
Old 03-17-2010, 04:31 PM   #8
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 411

Rep: Reputation: 42
I'm having trouble with the reason here. Let me do some more research and get back to you. I may post my smb.conf file for you so you can see it and use it as a base because it works. I will do some more thinking on this and post back in the next day or two.
 
Old 03-22-2010, 12:33 PM   #9
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 411

Rep: Reputation: 42
My Working smb.conf file

I've been quite busy and I haven't had any extra time. Sorry for letting you down. I'm posting my working file for your study and comparison. Then we can see what to do from there.

Code:
[global]
  socket options = TCP_NODELAY 
  dns proxy = no               
  workgroup = home             
  keep alive = 30    
  printing = cups               
  load printers = yes           
  preserve case = yes           
  short preserve case = yes     
  case sensitive = no           
  hosts allow = 192.168.0. 127. 
  security = user               
  encrypt passwords = yes       
  server string = Webhost1 Samba Server
  log file = /var/log/samba-log.%m
  max log size = 50
  lock directory = /var/lock/samba

[printers]
  comment = All Printers
  path = /var/spool/samba
  browseable = yes
  printable = yes
  use client driver = yes
I have a couple other sections like entries for cdrom access, floppy access, and home directories, but those are not relevant for you. As, I said before, I am using "security = user" which basically means that windows users must have the <i>same</i> usernames and passwords as the Linux host that does printing. That is the big difference here from what you are doing.
 
Old 03-22-2010, 06:39 PM   #10
spiderdan
LQ Newbie
 
Registered: Mar 2010
Posts: 6

Original Poster
Rep: Reputation: 0
meetscott, by no means have you let me down. You've been very helpful during this whole ordeal. Lately I haven't even been able to get my computer to see itself under network. I tried changing from share to user, but still it doesn't even detect itself (restarted smb). I thought I would give your file a try, but now the smb service wouldn't start and I get the selinux error below. I removed the following 3 lines and the service now restarts, but I still cant even see my own computer under network, while I can see one windows box.

removed lines
Code:
hosts allow = 192.168.0. 127. 
log file = /var/log/samba-log.%m
lock directory = /var/lock/samba
error
Code:
Summary:

SELinux is preventing /usr/sbin/smbd "search" access on /var/lock.

Detailed Description:

[smbd has a permissive type (smbd_t). This access was not denied.]

SELinux denied access requested by smbd. The current boolean settings do not
allow this access. If you have not setup smbd to require this access this may
signal an intrusion attempt. If you do intend this access you need to change the
booleans on this system to allow the access.

Allowing Access:

One of the following booleans is set incorrectly: samba_export_all_ro,
samba_export_all_rw

Fix Command:

Choose one of the following to allow access:
Allow samba to share any file/directory read only.
# setsebool -P samba_export_all_ro 1
Allow samba to share any file/directory read/write.
# setsebool -P samba_export_all_rw 1


Additional Information:

Source Context                system_u:system_r:smbd_t:s0
Target Context                system_u:object_r:var_lock_t:s0
Target Objects                /var/lock [ dir ]
Source                        smbd
Source Path                   /usr/sbin/smbd
Port                          <Unknown>
Host                          DANIEL-PC
Source RPM Packages           samba-3.4.7-58.fc12
Target RPM Packages           filesystem-2.4.30-2.fc12
Policy RPM                    selinux-policy-3.6.32-103.fc12
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Plugin Name                   catchall_boolean
Host Name                     DANIEL-PC
Platform                      Linux DANIEL-PC 2.6.32.9-70.fc12.x86_64 #1 SMP Wed
                              Mar 3 04:40:41 UTC 2010 x86_64 x86_64
Alert Count                   3
First Seen                    Mon 22 Mar 2010 06:36:43 PM EDT
Last Seen                     Mon 22 Mar 2010 06:36:43 PM EDT
Local ID                      eeb7b696-1e21-44c2-b8a3-c21b4bd628af
Line Numbers                  

Raw Audit Messages            

node=DANIEL-PC type=AVC msg=audit(1269297403.504:24): avc:  denied  { search } for  pid=3102 comm="smbd" name="lock" dev=dm-0 ino=114695 scontext=system_u:system_r:smbd_t:s0 tcontext=system_u:object_r:var_lock_t:s0 tclass=dir

node=DANIEL-PC type=SYSCALL msg=audit(1269297403.504:24): arch=c000003e syscall=2 success=yes exit=128 a0=7f24e684da70 a1=42 a2=180 a3=7fff5f13fe20 items=0 ppid=3101 pid=3102 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="smbd" exe="/usr/sbin/smbd" subj=system_u:system_r:smbd_t:s0 key=(null)
I looked through some of the log files and thought some of these might be helpful. The first was, if I recall correctly, the smbd log. The other two came from old. The first was the log labelled as the pc I was trying to print from. The second I only included because it mentions my printer a couple times. I don't really know what to look for, so if there are specific logs I should post or something I should be looking for I would appreciate advice.

smbd
branden-pc
mentions printer
note that parts of the last two are multiple logs. I marked the transition points. Noticed in that last log that my printer is getting a Unable to print file to hp psc 1200 series - client-error-not-found. That seems pretty promising as far as what could be the issue. Acting on that, I thought the issue could be that I was under the impression printer name was what you wanted to have it listed as on your network, now I'm thinking its what the name is on my box (noob mistake on my part). I changed printer name = psc-1200-series, which is what my printer is listed as locally. I think this was part of the issue, but I still can't even get my own computer to see itself under network. One other interesting entry

Code:
[2010/02/02 20:28:50,  0] nmbd/nmbd_workgroupdb.c:55(name_to_unstring)
  name_to_nstring: workgroup name LABAROWSKINETWORK is too long. Truncating to LABAROWSKINETWO
That can't be good. I feel that if I could get my computer back on the network, printing might work. All help is appreciated.

Last edited by spiderdan; 03-22-2010 at 06:42 PM.
 
Old 03-25-2010, 04:32 PM   #11
spiderdan
LQ Newbie
 
Registered: Mar 2010
Posts: 6

Original Poster
Rep: Reputation: 0
Finally managed to get printing to work this afternoon. Seems to have been setting browseable = true under global that made my pc visible under the workgroup. I've noticed that nmb is disabled. Its running now and things seem to work, but that's not the only thing I've changed. It does need to run for this to work, right? Not sure why its disabled. Not something I did. Thanks to meetscott for all his help!

smb.conf
Code:
[global]
	workgroup = labarowskinet
	browseable = yes
	server string = Samba Server Version %v
	log file = /var/log/samba/log.%m
	max log size = 50
	security = share
;	load printers = yes
	cups options = raw
;	printcap name = /etc/printcap
	# obtain a list of printers automatically on UNIX System V systems:
;	printcap name = lpstat
	printing = cups

#[homes]
#	comment = Home Directories
#	browseable = no
#	writable = yes
#;	valid users = %S
#;	valid users = MYDOMAIN\%S

#[printers]
#	comment = All Printers
#	path = /var/spool/samba
#	browseable = no
#;	guest ok = no
#;	writable = No
#	printable = yes

[hp psc 1200 series]
	security = share
	path = /var/spool/samba
	printer name = psc-1200-series
;	writable = yes
	public = yes
	printable = yes
	browseable = yes
	guest ok = yes
	use client driver = yes
 
Old 03-30-2010, 07:25 PM   #12
meetscott
Samhain Slackbuild Maintainer
 
Registered: Sep 2004
Location: Phoenix, AZ, USA
Distribution: Slackware
Posts: 411

Rep: Reputation: 42
Yep, you'll probably have nmbd and smbd running.

I've been checking back once in a while to see how things were going. Glad you got it working. Post back if you need anything else.

r. scott smith
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Samba and Windows workgroup Tenno Linux - Newbie 5 05-25-2009 12:40 AM
Samba Workgroup and Domain with File n printer Share full Configuration for Fedora 4 d.vinayaham Linux - Software 8 11-02-2006 03:13 AM
Samba on a windows xp home workgroup eladla Linux - Networking 1 07-03-2004 03:09 PM
Can't browse Windows Workgroup due to Samba? CanadianSlacker Linux - General 4 05-07-2004 06:49 PM
connecting to windows workgroup using samba? linoob Linux - Newbie 7 10-23-2002 08:17 PM


All times are GMT -5. The time now is 03:26 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration