Solved

Previously answered question -  Title: Mac Can no Longer Connect to one of our servers - with new user question

Posted on 2006-10-19
4
250 Views
Last Modified: 2013-11-13
After researching this issue here I found the answer under the following:

   

Home - All Topics - Networking - Mac Net. Q_21862435.html

One of the suggestions was to do the following:

1. Allow the mac to send clear text passwords, explaind here:
http://docs.info.apple.com/article.html?artnum=301580

2. Allow your Windows machine to accept packets that are not digitaly signed
Change this key at the server to 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\requiresecuritysignature

After completing these two steps our Mac user was able to connect without issue, but the next morning they ran into the same error. Upon checking the registry the setting had reverted to 1 instead of 0.

My question is this: what could be causing this to revert and how would I fix this?

Thank you,

John Hoffman
jhoffman@bernan.com
0
Comment
Question by:Kraus-IT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 7

Expert Comment

by:lukeca
ID: 17771395
That setting is controlled by domain security policy, which is what is changing it back.  Everytime the security policy is refreshed it will reset that registry key.

You need to follow these directions to change it permanently:

You need to go administrative tools, Domain Security Policy, Local Policies, Security Options, then for the entry "Microsoft network server: Digitally sign communications (always)" set it to disabled.  

Then you need to go to administrative tools, Domain Controller Security Policy, Local Policies, Security Options, then for the entry "Microsoft network server: Digitally sign communications (always)" set it to disabled.

Then open a command prompt and type "gpupdate /force" to apply the settings.  You may want to reboot to insure the settings have activated.

0
 
LVL 7

Accepted Solution

by:
lukeca earned 125 total points
ID: 17771406
Sorry you didn't say it was a domain controller.  If it is not a domain controller then you will go to administrative tools, Local Security Policy, Local Policies, Security Options, then for the entry "Microsoft network server: Digitally sign communications (always)" set it to disabled.  
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

SUMMARY Enterprise backup in a heterogeneous network is a subject full of complications and restrictions. Issues such as filename & path structure, attributes and extended metadata always tend to complicate the subject to the extent where either …
Worried about if Apple can protect your documents, photos, and everything else that gets stored in iCloud? Read on to find out what Apple really uses to make things secure.
In this video, viewers are given an introduction to using the Windows 10 Snipping Tool, how to quickly locate it when it's needed and also how make it always available with a single click of a mouse button, by pinning it to the Desktop Task Bar. Int…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question