Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Fedora This forum is for the discussion of the Fedora Project.


Search this Thread
Old 05-31-2008, 03:34 PM   #1
LQ Newbie
Registered: May 2005
Posts: 20

Rep: Reputation: 0
Upgraded to Fedora 9 and Samba broke.

I had samba running with fedora 8 and upgraded and now I can not get the linux box to see the win xp machine. It worked under 8, I was able to browse the network find the machine and mount the windoze share. Also I could print to the printer on the windoze machine.

I'm not sure where to begin. I can post my smb.conf file and start there I guess.


workgroup = wedgehome
server string =

netbios name = wedge2k

interfaces = lo eth0
# 192.168.
hosts allow = 127. 192.168.

# --------------------------- Logging Options -----------------------------
# Log File let you specify where to put logs and how to split them up.
# Max Log Size let you specify the max size log files should reach

# logs split per machine
log file = /var/log/samba/log.%m
# max 50KB per log file, then rotate
max log size = 50

# ----------------------- Standalone Server Options ------------------------
# Scurity can be set to user, share(deprecated) or server(deprecated)
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.

security = share
passdb backend = tdbsam

# ----------------------- Domain Members Options ------------------------
# Security must be set to domain or ads
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
# Use password server option only with security = server or if you can't
# use the DNS to locate Domain Controllers
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *

; realm = MY_REALM

; password server = <NT-Server-Name>

# ----------------------- Domain Controller Options ------------------------
# Security must be set to user for domain controllers
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
# Domain Logons let Samba be a domain logon server for Windows workstations.
# Logon Scrpit let yuou specify a script to be run at login time on the client
# You need to provide it in a share called NETLOGON
# Logon Path let you specify where user profiles are stored (UNC path)
# Various scripts can be used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts

; domain master = yes
; domain logons = yes

# the login script name depends on the machine name
; logon script = %m.bat
# the login script name depends on the unix user used
; logon script = %u.bat
; logon path = \\%L\Profiles\%u
# disables profiles support by specifing an empty path
; logon path =

; 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 ----------------------------
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; local master = no
; os level = 33
; preferred master = yes

#----------------------------- Name Resolution -------------------------------
# Windows Internet Name Serving Support Section:
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
# - WINS Support: Tells the NMBD component of Samba to enable it's WINS Server
# - WINS Server: Tells the NMBD components of Samba to be a WINS Client
# - WINS Proxy: Tells Samba to answer 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 - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups.

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

; dns proxy = yes

# --------------------------- Printing Options -----------------------------
# Load Printers let you load automatically the list of printers rather
# than setting them up individually
# Cups Options let you pass the cups libs custom options, setting it to raw
# for example will let you use drivers on your Windows clients
# Printcap Name let you specify an alternative printcap file
# You can choose a non default printing system using the Printing option

; load printers = yes
cups options = raw

; printcap name = /etc/printcap
#obtain list of printers automatically on SystemV
; printcap name = lpstat
; printing = cups

# --------------------------- Filesystem Options ---------------------------
# The following options can be uncommented if the filesystem supports
# Extended Attributes and they are enabled (usually by the mount option
# user_xattr). Thess options will let the admin store the DOS attributes
# in an EA and make samba not mess with the permission bits.
# Note: these options can also be set just per share, setting them in global
# 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 ==============================

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

