On Wed, 10 Jul 2002, Bob Latham said: > In article > John Karns <[EMAIL PROTECTED]> wrote: > > On Tue, 9 Jul 2002, Bob Latham said: > > > Presumeably the smb daemon is running on your server. > > service smb restart - works fine as far as I can tell. Does that answer > the question? > > > It helps to use the same pw on the MSW side as the samba side (yields an > > auto-login to samba), but it's not necessary, as samba will prompt for > > the pw if needed. > > Tried this, created a user and password on the linux box that matched that > already in use on the PC but still no better.
As long as you're just testing for your own purposes and since you've disabled encrypted pw's on W98, then try turning off samba's encryption as well. It definitely won't work with MSW set one way and samba set the opposite. > > Samba keeps it's own pw file called smbpasswd. Each user who wants > > samba access must have an entry in that file. Depending on what smb > > version you're using, it may be a multi-step process. The process was a > > bit awkward with older smb versions, as it was necessary to manually add > > the user entry in the smbpasswd file. > > I know this sounds a bit vague but last week I read somewhere (can't > remember where) that I needed to type a line of geek speak into the > command line in order to create the smbpasswd file. I did this and the > file was created. I thought that was it. Yes, that would have been it- but if samba was installed from a distro such as RH. SuSE, etc., then that shouldn't have been necessary, as the distro would have installed one. Before creating new files it's a good idea to see if it may already be on the system; try "locate smbpasswd" and see what comes back. One thing that can be confusing is the location of the files though. I don't remember if you mentioned what distro you're using, but the samba docs and howTo's tend to use the "stock" defaults, whereas if samba was installed from your distro CD's, then chances are good that they have changed things, and samba is using different cfg and pw files than you assume. In any case, what you created with your "line of geek speak" was to create the file. It wouldn't have contained any valid pw's, so running the smbpasswd utility was still required. > > With current versions, one simply > > needs to run the utility smbadduser. It will prompt for the user name > > and pw. > > Hmm, just had a stab at this. It appears to want 2 IDs separated by a ":" > and then a password. I've no idea why it need 2 IDs. I took a guess and > made them both the same ie. smbadduser user1:user1 and when asked password > = dogslife. Needless to say, it's made no difference. Still can't connect. Was the user indeed added? Did you check the smbpasswd file to confirm it? What version of samba are you running (smbd -V)? With 2.2x, then the functionality of smbadduser was integrated into smbpasswd (see the smbpasswd man page). > > > Someone sent me a W98 registry hack to make w98 use none encrypted > > > just as an experiment. That didn't connect either. Anyone know of an > > > anti-hack to put it back to the same as the others? > > > You will probably have to run regedit on the MSW machine to change it > > back, I believe. > > Sounds about right to me. > > > See the samba docs for more info; it is pretty well > > covered there. Look for a file called passwords.text > > As I say, I am very new to this. Where on the planet would I look for such > a document - not having any clue you understand. http://www.samba.org (http://www.google.com/linux is your friend) ---------------------------------------------------------------- John Karns [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek PC Mods, Computing goodies, cases & more http://thinkgeek.com/sf _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
