I'm not sure what to tell you guys, other than it works for me (and I bet you really hate hearing that ;-) All I can say is that pretty much every problem I've had with samba/windoze clients have been due to one or more of the following: 1) My own ignorance (a big one) 2) Flaky hardware/network configuration 3) Broken M$ client stuff/stupid defaults I only have experience with small LANs and 1.9.18p8 & p10 (I haven't tried 2.x yet; it's on my list of things to do, along with about a million other things...) I have one or two suggestions anyway (see below). Alex says:> On my Samba server I can see and store files regardless of > case but some files are not retrievable with W95 complaining > that either the file or the server does not exist. > I have suspected and tested filename case, file permissions, > file locking and code page compatibility but the problem remains.This sounds like a browsing or underlying network problem (it *could* be permission related, but you said you checked that). And Dave Walton says:> 1. Files or directories in a share are visible. > 2. Files or directories in an all-uppercase subdirectory of the > share are visible. 3. Lowercase or mixed-case subdirectories of the > share appear to be empty. 4. All-uppercase files can be opened. 5. > Lowercase or mixed-case files cannot be opened, and Win95 complains > that the file is not found. 6. Exception to #5: At a DOS prompt, > lowercase and mixed-case files can be opened, but ONLY if the case > is typed correctly. (This does not help with directory access.) > > My setup has: > > case sensitive = no > preserve case = yes > short preserve case = yes > > (Changing those to all "no" has no effect on the problem.)Things that work at the DOS prompt but not in explorer usually point to name resolution or browsing problems (your above case settings look okay). Also, when moving from 1.9.x to 2.x, some of the defaults changed (at least if you expect the same behavior) so you can't just use the same smb.conf file (do read the changes doc in the 2.x package). My setup is for samba to be both the domain and local browse master (no PDC or WINS). My case settings are the same as above (along with "mangle case = yes"). I have exported the /usr/doc tree as a readonly share and the /usr/src tree as well (with a valid users list). These trees have many mixed-case file and directory names, along with both uppercase and lowercase only names. All files and dirs are readable from an OSR2 client. Here are my share definitions: [docs] comment = Linux docs path = /usr/doc public = yes writable = yes printable = no write list = [name changed to protect the not so innocent] [source] comment = Source Code path = /usr/src valid users = [list of valid users with linux accounts] public = no writable = yes printable = no The main difference is that public=no on the second share makes the share invisible to those not in the list of valid users. Here's a short list of gotchas I've run into: Authentication problems -> win95 vredr and NT4SP3 updates require encrypted passwords (or reg hack). NT4SP3 browsing/auth problem -> browsing requires open connection when samba is in user-level security mode (ie, map a drive from a command prompt first). File access problems -> win95 RWIN setting needed "adjusting". Access denied when saving to a share (even though it's set as writable) -> incorrect permissions on the unix side (directory was owned by root). Intermittent browsing problems (LAN wide) -> over the length limit for a linear bus ethernet (ie, too much coax). Other tips: remove NetBlooie and IPX (unless you really need them) and disable the clients from browse master competition (File and Printer Sharing properties in Network properties). Also, make sure you have proper name resolution for both TCP/IP and NetBIOS (ie, some combination of DNS, WINS, hosts, lmhosts, etc). I can usually only spend the time on configuration problems that are directly relevant to work (unless I can do it at home, but I only have a single win95a client at the moment; wait till I finish networking the house...). Also, I'm not really a unix sysadmin or networking guru dude so there're lots of things I don't know. I do know that even a simple setup like mine is a very complex dance between marginally functional clients and a loosely defined and not well documented protocol (SMB) implemented as a software layer on top of a completely different OS & filesystem. And sometimes it's not easy getting everything working right. I'll be glad to try and muddy the waters a little more if you can give some more details on your problems. Regards, Steve ****************************************************************** Stephen L Arnold http://www.rain.org/~sarnold #include <std_disclaimer.h> ******************************************************************
On 3 Mar 99, at 11:54, Stephen L Arnold wrote:> I'm not sure what to tell you guys, other than it works for me (and > I bet you really hate hearing that ;-)You know, I really hate hearing that. :)> All I can say is that > pretty much every problem I've had with samba/windoze clients have > been due to one or more of the following: > > 1) My own ignorance (a big one)If that's the problem in my case, I'd sure love to be enlightened!> 2) Flaky hardware/network configuration2 servers running v1.9.18, Win95 clients work with both. Server 1 upgraded to v2.0.2, server 2 left alone. Win95 clients now work with server 2, but not server 1. Only one thing changed in the network config...> 3) Broken M$ client stuff/stupid defaultsWell, that's a basic assumption. :)> I only have experience with small LANs and 1.9.18p8 & p10 (I > haven't tried 2.x yet; it's on my list of things to do, along with > about a million other things...)Ah, I'm afraid that voids your "it works for me". I never had a problem with v1.9.18. You might want to be very careful when trying out v2.x... (Be sure to let me know how it goes.)> I have one or two suggestions anyway (see below).Suggestions are always welcome, as I've used up all of my own ideas. :(> And Dave Walton says: > > > 1. Files or directories in a share are visible. > > 2. Files or directories in an all-uppercase subdirectory of the > > share are visible. 3. Lowercase or mixed-case subdirectories of the > > share appear to be empty. 4. All-uppercase files can be opened. 5. > > Lowercase or mixed-case files cannot be opened, and Win95 complains > > that the file is not found. 6. Exception to #5: At a DOS prompt, > > lowercase and mixed-case files can be opened, but ONLY if the case > > is typed correctly. (This does not help with directory access.) > > Things that work at the DOS prompt but not in explorer usually > point to name resolution or browsing problems (your above case > settings look okay).It's not name resolution or browsing. I can see the servers and shares fine. It looks as if Win95 (or explorer, anyway) is uppercasing directory and file names, but Samba's case- insensitivity code isn't working right. On the other hand, I can't get into non-uppercase directories from the DOS prompt, even when typed correctly, so it isn't just that.> Also, when moving from 1.9.x to 2.x, some of > the defaults changed (at least if you expect the same behavior) so > you can't just use the same smb.conf file (do read the changes doc > in the 2.x package).I looked through there and played with all relevent settings. No joy.> Here's a short list of gotchas I've run into: > > File access problems -> win95 RWIN setting needed "adjusting".Hello? This sounds interesting. Please elaborate.> I'll be glad to try and muddy the waters a little more if you can > give some more details on your problems.Can it get any muddier? Anyway, the file and directory browsing description quoted above is pretty much the meat of it. But here's another twist -- I now have three machines running Samba: v1.9.18 on FreeBSD 2.2.6 -> Win95 works. v2.0.2 (upgraded from v1.9.18) on FreeBSD 2.2.6 -> Win95 broken. v2.0.2 (fresh install) on FreeBSD 3.0 -> Win95 works. Any FreeBSD people out there able to shed some light on this? I suspect my best bet at this point is to wait until I build a new FreeBSD 3.1 box to replace the 2.2.6 boxes and see what happens. Maybe the whole problem will just vanish... Dave ---------------------------------------------------------------------- Dave Walton Webmaster, Postmaster Emusic walton@emusic.com http://www.emusic.com ----------------------------------------------------------------------
When the world was young, Richard Stevens <Richard.Stevens@gmx.net> carved some runes like this:> I can get all the shares with smbclient -L. When I try to mount > a drive with smbmount, I allways get the following error: > > session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pair > in a Tree Connect or Session Setup are invalid.)[snip]> [tmp] > public=yes > path=/tmp > valid users = rootAre you logging into the client as "root"? Or do you have your client username mapped to root in smbusers? Or are you passing both the username and password via the smbmount commandline? What security setting are you using (ie, user, share, or what?) ****************************************************************** Stephen L Arnold http://www.rain.org/~sarnold #include <std_disclaimer.h> ******************************************************************
samba@samba.org wrote:> > SAMBA Digest 2004 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include: > > 1) oplock release and win 95 > by "Sean Murphy" <sean.murphy@Teltec.DCU.IE> > 2) domain group / users ? > by "Alan Hourihane" <alanh@pinacl.co.uk> > 3) "rename attempted on batch oplocked file" Samba mesg with Source > by "EFT.Eric Devolder" <eric.devolder@eft.be> > 4) Re: Samba Connect Via WIN99 PPP > by RICK_@t-online.de (JUERGEN ANZER) > 5) passwd auth problem > by Richard Stevens <Richard.Stevens@gmx.net> > 6) Extra samba-log appearances > by Raven <raven@Tribe.OnlineToday.Com> > 7) Problems with login > by dutchboy <dutchboy@saintjoe.edu> > 8) trial2: problem with loggin in-- Mit freundlichen Gruessen Dr.-Ing. Dierigen Technische Universit?t Dresden Fakult?t Informatik /MMK