Samsung phones only from AT&T
Mac OS X 10.4: SMB connection problems, solutions
Some users experience issues connecting to SMB (Samba) shares under Mac OS X 10.4 -- usually resultant in error -36.
SolutionsResourcesChanging the SMB configuration file MacFixIt reader Jim reports that changing a line in the smb.conf (configuration) file to be uncommented resolves the issue in his case.
Jim writes:
"I've solved my Samba problems - it seems Tiger is sending encrypted passwords. If Samba isn't configured to receive them, Tiger can't log in.
"In smb.conf, the line:
- encrypt passwords = yes
"must be uncommented (make sure there is not a ";" at the beginning of the line).
The smb.conf file is located at /usr/local/samba/lib/smb.conf.
You can access the smb.conf file in the terminal via the command:
- sudo vi /etc/smb.conf
which will open smb.conf in the text editing utility "vi".
Re-establishing keychain passwords Resetting keychain passwords (deleting then re-entering them) can resolve some SMB networking issues introduced by Mac OS X 10.4. We've since received several notes of confirmation for the fix.
MacFixIt reader Stewart writes:
"I could connect to other Windows machines successfully under Tiger, however, with one particular Windows machine, I get the following error: 'The finder cannot complete the operation because some data in 'smb://(windows machine' could not be read or written Error Code -36 )'."
"It was Keychain. I reset my keychain and everything worked. I can now logon to a share in that windows machine. I had copied the keychain from Panther to Tiger installation for my main user. I found this by logging into another user on my Mac and found that I could connect to a share ( and this one had the default tiger keychain ). I found the keychain item that was problematic, removed it and now everything is fine."
I find the instructions for fixing the -36 error confusing/contradictory
""I've solved my Samba problems - it seems Tiger is sending encrypted
passwords. If Samba isn't configured to receive them, Tiger can't log in.
"In smb.conf, the line:
encrypt passwords = yes
"must be uncommented (make sure there is not a ";" at the beginning of the
line)."
If Tiger is sending, by default, password encrypted, then how would
uncommenting "encrypt password = yes" fix the probem?
Would Tiger then not start sending password encrypted?
In addition, when I looked at my smb.conf in terminal, the line is already
uncommented ... and I have not change my smb.conf file ... it is the default,
out-of-the-box version.
Also, for us not techno-geeks a more detailed explanation of how to change
the file in "vi" woul dbe useful.
Thanks.
It would seem that "commenting" the entry and disabling encrypted passwords might be the thing to do. I wonder if the original poster could comment on this.
ps. Please ignore my question about terminal, I've figured that out.
Hi there!
I am having problems getting into the smb.conf line code to make the change to be uncommented to mount a NAS unit. I see you were experiencing similar problems - how did you eventually get to alter the code? Any tips would be much appreciated.
Best wishes, Clem
- by lesliemd1956 May 25, 2005 7:51 PM PDT
- I have this problem on my new powerbook which came with Tiger. I am a
- Like this Reply to this comment
-
(4 Comments)switcher from PC to MAC (YAY!!!) When I type the command sugggested into
terminal, I am prompted for a password, and none of my system passwords
work. How can I fix this??
Leslie