School switching some boxes to linux, showstopper: samba
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.
School switching some boxes to linux, showstopper: samba
Hi,
My school is currently thinking about switching the computers in the computer science department from windows to linux (fedora).
But first, here is what the linux box has to be able to do.
Security (DONE)
Office Suit (DONE)
Java Compiler and Tools (DONE)
Print to tcp/ip printer. (DONE)
Connect to Mac-OS X samba-enabled shares (PROBLEMATIC)
Mounting the samba thing works fine, and I can see the shares, but when I connect to them, and enter in correct authentication, the authentication box reappears, as if saying I have the wrong password.
Also, some shares' names are truncated to 13 characters, and can cause problems while looking it up, why is that?
Have you run smpasswd on the Linux machine? Then (if you have) make sure you have in the Linux machine's smb.conf something like:
[JEAN_DEVEL_YIELD]
path = /usr/local/apache2/htdocs/php/yield_jean
guest ok = no
writeable = yes
create mode = 0777
directory mode = 0777
browseable = yes
public = no
username = jean
read list = jean
write list = jean
valid users = jean
(where of course, the smbpasswd user you added was called jean)
Then, when using OSX to go to the share (I use XP, so I'm guessing here) type the smbpasswd'ed username in the connect box, and the password you assigned. See man smbpasswd for more info.
Oh yeah - strange thing: to get this working with my Rh9 system and my Windows machines, I had to call smbpasswd TWICE for every user I wanted to add before it would work from the Windows machines.
I saw a post on the Apple discussions - server software site which said there were problems with OS 10.3 software with Samba shares more than 12 characters long - when connecting with Windows clients. I know it's not your problem, but it seems similar enough to mention. Personally I've had no end of trouble with windows 95, 98 and XP connecting to MAC OS 10 server samba shares. So much so that I eventually advised people to connect with ftp via a web browser (and even that mysteriously stopped working for some users (but not others) after a few weeks, and I had to delete and re-install the user).
Could you try NFS shares perhaps instead? - I think the OSX server guides seem to encourage this connection method for Unix based clients.
The fact remains that although the XServe is a very beautiful object, we are paying dearly to beta test the server software, which is decidedly flaky - then they bring out a new version which fixes some problems and creates others (don't even think about "mobile accounts"!) which we then pay for all over again, and beta test again. I can't help thinking that if we'd started off with Yellow Dog Linux, we'd have had more success, fewer problems and the learning curve would, with hindsight, have been only slightly steeper.
Unfortunately Apple's samba implementation is quite dubious. This includes 10.4. It all depends on your luck. In this case I would concentrate on OS X samba side to try and fix the problem. To see if linux is configured properly connect to windows shares. This will work if config is o.k. Unfortunately is is more tricky ( if at all) with OS X.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.