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.
Hi there, I have a Samba book, and instructions to learn Samba.
So far, I have installed it using a script written by our incredibly busy Linux guy whom I never see. We have it on a main server here and it works like a charm. Not much to it. I'm going to dive into this book on Sunday when I actually have time to go home from work.
Question I have:
1. Any real commmon problems, issues people face when using it?
Any tips would be great. I've been given the task of learning Linux, along with about 50 other "to be done immediately you stupid worker" tasks. Ugh.
Keep in mind that if you have Window$ machines on the network (95/98), they send encrypted passwords to Samba server. You MUST specify the following somewhere in the [global] section on your Samba server:
encrypt passwords = yes
If you dont, and you do not have proper permissions on the directories and files you are trying to share, you will have trouble. By default, UNIX and Linux use plaintext passwords. Also, make sure that your smbpasswd file is created and that you have a user account on the Samba server matching the user account on the Window$ machine you are logged into. So, if you are logged into Windows as follows:
Username: Foo
Password: linux
make sure you have a similar account on Window$ with same username and password.
If you remember this, the rest is preety straight forward.
Watch out for NT Quirkstation. We use domain logons for Win9x boxes and it's great for making a 'portable' desktop/My Docs environment. However a Win NT workstation set up this way will chew up the user.dat. I just kept the one NT box to a 'workstation' login, then mounted the 'shares' while on the same Windows domain.
I never really got around to finding a fix for it, but I'm sure there is one. (Cheking User environment at login and using different login scripts seems to ring a bell)
All is much better now as I squeegeed the NT4 install and replaced it with SuSE
As mentioned by breeze the crypt_passwords part was a hassle for me as I misread the docu (ugh) and failed to understand the importance of the sequence of events for a proper passwd migraton.
I don't sync unix passwords. I don't want bodies ssh -ing to the samba servers.
Build your windows logon scripts wiht a text editor that handles <cr/lf> in windows style. Notepad type editors will do fine, vi will cause the .bat files to be mis-interpreted.
We have been forcing the 'mask' for public dirs so that only an admin can remove files. This kluge was inmplemented after an unfortunate Win virus that went after any .jpg that the unlucky victim had r/w access to. It also forced users to a primitive (albeit space-wasting) revision system. ie: Tom bulds a Word doc and saves it in the pub folder. Dick can open the file but can only ..save|new. Harry can look for the most recent doc version and open and ...save|new. etc...
Have a good look at Samba 2.2.x - I haven't upped to it yet, but 'they' all say it's worth it. 'Specially in a mixed environment (NFS/Samba shares and file locking).
If a networked environment is new to your workplace, get a good backup plan in effect. Then inform users that the server gets backed up frequently (every night, right?) and that work-related stuff should live on the server. In my experience most new users tend to just keep saving new work files to the desktop rig, with the intention of "copying over the files at the end of the day". Yeah, right. This makes bosses happy as most desktoppers dont back up or back up and leave the cartridge (or floppy!) in the drive. Now it's your job is to ensure HUGE uptime.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.