Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
At work, everyone connects using //server/home no matter that user at each terminal they log in at.
At home, my users can only connect using //server/theirusername.
I'm not sure if it's a setting in the samba config that enables the network login to see the user login and map as //server/home rather than //server/theirusername at work.
At home, users in my network at home can only connect using //server/theirusername for each user.
it doesn't mean "just that". I'm still unsure what you actually mean. What do you mean by connect? That's a cifs share, so how does a user choose it? Are these users the same people? Is that relevent? Do all your colleagues also live in your house? Please give specific terms, not generalizations that can be taken in many different ways.
Last edited by acid_kewpie; 02-20-2012 at 08:52 AM.
At work, my business has Samba running off of a Linux box and Windows users for the entire business map from their individual Windows desktop machines using "map network drive" to their home share on the Linux box using //server/home.
So my user is reckless2k2 and I map using //server/home rather than //server/reckless2k2. Any other user at my work maps using //server/home and never have to put in their username after the //server. Like Jenny doesn't map the network drive as //server/jenny. She's maps the network drive on her Windows machine at work as //server/home.
At my house, I have Samba running on a Linux box and Windows machines mapping their network drives but they can't map //server/home. So my user at home is reckless2k2 and I have to map using //server/reckless2k2.
Why is that? I assume it has something to do with a config in the Samba file. At home, I'd like any of my users to map to their Samba share using only //server/home. I assume the Linux box has to understand that reckless2k2 is mapping so it can map using //server/home rather than //server/reckless2k2.
Primary domain controller must be on the Samba box? OpenLDAP must be on the Linux box?
Well that wasn't at all what I thought you meant, I would have guessed this was Linux clients to a Windows server.
I think you're referring to the [homes] section of smb.conf, I think the difference is probably that at work they set a dynamic path, e.g. "path = /home/%u" which would NOT be in a [homes], whereas you are not, and instead have a "valid users = %S" entry or similar IN a [homes]?
You are correct. My smb.conf [homes] section refers to valid users = %S.
Are you saying they are using something else like a combo of NFS along with NIS or OpenLDAP and then the 'path = /home/%u' to get this mapping at work?
I'm not sure if you are saying that I can't do this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.