Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
I'm running CentOS 6.4 and having a problem with Samba shares. All my Windows based computers cannot see CentOS shared folders in the Workgroup, but can open them by IP. Also there is a NAS drive that all Windows boxes can access by name, but CentOS server cannot, only by IP. I did my tests on my home network before getting this box installed at my friend's shop, and everything worked. What do you think? Could be the network issue, or my configuration?
This CentOS box should replace old Windows2003 server.
Here is my smb.conf:
Code:
[global]
workgroup = MYWORK
netbios name = SERVER1
server string = My File Server Version %v
log file = /var/log/samba/log.%m
max log size = 50
idmap config * : backend = tdb
cups options = raw
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
print ok = Yes
browseable = No
[data]
comment = Samba Data Share Directory
path = /media/share_data/data
valid users = @shareusers
force group = shareusers
read only = No
create mask = 0770
[installs]
comment = Samba Install Packages
path = /media/share_data/installs
valid users = @shareusers
force group = shareusers
read only = No
create mask = 0770
[printer_scans]
comment = Samba Printer Scans
path = /media/share_data/printer_scans
valid users = @shareusers
force group = shareusers
read only = No
create mask = 0770
If everything worked at home, but doesn't at your friend's, then it must be his/her network setup. Are the machines all running the same Windows version? Is the work group name correct? Did you wait a while; Windows networks seem flaky in general in terms of refreshing time...
firewall of windows clients should allow file and print sharing,add the exception to windows firewall or disable it..
Windows firewall doesn't block view of the all available computers on the Network, it blocks the access it self, and we can access to shares by IP. So, its not THE reason.
Well, we ended up with updating shortcuts on the desktops to use IP address.
I'm not marking this thread as SOLVED, just in case for some other ideas.
linux can not resolve netbios names to IP addresses without a little help. You have a few options ie.e use the hosts or lmhosts file, configure samba as a WINS server or use a local DNS. With only a few devices on the network the hosts or lmhosts file is the easiest. The second easiest is configuring samba as a WINS server. In a nutshell samba always becomes the master browser and your windows PCs use it to find the server and other windows devices. The server can also use WINS to resolve netbios names to IP address.
What version of windows is running in the shop? As stated the workgroup name should be the same on all computers. Are the computers configured for a homegroup?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.