Differences between version 6 and previous revision of MacSambaNotes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 6 | Last edited on Saturday, April 9, 2005 12:58:21 pm | by MikeKelly | Revert |
Older page: | version 5 | Last edited on Saturday, April 9, 2005 12:56:40 pm | by MikeKelly | Revert |
@@ -12,10 +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.
-
-Solving this problem is easy. Ping "foo" from an affected Mac and find out what it's IP is, then track it down and change it's name in System Prefferences->Sharing click "Edit" and change the name.
!!DNS vs. NetInfo / Rendezvous
If you find that you are not getting prompted for a password when connecting to a samba share from a Mac, this may be due to a name resolution issue. Macs will prefer their own NetInfo and Rendezvous to DNS. This means that if you have a Mac on your network which is configured to call itself "foo", then Macs will gravitate towards this server instead of going to the "real" (according to DNS) server named "foo". Meanwhile, you will be very confused about why only the Macs on the network have this problem.
+
+Solving this problem is easy. Ping "foo" from an affected Mac and find out what it's IP is, then track it down and change it's name in System Prefferences->Sharing click "Edit" and change the name.