Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Why this is necessary' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Why this is necessary
Authored by: andrewz on Aug 26, '02 02:38:24AM

When you set your Mac OS X (UNIX) account password, it stores a hashed (encrypted) version on disk. For example, if your password is "MacsRule!", it might store "K$sJ4%3La". When you authenticate, it hashes what you type using the same algorithm and compares the result against the version on disk. Your actual password isn't stored anywhere, and there isn't any way to get the real password from the hashed one.

Windows uses a different hash algorithm, so Mac OS X 10.2 stores two different hashes of your password -- for authenticating from UNIX and Windows respectively. If the system only has the UNIX hashed version, then you need to enter the original password again to store the Windows version. (Note that Mac OS X does not mind if the password is the same when you do this.)



[ Reply to This | # ]
SMB & Active Directory
Authored by: lucky on Aug 26, '02 04:51:23AM

Sorry this hint dosn´t work for me (i have updated from 10.1.5 to 10.2 - no clean install). When i select "connect to server" i see the Windows Server, i select and the authentivication dialog comes up, but after authentification i got this errors -36 or -50?
But when i enter the full path with the authentivication like:
smb://workgroup;user:password@server/share
everthing works fine!
What´s wrong or where can i find more information about OSX and SMB or OSX and the ACTIVE DIRECTORY?



[ Reply to This | # ]
Why this is necessary
Authored by: harpdog on Aug 26, '02 03:20:17PM

Thanks for the hints it worked a treat for me.



[ Reply to This | # ]
10.1.5 Users on 10.2 upgrade
Authored by: CJLinst on Aug 29, '02 04:33:41PM

I, too, would get an authentication error using a 10.1 user after upgrading to 10.2. Simply changing the password didn't work for me. It appears jaguar stores SMB passwords in /var/db/samba/hash with a file for each logname. This directory did not exist until AFTER I added a user with "Allow user to log in from Windows" checked.

I then disabled the check box for Windows login for the 10.1 user, saved, then re-checked it, saved again, and I now have a hash file for the old user.

I tested authentication using:

smbutil view //localhost

Windows 2000 could mount CJL's home drive WITHOUT changing to clear-text passwords. This is a major improvement over the last time I tried to integrate SAMBA and Windows.

The following also worked:

C:\> NET USE LPT1: \\192.168.0.5\HP_LaserJet_2200 /USER:CJL
Entered Password
C:\> DIR > LPT1:

Viola! Directory listing printed on my shared jaguar printer. Happy day since that's the only laser in the house. The only change I made to enable shared printing was the [global] "printing = cups" line.



[ Reply to This | # ]