Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Set Windows Server 2003 to allow Mac connections' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Set Windows Server 2003 to allow Mac connections
Authored by: jsazout on Mar 09, '05 06:56:26AM

I can vouch for this hint. I was faced with exactly the situation described during a client visit last October. Here are my notes from that visit:

Macs were unable to mount volumes on the Windows 2003 server. Message was bad user name or password, console message: no credentials cache found krb5_cc_get_principal. Needed to disable 2 security policies in win2003 server.

Solution came from:

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.

I do not know enough about Win2003 server to intelligently discuss the security implications of the procedure, except to say that my client has not experienced any issues since I made the change...


[ Reply to This | # ]
Out of disk space message
Authored by: apta on Dec 27, '05 07:32:16PM

Well, followed the instructions and managed to connect from a Tiger 10.4.3 G5 to Win 2003 server via SMB. But everytime I try to copy a file to the server from the Mac I get an "out of disk space" message even though there's space available. Also, a Get Info for the shares shows them to be precisely 1GB even though they're bigger than that.

Is this a bug or do I need to set something else?

[ Reply to This | # ]