|Newer page:||version 7||Last edited on Thursday, August 18, 2005 12:57:28 pm||by JohnMcPherson|
|Older page:||version 4||Last edited on Thursday, October 21, 2004 8:36:26 am||by JohnMcPherson||Revert|
@@ -1,5 +1,5 @@
-Some notes on using Macs are clients to Windows SMB or Samba fileservers. Particularly notes on the Apple Samba implementation bundled with
Mac OS X
+Some notes on using Macs are clients to Windows SMB or Samba fileservers. Particularly notes on the Apple Samba implementation bundled with .
!!Windows Server 2003
You may find that you are completely unable to mount SMB volumes shared by Windows Server 2003 by using the "Go->Connect To Server" option in Mac OS X. This is a result of new encryption introduced with Windows Server 2003. Symptoms of this problem are errors about invalid usernames or passwords or errors like this logged in the console:
@@ -12,4 +12,10 @@
You may still be able to browse the file shares fine with smbclient, it is the mount_smbfs tool that fails (which is used by the "Connect To Server" menu option).
The easiest solution to this problem is to disable the default server setting of always requiring "digitally signed communication". To do this, log in to the domain controller and open the DC policy editor. Look for "Security Settings -> Local Policies -> Security Options" and change "Microsoft network server: Digitally sign communications (always)" from "Enabled" to "Disabled". Leave everything else. This means that the server will digitally sign communications if the client is capable, but won't reject a connection if your client is not.