Samab err update

Samab err update

Post by J Steinber » Fri, 07 Dec 2001 07:23:35



I turned on encryption in smb.conf and now both win clients get a password
dialogue, but entering

unix acct's and passwords fail. I also enabled user name mapping , etc

It still won't recognize neither smd mapped users or users native to that
machine.

Any tips would be appreciated!

JSS

 
 
 

Samab err update

Post by Karl Heye » Fri, 07 Dec 2001 09:46:42



> I turned on encryption in smb.conf and now both win clients get a password
> dialogue, but entering

> unix acct's and passwords fail. I also enabled user name mapping , etc

> It still won't recognize neither smd mapped users or users native to that
> machine.

I'm guessing you haven't setup the accounhts in the smbpasswd file
correctly,  have you used smbpasswd -a <windows username> yet

karl.

 
 
 

Samab err update

Post by Dean Thompso » Fri, 07 Dec 2001 23:30:08


Hi!,

Quote:> I turned on encryption in smb.conf and now both win clients get a password
> dialogue, but entering

> unix acct's and passwords fail. I also enabled user name mapping , etc

> It still won't recognize neither smd mapped users or users native to that
> machine.

> Any tips would be appreciated!

What configuration have you got the SAMBA system set up in.  If you are set up
for the security mode "user" then you are going to have to generate the
accounts like Karl said, if you want, an easier solution might be to go into
"share" mode, but it really does depend on what you want.

Have you taken a look at the SMB-HOWTO document (http://www.linuxdoc.org) ?

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

1. semop ERANGE err update

I found the bug.  Turns out the Linux code uses

static struct sembuf sops_lock = {0, -1, SEM_UNDO};
static struct sembuf sops_unlock = {0, 1, 0};

to pass to the semop() call for locking and unlocking.

I found that the 3rd argument (zero) for sops_unlock
is supposed to be SEM_UNDO, not 0.  SEM_UNDO is
defined as 10000, not zero on the system.  The mere
fact that it works so well on linux is scary, or
even works at all on both systems amazes me.

Seems to work great now!

Thanks for the help.
Jeff

2. unprofessional software writers can't write secure code -- FrankenTROLL

3. taper: sense data err/ creating device err [urgent!]

4. Slackware 3.2, passwd and shadow

5. Err#62 and Err#91s from hung Java threads on Solaris 7

6. Linking for libc5 under libc6

7. 2.2.13 "invalid compressed format (err=1 or err=2)"

8. Compaq Deskpro 166

9. Samab for multiple workgroups

10. Stale NFS file handle and Samab

11. FYI: Updates On SCO Updates

12. kconfig update, GTK+ updated

13. Is it possible to update PCI 2.1 to PCI 2.2 by updating BIOS?