Re: Mac OSX and AD
- From: Scott Lowe <me@xxxxxxxxxxx>
- Date: Wed, 10 Aug 2005 09:36:50 -0400
On 2005-08-09 22:03:01 -0400, "bjhow" <bjhow@xxxxxxxxxxxxxxxxxxxxxxxxx> said:
I am using Samba to connect trying to connect to the shares and I get either unknown user or bad user and bad password. Some combination of both.Check your Default Domain and Default Domain Controllers policies to see if the "Send unencrypted password to third-party SMB servers" is set to disabled. In addition, check the policies for requiring SMB signing (sorry, can't remember the exact policy name right off the top of my head). These options will cause Mac OS X, which uses Samba, to be unable to access shares on a server running Windows Server 2003. (Note that these settings will affect any Samba client, including Mac OS X, Linux, *BSD, etc.)
"bjhow" wrote:
I have a Windows 2003 server and several MAC OSX machines that vary from OSX 10.3.39 to the new 10.4- Tiger. I can get the Mac's to bind to AD and I can see that is working but cannot get the MAc's to see any of the shares on the Windows 2003 server. I can safely say the Mac's are kerborized and authenticating them but share's are a no go. Any input would be helpful. I do not have an OS X server or Xserve in the picture. Is this needed in order for the Mac's to get to the shares on the Windows server. Need help.
In addition, you may need to make sure that all your share names are less than 12 characters in length and do not have any spaces.
HTH.
-- Scott Lowe
.
- Follow-Ups:
- Re: Mac OSX and AD
- From: Al Mulnick
- Re: Mac OSX and AD
- References:
- RE: Mac OSX and AD
- From: bjhow
- RE: Mac OSX and AD
- Prev by Date: Re: Mac OSX and AD
- Next by Date: Allow logon to terminal server
- Previous by thread: RE: Mac OSX and AD
- Next by thread: Re: Mac OSX and AD
- Index(es):
Relevant Pages
|
Loading