Hi guys. I'm new in the Fedora Core world and my welcome hasn't been gud. In the past years have been working with Redhat 9(My favorite Linux distribution) in setting up different type of servers.

At present, I'm facing permission problems in setting a SAMBA server in FC6 (2.6.18-1.2798.fc6 i686) I have added a user on samba (elly) that also exist has a linux home user. I have also created a shared folder with 777 permission (writeable for all users). With all these settings, I still cant access my home folder and the shared folders from my windows my machine.

Output of testparm smb.conf
[global]
server string = Samba Server
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = No
cups options = raw

[homes]
comment = Home Directories
read only = No
browseable = No

[printers]
comment = All Printers
path = /usr/spool/samba
printable = Yes
browseable = No

[share]
comment = Helen in linux
path = /home/elly/share
valid users = elly, root
write list = elly
read only = No
create mask = 0777

Please assist in this. thanks in advance

Do you mean "from my Windows ME machine"; or "from my Windows machine"?

Is your username and password on the Linux Machine the same as on your Windows Machine? Did you use smbpasswd to add the elly user and password.

Do you have ports 137-139 open in the Linux Server's firewall?

Look in your /usr/share/doc/samba-<version>/ directory for 4 books on Samba 3. They may have a couple of registry hacks needed for Windows ME. The samba3byExample and the Samba 3 Howto & Reference guide are the two to look at.

Have you also ran the smbpasswd command and added the user that way?

Sorry, I ment Windows machine, running XP pro. I have also allowed port 137-139 tcp and udp on my iptables. Even if i flush the iptables rule, i still cant access the server.

I have user smbpasswd -a to add elly to samba, used the same/different password and still face the same problem. I just don't know what going on. all configuration OKAY.

Make sure that the smbd daemon is running. Also try opening port 445 as well. At least temporarily. Does the windows network use WINS or DNS for browsing?

Either the samba or a samba-doc package contains some samba 3 books that might help. The Samba 3 by example may illustrate a step you skipped. The Samba 3 Howto & Reference has a troubleshooting section on browsing as well.

OK. I have made some progress towards the solution. We can rule out following:
1. firewall - currently, I don't have any active ip chain rule.
2. DNS or WIN server - But my network uses dns.

I gone trough the samba check list, n change my smb.conf file to

[global]

[homes]
read only = No

[tmp]
comment = temporary files
path = /tmp

[share]
path = /share

VERY simple configuration. Now, I can only access the /share and /tmp folders but, I can't write nor edit. The folders have the following properties

/share - Permission(1777), owned by elly
/tmp - Permission(1777), owned by root

the basic firewall in the fedora core system manager needs to be disabled for samba! I had the same issue myself.

can you use the ping command to ping each machine on the network?? also check to see if there is an entry in the arp list for the linux box on your windows machine (run > cmd > arp -a)

try and ping by ip address first and then by netbios name and/or dns name (if applicable).

also browse to the folder in the fedora core hard drive and set the permissions /owner permissions to "elly"

then run:

service smb restart

then try again

HTH

BlackFish

EDIT: Sorry disregard the stuff about pinging, misread another post :-P

sorry

hey friend

don't worry!
follow this configuration.........

[global]

workgroup = Destiny
server string = Samba Server
netbios name = Server1
interfaces = lo eth0 192.168.0. /24
hosts allow = 127. 192.168.0.
log file = /var/log/samba/%m.log
max log size = 500
passdb backend = smbpasswd
smb passwd file = /home/samba/smbpasswd
pam password change = Yes
passwd program = /usr/bin/passwd %u
encrypt passwords = yes
unix password sync = Yes
time server = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
security = user
; password server = <NT-Server-Name>
domain master = yes
domain logons = yes
logon script = %u.bat
logon path = \\%L\Profiles\%u
logon drive = Y:
logon home = \\Server1\%U\win9x_profile
idmap gid = 16777216-33554431
admin users = root rahul
delete group script = /usr/sbin/groupdel '%g'
add machine script = /usr/sbin/adduser -n -g 100 -d /dev/null -s /bin/false -M %u
add user script = /usr/sbin/useradd "%u" -n -g users
delete user script = /usr/sbin/userdel "%u"
delete user from group script = /usr/sbin/userdel "%u" "%g"


local master = yes
os level = 64
preferred master = yes


wins support = yes
# wins server = 192.168.0.2
wins proxy = yes
[homes]
comment = Home Directories
browseable = no
writeable = yes
; valid users = %S
; valid users = MYDOMAIN\%S


[Profiles]
path = /home/profiles
browseable = no
create mask = 0600
directory mask = 0700
profile acls = yes
comment = public profile
writeable = yes
[Interview]
comment = Destiny Interview
path = /Destiny/Interview
valid users = @interview
read list = @interview
write list = @interview
writeable = yes
inherit permissions = Yes
volume = Interview
browseable = yes
................................
This is what i m using now.
Frist u should declare a domain (Destiny_im using)and server name(server1_im using) in ur machine.
and then its important to add ..

wins support = yes
wins proxy = yes

in ur golbal section in smb.conf file

here..
01. [Homes] for user home directory. each user can browse there own directory
02. [profile] for user logon and access
03. [Interview] a share, where only interview group can access.
and so on...........

first try to understand my configuration and go ahed. I think u can...............
if u use XP machine then u shoud add ur machine in ur domain. for that u must create a admin user for smb. here i create root,rahul.

if failure allwayes follow the .log file in /var/log/samba/smbd.log or like this (what u declare in global section)


best luck

I'm glad to announce that, I have SOLVED my problem.

There is something called SElinux, an additional security feature on the kernel that comes with FC5, FC6 and I'm sure FC7 too. In order to get samba to work and remove the permission issues (that stressed me). You've to disable it. U can use one of the two method (I have used the first method.)

1. On the Lilo or grub.conf file, append selinux=0 on the kernel line
exampel of my grub.conf
-----------------------------------------------------------------------------------------------------
default=0
timeout=5
splashimage=(hd0,2)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.18-1.2798.fc6)
root (hd0,2)
kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb quiet selinux=0
initrd /initrd-2.6.18-1.2798.fc6.img
title WIndows 2003 Server
chainloader +1
-----------------------------------------------------------------------------------------------------
2. Another method can be found on the following link:
http://lists.samba.org/archive/samba...ay/120625.html

Thanks for the help guys. Looking forward in returning the favor.