Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
localhost refers to the local loopback adapter. This is a virtual device with the IP address 127.0.0.1. So you might be trying to access the client computer and not the server. Is your linux box hostname localhost?
Add this line to your smb.conf file.
netbios name = server
Change server to anything you want. This name will then be displayed in windows network neighborhood. Be sure to restart samba. It might take several minutes for windows to actually see the new name in network neighborhood.
An Internet Protocol (IP) address in a nutshell is a unique number that identifies devices on a network.
localhost refers to the local loopback adapter. This is a virtual device with the IP address 127.0.0.1. So you might be trying to access the client computer and not the server. Is your linux box hostname localhost?
Add this line to your smb.conf file.
netbios name = server
Change server to anything you want. This name will then be displayed in windows network neighborhood. Be sure to restart samba. It might take several minutes for windows to actually see the new name in network neighborhood.
An Internet Protocol (IP) address in a nutshell is a unique number that identifies devices on a network.
Hi there!
This is my first post, so I expect an answer :-)
I hve the same problem, mentioned above. I've changed 'netbios name' variable, but the problem remains. It it still represented on the network as 'localhost', and I can't access it.
After I set it up, I could see my server. It was named 'Localhost' and I could not access it. After I read here that the problem can be in the name 'localhost' (because of a loop back driver), I've set up a new 'netbios name', but from then, I can't see my Samba server.
After every change I restart Samba server.
Confusing is that, that I can see shared contents calling smb://192.168.1.34/ from browser (on local computer, of course).
When I type in terminal command smbclient -L localhost -U% I got this result:
Sharename Type Comment
--------- ---- -------
netshare Disk
IPC$ IPC IPC Service (Samba Server Version 3.0.25-2.fc7)
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.25-2.fc7]
Server Comment
--------- -------
ACA-SASKA
LOCALHOST Samba Server Version 3.0.25-2.fc7
Anyway, the problem remains. I can't see the samba server anymore from local computer (except from browser), and also from any other computer on the network. I could see it as a 'localhost' before (just see, not access), and now I can't.
This is the part of my smb.conf file:
Quote:
[global]
workgroup = WORKGROUP
server string = Samba Server Version %v
netbios name = Gigabyte-Fedora
[netshare]
path = /share
public = yes
writeable = yes
The problem was, that in Fedora 7 you must separately start SMB and NMB services, as they are separated. In previous versions of Fedora, NMB was a part of Samba, so it was enough just to start SMB service.
In terminal, type next two commands: sudo /etc/init.d/smb start sudo /etc/init.d/nmb start
To start automaticly SMB and NMB services on boot, type these two commands in terminal: sudo /sbin/chkconfig --level 35 smb on sudo /sbin/chkconfig --level 35 nmb on
Distribution: Real geeks know Linux is Linux (Ubuntu, Suse, Mandriva, etc....)
Posts: 5
Rep:
Must give access to parent directories
I just spent a couple hours trying to figure this one out.
I was trying to share a sub-folder, but I hadn't allowed anyone to browse into the parent folders.
So I guess make sure your parent folders allow access if you want to share a sub-folder.
I'm not sure if this is the cause of your problem, but it is worth a try, especially since I was getting the exact same message, and it fixed my problem.
The first thing to do is to give your computer a real hostname. Localhost is an alias for 127.0.0.1 so if a client computer tries to access your server's share by the hostname "localhost", it will resolve to the client machine instead of the server.
Also post the [General] portion of your smb.conf config file. Make note of the "Security =" line. If it isn't present, then the default is "Security = User". If this is the case, make sure you use the "smbpasswd" program to enter your username & password in samba's smbpasswd file.
Another thing to check is that you have ports 137-139 open. These are used either for browsing or for transferring files.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.