Active Directory Shares not working

  • Thread starter Thread starter michael.houser.jr
  • Start date Start date
M

michael.houser.jr

I am trying to connect to a share on my AD machine. I am able to "Bind"
to the AD using 10.3.9 and Apple's AD-Plugin. Everytime I try to
connect to the AD share I get a "Could not connect to the share because
the name or password is not correct". This is the same machine that I
authenticated to in order to login. I am using smb://ip_address/share
Any ideas?

Thanks,

Michael Houser
 
I am trying to connect to a share on my AD machine. I am able to "Bind"
to the AD using 10.3.9 and Apple's AD-Plugin. Everytime I try to
connect to the AD share I get a "Could not connect to the share because
the name or password is not correct". This is the same machine that I
authenticated to in order to login. I am using smb://ip_address/share
Any ideas?
Click to expand...

Hi Michael!

This may not be related to Active Directory at all. Is the server you're
trying to connect to running a default installation of Windows Server
2003? If so, it has enabled by default a policy that requires a more
secure SMB connection (Microsoft Client: Digitally sign communications
Always). Mac OS X's implementation of SMB doesn't support this more
secure connection.

Have a look at this page on Microsoft's website
<http://support.microsoft.com/default.aspx?scid=kb;en-us;887429>. While
it doesn't specifically mention Mac OS X, it does the policy and SMB
clients and explains where to find the policy to disable it.

Alternatively, if you're uncomfortable with lower your server's
security, you can look into using a different SMB client such as Dave or
ADmitMac from <http://www.thursby.com>. You can download 30-day trials
to test for yourself.

Hope this helps! bill
 
Bill,

As a workaround I am able to connect to the shares without being in the
Active directory using AFP, Services For Macintosh and using
Microsoft's UAM. I am not able to connect to the shares using SMB I
still get a "bad user name and password". Strange. Any Ideas?

Thanks,

Michael
 
Bill,

The Windows XP 2000 users use the higest security policy so disabling
that is not an option for me. I think the SFM seems to be the trick for
now anyway.
 
Hi Michael!

If your servers have the hisecurity policy enabled, which is unusual,
then you definitely won't be able to connect using Mac OS X's built-in
SMB client. The hisecurity policy greatly limits what a server can do
and who can interact with it.

If you're satisfied with the limitations when using File Services for
Macintosh then it is your only solution outside of third party software.

bill
 
Back
Top