sierrapacific
IS-IT--Management
My 10.4.7 G5 Macs can't search my new Windows 2003 server. Any thoughts? Appletalk and TCP/IP is installed on the server. I can see all the shares, but I can't search them.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Searching a Windows 2003 Server Share
- Thread starter sierrapacific
- Start date
- Status
Had a similar problem where I could log onto the server but see only empty folders, the answer was #2 below, from the site
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.
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.
- Thread starter
- #4
sierrapacific
IS-IT--Management
I actually found the answer to my original problem in one of the MS KB articles that as posted on this site before. It all comes down to applying a hotfix from MS, fixed my problem.
- Thread starter
- #6
sierrapacific
IS-IT--Management
dodge20, yes, you were right on with the hotfix. Thanks.
- Status
Similar threads
- Locked
- Question