file-sharing using Samba?
On my own system, I have problems sharing files with Samba. In KDE, I configured file-sharing and tried to share several folders. Then when I checked their properties, it said they were not shared. I read several articles about how to set up Samba and tried some things in smb.conf, but it still did this. Has anyone had this problem and figured out a solution? The folders I am sharing are set a+r, a+x, though I may not set a+w on them all.
|
Which distribution and release are you running?
Are you sure the smbd and nmbd services are running? Maybe it is a KDE problem. Have you tried using the SWAT service? It gives a web-based GUI to configure SAMBA. Have you tried to use the samba share? If so, did it work? If it failed, what error did you get? Would you post the contents of your smb.conf? |
I am using Slackware 13.37 and the 64-bit one on this computer. Ps showed smbd and nmbd (I had also tried restarting smbd after updating smb.conf.) I had not heard of SWAT. I was able to access my files on a Windows machine using Samba; I just cannot share files from GNU/Linux to Windows. I did try to access smb://var/spool/samba or something in a file manager, and it seemed to work, though there was of course nothing there. Below is my smb.conf (omitting the header.) My router can assign specific IP addresses to machines, which is why I edited the allowed IP addresses, though that should not really be relevant to the question.
Code:
[global] |
On your Samba server:
Run the testparm command to validate your smb.conf file. Then run smbclient -L localhost After entering a password you should see a list of available shares. If you have another Slackware machine, you can run smbclient -L sambaserver, where sambaserver is the hostname of the Samba server. You should see the same result as when run locally. |
I think it would be a good idea to troubleshoot samba first, and worry about KDE later.
When you tried to access samba from the Windows machine, what UNC path did you use, and what error did you get? It can help to note the hour and minute. Then look for more details in the messages around that time in the Event Log on the Windows machine and /var/log/samba* on the slackware machine. |
I did what Woodsman said, and it seemed fine, but after entering the password I set up reading some tutorial, I always got the following error.
Code:
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Thanks again, everyone, for the suggestions so far. It will not be until the weekend that I want to try to share the files, but I guess I could try SWAT or something if they can be accessed on the Slackware machine to test. I uncommented swat in inetd.conf; I will try it soon. |
Here's a link to the guide I used to learn Samba setup.
http://alien.slackbook.org/dokuwiki/...lackware:samba |
Are you using windows 7?
It might be easier to use swat to configure your smb.conf The only shares as seen in the smb.conf file is [homes] which is a special share that creates a home directory for all users. /var/spool/samba is not a share. Can you see your linux computer from windows network neighbourhood? Another method would be to start a windows CMD box and type in the command: net view \\IP_address_of_your_linux_box Did you create a samba user via the smbpasswd command? Try this example with one addition: Code:
# This one is useful for people to share files |
Quote:
Code:
WARNING: Your 'passdb backend' configuration includes multiple backends. This |
I am trying some configurations like yours (also in smb.conf) and in slackass' link. Maybe the problem was not having the paths on Slackware, not having the same workgroup name, and I do not know how to connect from windoze, but my Slackware system was listed when adding a network place. I am able to access one of the paths using Samba on Slackware and will try windoze more tomorrow.
Quote:
Quote:
Quote:
Quote:
|
Do you really need sharing Homes ?
If you want to share some other folders, you may try setting this option in the very beginning of the config file: Code:
security = share Code:
workgroup = WORKGROUP # <---- change to your Windows machines workgroup |
Quote:
That did not work though, and everything else I have tried so far has not worked. Windows recognizes my Slackware system exists, which I can access a public folder on itself using Samba, but nothing more works on the Windows machine yet. |
I decided to use SWAT for now and have started to figure it out (I just dislike having to use a password.)
Apparently putting 'guest only = Yes' under the guest share in smb.conf was one answer (and I saw many) that worked. I also smbclient to set the guest password blank. I also decided to restrict the shared folders on OpenBSD by turning guest access off, but I could still access them from the two other machines without logging in. So, my Slackware problem with this is solved--and maybe it would have worked if I initially set it up differently (since something in Samba seems to keep the same state for a long time)--but my Samba ones are not. |
Here's my own Samba HOWTO for file sharing in a mixed environment :
http://www.microlinux.fr/slackware/L...amba-HOWTO.txt |
Thanks. I will not need to do that yet, since I was talking about two different POSIX-style systems... but it might come in handy. I guess I will mark this solved if I can, since I solved the original problem after Ben mentioned SWAT and I decided to use a password.
|
All times are GMT -5. The time now is 06:17 PM. |