comment = All Printers
path = /var/spool/samba
browseable = no
; guest ok = no
; writable = No
printable = 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, but read only, except for people in
# the "staff" group
; [public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = +staff
How do I check what my computer name is. Not the netbios name but the one that network uses?

Old 06-01-2008, 07:51 AM   #2
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654
Do you have a backup of smb.conf from your old system? Restoring it would be the easiest way.

Do you really want "security = share". That mode is obsolete and was used with win95. I'm surprised to see tdbsam being used on such a small scale. You might consider using smbpasswd instead.

You can print out your hostname with the command "hostname".

Also make sure that the firewall isn't blocking ports 139 & 445. For printing, port 631 may be needed.

Also, try "smbclient -L <winxp hostname or IP>". See if the services offered by the xp host are displayed.

You might consider using Samba swat to configure your server. You may need to edit /etc/xinet.d/swat, deleting the line "disable = yes", and then restart xinetd. Then point your web browser at "localhost:901"

On the other hand, you don't need the full samba server to access an XP share. You just need the client. Which of the services: smbd, nmbd or winbind do you have running?

Last edited by jschiwal; 06-01-2008 at 09:20 AM.
Old 06-18-2008, 03:06 PM   #3
LQ Newbie
Registered: Jun 2008
Posts: 7

Rep: Reputation: 0
greetings jschiwal

Sorry to barge in but I have run into the same problem.

I had F8 and had SMB running smoothly (both local shares on my Linux machines and successful access to remote Windows machines)

I upgraded to F9 and have been having problems accessing smb shares on Windows machines from my Linux F9 machine, the other direction works fine

I guess this means I got my smb.conf file configured right .

I run the smbclint -L and see the desired machines are still offering sharing services

I've got winbind running and still no go on accessing the shares on the windows machines

Can you assist a new comer ?
Old 06-18-2008, 03:40 PM   #4
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
Have you guys checked to see if it's SELinux causing you issues?

Try (as root) setenforce 0 to temporarily disable (setenforce 1 to re-enable) and see if it works
Old 06-18-2008, 03:46 PM   #5
LQ Newbie
Registered: May 2005
Posts: 20

Original Poster
Rep: Reputation: 0
Ive haven't even taken the time to try and fix this yet.
I can get to work (at times) so when I really need to transfer files I tinker till I get it working. If I need to print I print to a pdf and move the file. PIA, but too many other things at the top of the to-do list.
Old 06-19-2008, 01:41 AM   #6
LQ Newbie
Registered: Jun 2008
Posts: 7

Rep: Reputation: 0
Originally Posted by billymayday View Post
Have you guys checked to see if it's SELinux causing you issues?

Try (as root) setenforce 0 to temporarily disable (setenforce 1 to re-enable) and see if it works
Sorry, for neglecting to mention .. my original assumption was that the problem was due to security settings on my Linux machine ( the only changed element in the setup)

In order to rule out this sort of problem I first tried to create exclusions for file sharing and then went a step further and disabled both SELINUX and Firewall

neither did the trick
Old 06-19-2008, 02:36 AM   #7
LQ Newbie
Registered: Jun 2008
Posts: 7

Rep: Reputation: 0
Talking Solution found


I have managed to find an easy work around

when using the connect to server I keep failing miserably so I decided to change the approach.

I decided to treat the remote windows servers as just that - servers I want to access

I imitated the windows method of using the explorer and tried doing the same with the linux web browser

I couldn't get FF to work so i moved to Konqueror

now I simply typed in the desired address in the same manner I would browse to any web server

to summarize

1. open Konqueror
2. in the url type smb://<desired server ip address/hostname>
3. type in credentials when requested

Good luck
Old 01-24-2009, 09:56 AM   #8
LQ Newbie
Registered: Jan 2009
Posts: 1

Rep: Reputation: 0
I have found a different issue. (After way too many hours)
This was from a raw Fedora 9 install, but I assume the upgrade has the same problem.

Fedora 9 introduces a second process to Samba called nmbd
BOTH need to be running at startup.
check /etc/init.d and you should see smb and nmb

You should make sure they BOTH automatically start by adding it to your runtime start levels (depending on your config...)
chkconfig --level 5 nmb on
chkconfig --level 5 smb on
chkconfig --level 3 nmb on
chkconfig --level 3 smb on

You can check this manually by logging in to Fedora 9 via the GUI and going to System -> Administration -> Samba
Any changes you make to the Samba settings through the GUI will start or restart the nmdb process.
Hope this saves someone some hours..too late for me



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
I upgraded Fedora 3 to Fedora 4 and only lost half a head of hair! dlowery Member Success Stories 0 04-17-2006 05:44 PM
Upgraded to inkscape .42 and broke my install. bpcomp Linux - Software 2 07-30-2005 04:24 AM
Setup NFS now Samba broke tkman Linux - Networking 2 04-10-2005 03:54 PM
samba was working great, now its broke :( rayber2000 Linux - Enterprise 4 02-28-2005 09:56 PM
I broke samba, but I don't know how Concillian Linux - Networking 13 04-12-2004 02:22 AM

All times are GMT -5. The time now is 11:59 AM.

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