Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So I've already edited the registry entry necessary to see linux samba shares. However, I'm still running into an issue with even the most basic shares. I am running Fedora Core 10 and building a NAS out of it. Everything's kosher so far but I can't get the Samba shares up and running. I'll worry about writeable user share later but right now I have the following smb.conf file:
Code:
[global]
workgroup = WORKGROUP
netbios name = NUVNETNAS
security = share
[NAS_PUBLIC]
path = /home/NAS
read only = Yes
guest only = Yes
I've set up the firewall to allow Samba client and server traffic and set my file permissions for /home/NAS to 775. Yet I still get the following message:
Quote:
Windows cannot acesss \\NUVNETNAS\NAS_PUBLIC
Check the spelling of the name. Otherwise there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.
Could it have something to do with the fact that I set up my NAS in the home directory? Is there some SELinux policy that would hamper this? Thanks in advance for serious replies!
So I've already edited the registry entry necessary to see linux samba shares. However, I'm still running into an issue with even the most basic shares. I am running Fedora Core 10 and building a NAS out of it. Everything's kosher so far but I can't get the Samba shares up and running. I'll worry about writeable user share later but right now I have the following smb.conf file:
Code:
[global]
workgroup = WORKGROUP
netbios name = NUVNETNAS
security = share
[NAS_PUBLIC]
path = /home/NAS
read only = Yes
guest only = Yes
I've set up the firewall to allow Samba client and server traffic and set my file permissions for /home/NAS to 775. Yet I still get the following message:
Could it have something to do with the fact that I set up my NAS in the home directory? Is there some SELinux policy that would hamper this? Thanks in advance for serious replies!
Run the command testparm, if the command run correctly this will load all the services , if not will give you errors.
Testparm will parse your configuration file and report any unknown parameters or incorrect syntax.as root run :
Load smb config files from /etc/samba/smb.conf
Processing section "[NAS_PUBLIC]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
security = SHARE
[NAS_PUBLIC]
path = /home/NAS
guest only = Yes
guest ok = Yes
If you are using a router you have to open samba port on the router, also to test try to disable the firewall on windows, perhaps windows vista firewall is blocking access.
If you are using a router you have to open samba port on the router, also to test try to disable the firewall on windows, perhaps windows vista firewall is blocking access.
Have Network Discrover/Filesharing open in my firewall including the protocols. Also, everything's on a local network :/ so there shouldn't be an issue there.
And if you shut down the firewall to test.. does it work ?
Alternately you could leave the firewall up and do packet captures..
It definitely not the firewall. I can access Windows shares from THIS linux box, just not visa versa. I have a linux laptop that I can still access shares from my Vista/Windows 7 machine with no trouble, so it has to be something with this machine. Both Fedora and my Vista/Windows 7 firewalls are configured correctly.
Every Morning I fire up Linux and Restart the Network and then Reload Samba
[code]$ /etc/init.d/networking restart
[\code]
and then
[code] $ /etc/init.d/samba reload
[\code]
Need to look in /etc/init.d to see if the script is named "network" or (as in my case) "networking" and adjust accordingly.
I went round n round with "smbstatus" and "testparm" and the samba shares were invisible to Vista until I initiated the regimen above.
Goof Luck
Never tried that before, but didn't seem to alieviate the issue. The worst part is, NUVNETNAS shows up on the network and NAS_PUBLIC is visible as well :/. Thanks for the tip though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.