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: ozzyrules on Mar 09, '05 07:03:51PM
I too had the same problem and had some major battles with the PC techs who were trying to convince my client that it was the fault of the Mac guy (me) that the Mac's couldn't connect to the Windows 2003 server. With a little research I found this on the Microsoft site:
Windows Server 2003 uses secure encryption which the version of samba in Panther (Mac Operating System) doesn't support. The server's authentication needs to be changed to allow unsigned authentication, per the following: On the server, go to "Start" ->"Administrative Tools" -> "Domain Controller Policy" (not Domain Policy) and look for "Security Settings" -> "Local Policies" -> "Security Options" -> "Microsoft network server: Digitally sign communications (always)". It should show "Enabled" by default. Double-click on it and set to "Disabled". Then close the app and reboot the server.
It worked like a charm and shut the PC techs up real quick. It really embarrassed them.

[ Reply to This | # ]
Set Windows Server 2003 to allow Mac connections
Authored by: wraevn on May 28, '05 02:35:33PM

I'm having this same problem, only w/ a Win XP machine - and the Administrative Tools for XP don't contain the tool used in the Win2K3 fix . . . anybody have a fix for me?



[ Reply to This | # ]
Set Windows Server 2003 to allow Mac connections
Authored by: clong@mac.com on Jun 01, '05 12:03:49PM

Look for Local Security Policy instead of Domain Controller Security Policy. This is where I found the same settings for my "workgroup server" since my school isn't running active directory. Making the same changes works like a charm.



[ Reply to This | # ]
Set Windows Server 2003 to allow Mac connections
Authored by: pfunk on Jun 07, '05 03:43:41PM
I too had the same problem and had some major battles with the PC techs who were trying to convince my client that it was the fault of the Mac guy (me) that the Mac's couldn't connect to the Windows 2003 server. With a little research I found this on the Microsoft site:
Windows Server 2003 uses secure encryption which the version of samba in Panther (Mac Operating System) doesn't support. The server's authentication needs to be changed to allow unsigned authentication, per the following: On the server, go to "Start" ->"Administrative Tools" -> "Domain Controller Policy" (not Domain Policy) and look for "Security Settings" -> "Local Policies" -> "Security Options" -> "Microsoft network server: Digitally sign communications (always)". It should show "Enabled" by default. Double-click on it and set to "Disabled". Then close the app and reboot the server.
It worked like a charm and shut the PC techs up real quick. It really embarrassed them.
Huh? Why would the PC techs be embarrassed for using a more secure method of logging in? By making the above changes to your 2000/2003 server, you're effectively sending all your usernames and passwords in plaintext across the network. Hardly what any good system administrator would want in the year 2005. You're asking the Windows server to lower it's security for ALL clients, in order for your Macs to connect.

[ Reply to This | # ]