View Full Version : [SOLVED] Samba NOT working
jakebpg
23rd February 2012, 09:24 PM
Has any one gotten samba working?
I can't log into SWAT. All of the typical samba services are running smb,nmb and xinetd.
I can't even run system-config-samba from the menu but it does run if I start it from a terminal but it shows errors when doing so.
here's the error as shown in the terminal:
WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'
** WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'
I'm using the KDE spin from a couple of nights ago.
Is this a bug that needs to be reported?
Swap is enabled, selinux is enabled with all samba bolleeans set to allow samba communication and the firewall is set to allow samba through.
Stumped!!
EvilRedHorse
25th February 2012, 09:26 AM
yum -y install samba samba-common samba-client samba-windbind-clients
systemctl enable smb.service
systemctl enable nmb.service
# samba-swat is really not needed if you are familiar with smb.conf
yum -y remove samba-swat
# edit your /etc/samba/smb.conf file appropriately or post it so someone can analyze it.
vi /etc/samba/smb.conf
# or
nano /etc/samba/smb.conf
# restart daemons
systemctl restart smb.service
systemctl restart nmb.service
jakebpg
25th February 2012, 07:31 PM
Already have all the stuff. See my original post. SMB, NMB are running and all selinux stuff is set to allow smaba to work.yum -y install samba samba-common samba-client samba-windbind-clients
systemctl enable smb.service
systemctl enable nmb.service
# samba-swat is really not needed if you are familiar with smb.conf
yum -y remove samba-swat
# edit your /etc/samba/smb.conf file appropriately or post it so someone can analyze it.
vi /etc/samba/smb.conf
# or
nano /etc/samba/smb.conf
# restart daemons
systemctl restart smb.service
systemctl restart nmb.service
Already have all the stuff. See my original post. SMB, NMB are running and all selinux stuff is set to allow smaba to work.
I know swat is not needed but it makes things simple. Did you see the rror that I mentioned.?
Even after reinstalling all of the samba software I still get the same errors!
Thanks anyhow.
EvilRedHorse
25th February 2012, 09:38 PM
Can you post your smb.conf file, please?
jakebpg
25th February 2012, 10:04 PM
Can you post your smb.conf file, please?
Well I can but that will not correct the errors that are listed in my original post.
Just an FYI.
Workgroup = xxxx = my domain.
testx = my home directory.
Oh and I did create a bug report on the errors.
EvilRedHorse
25th February 2012, 10:18 PM
# have you opened tcp port 901 for swat?
# This is my smb.conf
[global]
workgroup = MSHOME
server string = Samba Server Version %v
force user = smc
force group = smc
force create mode = 0755
follow symlinks = yes
netbios name = F16Server
interfaces = lo eth0 192.168.1.105/24
hosts allow = 127. 192.168. 169.254.
log file = /var/log/samba/log.%m
max log size = 50
security = share
passdb backend = smbpasswd
domain master = yes
local master = yes
os level = 65
preferred master = yes
wins support = yes
; wins server = 192.168.1.95
wins proxy = yes
dns proxy = yes
load printers = yes
cups options = raw
[home]
path = /home
comment = Home Directories
browseable = yes
writable = yes
public = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
guest ok = yes
writable = yes
printable = yes
jakebpg
25th February 2012, 11:22 PM
# have you opened tcp port 901 for swat?
# This is my smb.conf
[global]
workgroup = MSHOME
server string = Samba Server Version %v
force user = smc
force group = smc
force create mode = 0755
follow symlinks = yes
netbios name = F16Server
interfaces = lo eth0 192.168.1.105/24
hosts allow = 127. 192.168. 169.254.
log file = /var/log/samba/log.%m
max log size = 50
security = share
passdb backend = smbpasswd
domain master = yes
local master = yes
os level = 65
preferred master = yes
wins support = yes
; wins server = 192.168.1.95
wins proxy = yes
dns proxy = yes
load printers = yes
cups options = raw
[home]
path = /home
comment = Home Directories
browseable = yes
writable = yes
public = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
guest ok = yes
writable = yes
printable = yes
Yes it is open. I believe that the error has a lot to do with the error in my first post. When I run testparm everything is OK.
That's why I was wondering if anyone else was able to get samba working.
I've had samba working on all of my fedora machines way back to F12. In fact in F12 samba was my domain controller with homes directories created on the fly, roaming profiles, you name it, samba did it. But for some reason samba just doesn't want to cooperate unless it really isn't a samba problem at all and is something in the underlying system that is causing the problem, hence the posted error I mentioned and submitted as a bug.
I run the KDE desktop as Gnome is garbage in my opinion, always has been and always will be. I don't even think the desktop that I liked the most is even around, it was in the second release of redhat way before they became RHEL. I think the version was like 2. something. Now I'm just dating myself with that last tidbit. I use to buy the box set every new release. The last release I bought was redhat 6 and that was before RHEL.
jakebpg
27th February 2012, 10:37 PM
This problem was fixed by installing:
Kernel 3.3.0-0.rc5.git0.3.fc17.x86_64 from koji.:dance:
However, the error that I posted still exists but at least samba is up and running!
And this was the only change to the system. I tried many things from reinstalling samba, removing samba and reinstalling again and to no avail samba just would NOT be available.
I installed this new kernel, rebooted and samba works.
Only problem is it's back to configuring samba the hard way, through a text editor!
lmcogs
26th May 2012, 02:44 PM
Although a few months after the last reply, I am in th same boat. I have 3.3.7-1.fc17.x86_64 on Kde. No matter what I try I can't seem to get samba share recognise by my asus O!play. I can ping it's address and telnet to O!player but no matter what I try I can't get samba share up on player.
sudo smbclient -U leonc -L localhost
Enter leonc's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.5-86.fc17]
Sharename Type Comment
--------- ---- -------
Shares Disk
IPC$ IPC IPC Service (localhost.localdomain)
leonc Printer Home Directories
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.5-86.fc17]
Server Comment
--------- -------
LOCALHOST localhost.localdomain
Workgroup Master
--------- -------
WORKGROUP
I have selinux on permissive mode and I have even done sudo setsebool -P samba_export_all_rw on. I have tried selinux off.
sudo testparm
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[HOMES]"
Processing section "[Shares]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
server string = localhost.localdomain
smb passwd file = /etc/samba/smbpasswd
username map = /etc/samba/smbusers
log file = /var/log/samba/log.%m
max log size = 50
name resolve order = bcast hosts lmhosts wins
load printers = No
local master = No
idmap config * : backend = tdb
cups options = raw
[HOMES]
comment = Home Directories
valid users = %S
read only = No
printable = Yes
print ok = Yes
browseable = No
[Shares]
path = /disk/
valid users = %S
Is there anything I can do. I had it up on f16, unfortunatley disk crashed.
lmcogs
27th May 2012, 11:20 PM
In my case it is firewalld. When I stopped firewalld Samba worked. I don't know how to allow samba ports in firewalld or set rules, instructions are a bit unclear. I am also a bit confused is firewalld going to be in f17 or will it use iptables and if not should I remove it?
bbfuller
28th May 2012, 09:10 AM
Hello lmcogs
There's been some talk of "firewalld" on the forum centered on the lack of a gui configuration tool and whether it is going to be the default in F17.
I'm using samba on a couple of F17 machines at the moment with firewalld and so I can tell you that the command line way to enable samba with firewalld is:
firewall-cmd --add --service=samba
Hope that helps.
lmcogs
28th May 2012, 12:59 PM
thanks that did the trick
AdamW
29th May 2012, 06:14 AM
note, you'll only have firewalld if you installed from F17 Alpha or Beta (or a nightly around that time). Shortly after Beta, we switched back to iptables by default.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.