Linux - General This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
07-28-2007, 11:11 AM
|
#1
|
|
LQ Newbie
Registered: Jun 2007
Location: cairo , Egypt
Distribution: Fedora
Posts: 25
Rep:
|
Samba (sharing with M$ Windows) Problem ?!
i get this error massage when i try to open my sharing folder from the windows network folder
The folder contents could not be displayed.
"Windows Network: localhost" couldn't be found. Perhaps it has recently been deleted.
i dont know what is wrong i have tried every thing in configuring the sharing folders
- from the conf file
- from samba GUI
- permission to all user to read and write
i really want to know what is happening... 
|
|
|
|
07-28-2007, 11:29 AM
|
#2
|
|
Senior Member
Registered: Nov 2006
Location: California
Distribution: Fedora , CentOS , Solaris 10, RHEL
Posts: 1,763
Rep: 
|
have you tried connecting with an IP address?
|
|
|
|
07-28-2007, 08:01 PM
|
#3
|
|
LQ Newbie
Registered: Jun 2007
Location: cairo , Egypt
Distribution: Fedora
Posts: 25
Original Poster
Rep:
|
sorry ,i dont know what are u talking about
|
|
|
|
07-30-2007, 11:29 AM
|
#4
|
|
Member
Registered: Sep 2006
Location: Canada, Alberta
Distribution: RHEL 4 and up, CentOS 5.x, Fedora Core 5 and up, Ubuntu 8 and up
Posts: 251
Rep:
|
when you connect to your SAMBA share from your windows machine try this:
\\192.168.0.111(YOUR SAMBA machines IP)\share_name
So i have a share like this:
\\192.168.0.101\media
|
|
|
|
07-30-2007, 11:46 AM
|
#5
|
|
Member
Registered: Sep 2006
Location: Canada, Alberta
Distribution: RHEL 4 and up, CentOS 5.x, Fedora Core 5 and up, Ubuntu 8 and up
Posts: 251
Rep:
|
How to map a Network Drive
here i made this for you (and others):
How to Map a Network Drive
if you dont know your password then you will need to reset it (if you have admin rights) or else contact your network administrator.
if you need any help feel free to e-mail me
|
|
|
|
07-30-2007, 11:55 AM
|
#6
|
|
Moderator
Registered: Aug 2002
Posts: 10,684
|
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.
|
|
|
|
08-27-2007, 10:51 AM
|
#7
|
|
LQ Newbie
Registered: Aug 2007
Posts: 8
Rep:
|
Problem accessing files - Samba
Quote:
Originally Posted by michaelk
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.
Regards...
|
|
|
|
08-27-2007, 02:21 PM
|
#8
|
|
Moderator
Registered: Aug 2002
Posts: 10,684
|
a.ilic,
Welcome to LinuxQuestions. What linux distribution/version are you running?
Did you restart samba?
|
|
|
|
08-28-2007, 08:01 PM
|
#9
|
|
LQ Newbie
Registered: Aug 2007
Posts: 8
Rep:
|
Quote:
Originally Posted by michaelk
a.ilic,
Welcome to LinuxQuestions. What linux distribution/version are you running?
Did you restart samba?
|
Thank you.
I use Fedora 7 (kernel 2.6.21).
This is the manual that I used to set up Samba server.
http://www.mjmwired.net/resources/mj...-f7.html#samba
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:
Quote:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.25-2.fc7]
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
Workgroup Master
--------- -------
WORKGROUP ACA-SASKA
|
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
|
Any help is welcome. Thanks in advance!
|
|
|
|
08-30-2007, 06:48 PM
|
#10
|
|
LQ Newbie
Registered: Aug 2007
Posts: 8
Rep:
|
I found solution on page:
http://forums.fedoraforum.org/forum/...d.php?t=164650
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
Problem solved!
|
|
|
|
09-09-2007, 07:26 AM
|
#11
|
|
LQ Newbie
Registered: Jun 2007
Location: cairo , Egypt
Distribution: Fedora
Posts: 25
Original Poster
Rep:
|
i have done that already but no use i guess this is another thing
|
|
|
|
01-26-2008, 11:43 PM
|
#12
|
|
LQ Newbie
Registered: Apr 2005
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.
|
|
|
|
01-26-2008, 11:53 PM
|
#13
|
|
Moderator
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733
|
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.
Last edited by jschiwal; 01-26-2008 at 11:54 PM.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:30 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|