bemara57
asked on
Mac OS X can't see Windows shared files on domain controller, pls help!
I have a Windows 2003 file server (and is a domain controller) that I'm having a hard time getting to from a Mac OS X laptop. I found a solution to loosen my Windows security which did allow the Mac to fiew the shared files, but I can't be lowering my security on my Windows server just so Mac's can view the files. What do I have to do on the Mac for it to work?
To help illustrate what's going on, this is what I did to the Windows server for it to work (which I then reversed it because it made me nervous):
"Windows Server 2003 Authentication
By deafult Windows Server 2003 will try to encrypt everything sent to and from it. With this enabled you will not be able to log in to the share from your Mac.
To fix this there are a couple of options.
Case 1, your server is nothing more than a regular file server. In this case open up regedit (Start > Run > "regedit" {return}), and navigate to HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ LanManServer \ Parameter \ RequireSecuritySignature, and set it's value to "0".
Case 2, your server is also a Domain Controller. In which case you need to open the DC's Security Policy (Administrative Tools > Domain Controller Security Policy). Navigate to Local Policies > Secuiry Options, and disable "Microsoft network server: Digitally sign communications (always)" & "Microsoft network server: Digitally sign communications (if client agrees)". Reboot your sever, and you should be good to go."
To help illustrate what's going on, this is what I did to the Windows server for it to work (which I then reversed it because it made me nervous):
"Windows Server 2003 Authentication
By deafult Windows Server 2003 will try to encrypt everything sent to and from it. With this enabled you will not be able to log in to the share from your Mac.
To fix this there are a couple of options.
Case 1, your server is nothing more than a regular file server. In this case open up regedit (Start > Run > "regedit" {return}), and navigate to HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ LanManServer \ Parameter \ RequireSecuritySignature, and set it's value to "0".
Case 2, your server is also a Domain Controller. In which case you need to open the DC's Security Policy (Administrative Tools > Domain Controller Security Policy). Navigate to Local Policies > Secuiry Options, and disable "Microsoft network server: Digitally sign communications (always)" & "Microsoft network server: Digitally sign communications (if client agrees)". Reboot your sever, and you should be good to go."
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.