drakkarnoir
asked on
SAMBA and applying config changes
Hello Experts,
I made changes to my rc.conf, is there a way to make them take effect without restarting freebsd? And does anybody have some good SAMBA tutorials, I can't get it to work with the handbook.
I made changes to my rc.conf, is there a way to make them take effect without restarting freebsd? And does anybody have some good SAMBA tutorials, I can't get it to work with the handbook.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Now when I go to View Workgroup Computers on my XP client, it says "Workgroup is not accessible". My SAMBA, Windows, and FreeBSD username and password are all the same.
Have you configured the Workgroup setting on your XP Client? You can find that in Start -> Control Panel -> System (then restart your xp computer).
Make sure the workgroup is set to the same as you've set it on the samba share. If you don't have NT or Windows 2000/2003 Servers on your network then you might also want to enable your samba server as:
[global]
domain master = Yes
local master = Yes
preferred master = Yes
os level = 35
wins support = Yes
Then configure your xp clients to connect to your samba server via WINS. You can configure this in network properties in the control panel.
restart samba after any changes.
Make sure the workgroup is set to the same as you've set it on the samba share. If you don't have NT or Windows 2000/2003 Servers on your network then you might also want to enable your samba server as:
[global]
domain master = Yes
local master = Yes
preferred master = Yes
os level = 35
wins support = Yes
Then configure your xp clients to connect to your samba server via WINS. You can configure this in network properties in the control panel.
restart samba after any changes.
ASKER
My workgroup name in SAMBA is "Workgroup" and on my XP Pro machine it's "Workgroup". Before I setup Samba, I was able to see the computer I'm on in the workgroup computers section.
Try making your Samba server be a domain master browser and local master browser as well as WINS, as that will improve your client's ability to find things on the network. You may need to restart your windows clients to flush their cached network info once you've applied the new settings.
also: encrypted passwords = yes
public = yes
If that doesn't work you might want to try:
security = share
as well which loosens some of the restrictions on the server. Check your samba logs for details of any problems. Also run: testparm to make sure that your smb.conf file is syntactically corrrect.
also: encrypted passwords = yes
public = yes
If that doesn't work you might want to try:
security = share
as well which loosens some of the restrictions on the server. Check your samba logs for details of any problems. Also run: testparm to make sure that your smb.conf file is syntactically corrrect.
ASKER
I'm using SWAT, so the syntax has to be right?
From the Samba install notes:
Test Your Config File with testparm
It's important to validate the contents of the smb.conf file using the testparm program. If testparm runs correctly, it will list the loaded services. If not, it will give an error message. Make sure it runs correctly and that the services look reasonable before proceeding. Enter the command:
root# testparm /etc/samba/smb.conf
Testparm will parse your configuration file and report any unknown parameters or incorrect syntax.
Always run testparm again whenever the smb.conf file is changed!
Test Your Config File with testparm
It's important to validate the contents of the smb.conf file using the testparm program. If testparm runs correctly, it will list the loaded services. If not, it will give an error message. Make sure it runs correctly and that the services look reasonable before proceeding. Enter the command:
root# testparm /etc/samba/smb.conf
Testparm will parse your configuration file and report any unknown parameters or incorrect syntax.
Always run testparm again whenever the smb.conf file is changed!
ASKER
Said it was okay
and did you do all the other stuff (set master domain browser, local master browser, wins support, etc.) ?
post your smb.conf
ASKER
Op, I got it working. Turns out I needed to run the Network Wizard in XP. Thanks :)
ASKER
Ah geez, says I don't have write access to it, even though I put "No" to Read Only in my share group called "home"
check the permissions set on the actual directory (ie. ls -la /path/to/directory/you/are /sharing)
Then if necessary:
chown -R user:group /path/to/directory/you/wan t/to/share
(user being the user and/or group that you want to allow access to)
chmod -R 777 (or 775, etc.) /path/to/directory/you/wan t/to/share
ensure you have:
writeable = yes
in your smb.conf entry for that particular share.
restart samba ( /usr/local/etc/rc.d/samba. sh restart )
You can also use the force user = and force group = parameters in smb.conf to ensure that all permissions are treated as a particular user regardless of who logs in.
Then if necessary:
chown -R user:group /path/to/directory/you/wan
(user being the user and/or group that you want to allow access to)
chmod -R 777 (or 775, etc.) /path/to/directory/you/wan
ensure you have:
writeable = yes
in your smb.conf entry for that particular share.
restart samba ( /usr/local/etc/rc.d/samba.
You can also use the force user = and force group = parameters in smb.conf to ensure that all permissions are treated as a particular user regardless of who logs in.
ASKER
Made another question, not fair to keep asking you new questions on the same thread.
ASKER