[SOLVED] Samba problem

[ahesham]

I've Fedora 14 X86_64 installed on my PC and I'm trying to connect to my other 2 PCs[XP and Win7]. Basically what I need to do is share my printer to these 2 PCs and enable file sharing. I've read through the Samba man pages and wrote my own smb.conf; however, it never works.

When I go to Network, I can't see any shares except 2 things: "ahesham's public files on amr-pc" and "Windows Network" and both of them give errors when trying to open them. Also the other PCs (and another MacBook Pro) can't see this Linux box.

It always worked like a charm in Ubuntu. Is there something that I'm missing?

[global]
workgroup = WORKGROUP
netbios name = amr-pc
security = SHARE

printing = cups
printcap name = cups
disable spoolss = Yes
show add printer wizard = No

domain master = yes
local master = yes
preferred master = yes
os level = 65
wins support = yes
name resolve order = host lmhost wins bcast
guest ok = yes
guest account = nobody

[printers]
comment = All Printers
path = /var/spool/samba
guest ok = Yes
printable = Yes
use client driver = Yes
browseable = No

[Windows]
path = /media/Windows
read only = no
; browseable = yes
guest ok = yes

[Programs]
path = /media/Programs
read only = no
; browseable = yes
guest ok = yes

[Fun]
path = /media/Fun
read only = no
; browseable = yes
guest ok = yes

[Work]
path = /media/Work
read only = no
; browseable = yes
guest ok = yes

[jpollard]

Have you enabled the samba flags in SELinux?
Do you have security alerts?

[ahesham]

Originally Posted by jpollard

Have you enabled the samba flags in SELinux?
Do you have security alerts?

I don't have any security alerts; however, I haven't touched SELinux. I just marked samba as trusted in the firewall.

[pythagorean]

If you have Windows Live Essentials installed on the windows machine then samba shares wont work from the linux machines but it will work the other direction.

[jpollard]

There are several - most deal only with files. one to allow samba to act
as a domain controller:

samba_domain_controller
samba_export_all_ro
samba_export_all_rw
samba_create_home_dirs
allow_smb_anon_write
samba_share_fusefs
samba_share_nfs
samba_run_unconfined
use_samba_home_dirs

For most files I have samba_enable_home_dirs, and use_samba_home_dirs this allows samba to
pass data from home directories to windows.

I haven't shared printers yet.

[ahesham]

Originally Posted by jpollard

There are several - most deal only with files. one to allow samba to act
as a domain controller:

samba_domain_controller
samba_export_all_ro
samba_export_all_rw
samba_create_home_dirs
allow_smb_anon_write
samba_share_fusefs
samba_share_nfs
samba_run_unconfined
use_samba_home_dirs

For most files I have samba_enable_home_dirs, and use_samba_home_dirs this allows samba to
pass data from home directories to windows.

I haven't shared printers yet.

In SELinux, I filtered all the bools by "samba" and enabled all the results. I've also played with the name resolution order and set it as "name resolve order = lmhost wins bcast host" and now I can view other Windows PCs shares; however, still they can't view my shares nor are they listed in "Network" on my box. When I do "Connect to server" and follow the procedure, I can view my shares; however, they are not listed in "Network" and thus are not available to other computers even if I type \\amr-pc\ShareName in Windows. It complains that no PC named amr-pc is on the same network, and yes we're all in the same workgroup and subnet.

[jakebpg]

Originally Posted by ahesham

In SELinux, I filtered all the bools by "samba" and enabled all the results. I've also played with the name resolution order and set it as "name resolve order = lmhost wins bcast host" and now I can view other Windows PCs shares; however, still they can't view my shares nor are they listed in "Network" on my box. When I do "Connect to server" and follow the procedure, I can view my shares; however, they are not listed in "Network" and thus are not available to other computers even if I type \\amr-pc\ShareName in Windows. It complains that no PC named amr-pc is on the same network, and yes we're all in the same workgroup and subnet.

Almost sounds like you do not have the samba daemons running.

Check to make sure that SMB and NMB are running if not start them and mark them for auto start in all run levels 2,3,4,5

Also is xinetd installed and running?

The easiest way to see if samba is working right is to use SWAT in a browser for admin. If you do localhost:901 after swat is installed and enabled in services and add port 901/tcp into the firewall as trusted you should be able to connect to the samba server and if not then you have a configuration problem.

[ahesham]

Originally Posted by jakebpg

Almost sounds like you do not have the samba daemons running.

Check to make sure that SMB and NMB are running if not start them and mark them for auto start in all run levels 2,3,4,5

Also is xinetd installed and running?

The easiest way to see if samba is working right is to use SWAT in a browser for admin. If you do localhost:901 after swat is installed and enabled in services and add port 901/tcp into the firewall as trusted you should be able to connect to the samba server and if not then you have a configuration problem.

Now it works, thank you. I had winbindd, nmb, and xinetd service stopped.

[jakebpg]

Originally Posted by ahesham

Now it works, thank you. I had winbindd, nmb, and xinetd service stopped.

No problem.

You should mark this as solved so that if others are having problems they can look here and know what solved you're problem and then they can verify if they need to do the same to fix their problem.