Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
May be dumb to ask but you did create the Samba password file and added passwords for your users? Reason I ask is because I have searched quite a few links and the response to that error is usually just that. Here is the commands I used to add my users:
Also found some interesting info if your are running Samba 3.0, pulling straws at this point:
The following issues are known changes in behavior between Samba 2.2 and
Samba 3.0 that may affect certain installations of Samba.
1) When operating as a member of a Windows domain, Samba 2.2 would
map any users authenticated by the remote DC to the 'guest account'
if a uid could not be obtained via the getpwnam() call. Samba 3.0
rejects the connection as NT_STATUS_LOGON_FAILURE. There is no
current work around to re-establish the 2.2 behavior.
You gave me the hint I needed. I re-read the man page on smbpasswd which caused me to check the status of the "Allow null passwords" and it was set to no whereas the smb users were setup with no passwords.
I am using Webadmin to administer Samba 2.2.8. I did try the "Allow null passwords" equal to no with the Samba users setup to use their current passwords, but that did not work, so will have to stick with less security and at last the ability to use the ample disk space on the Linux server.
Yes also set the shares up with writeable = true and no change in behaviour. I am getting the feeling the expertice to answer this might only be found on the Samba mailing list. Seems th esame with my iptables question, mailing list is the next option.
Shame, because linuxquestions used to be good a year ago when I first got into Linux now, a year later, I have not had a single question answered. such is life.
I have the exactly same problem, and i also been looking for the answer for the last couple days but can't find anything and another problem is i can't get the windows to see the linux's share, if u found an answer to this please do not keep it as a secret.
Jun 29 04:12:09 linuxbox nmbd: [2003/06/29 04:12:09, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(359)
Jun 29 04:12:09 linuxbox nmbd: find_domain_master_name_query_fail:
Jun 29 04:12:09 linuxbox nmbd: Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Jun 29 04:12:09 linuxbox nmbd: Unable to sync browse lists in this workgroup.
Could this be the reason I cannot now see my shared drives on the linuxbox? What causes this? testparm smb.conf passes without error?