Is it still a requirement to modify the DisableStrictNameChecking value under lanman server in the registry?
- Sean > On Oct 10, 2017, at 1:26 PM, David McSpadden <dav...@imcu.com> wrote: > > Not > Root > E:\files > Then cannot access\\cname\files > Can access \\ip\files and \\computername\files > > > > Sent from my iPhone > > On Oct 10, 2017, at 5:21 PM, Michael B. Smith <mich...@smithcons.com> wrote: > >> Notice: This email is from an outside source. Please do not open any >> attachments, click on any hyperlinks, or respond without first confirming >> the authenticity of the email. >> >> >> >> >> Try harder. >> >> Did you create the share at the root of the volume? That’s the #1 problem I >> see these days. >> >> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] >> On Behalf Of David McSpadden >> Sent: Tuesday, October 10, 2017 4:58 PM >> To: ntsysadm@lists.myitforum.com >> Subject: [NTSysADM] Can not access cname >> >> New 2016 standard server >> Want to access cname/share >> Failing >> >> Sent from my iPhone >> This e-mail and any files transmitted with it are property of Indiana >> Members Credit Union, are confidential, and are intended solely for the use >> of the individual or entity to whom this e-mail is addressed. If you are not >> one of the named recipient(s) or otherwise have reason to believe that you >> have received this message in error, please notify the sender and delete >> this message immediately from your computer. Any other use, retention, >> dissemination, forwarding, printing, or copying of this email is strictly >> prohibited. >> >> >> Please consider the environment before printing this email. >> > > This e-mail and any files transmitted with it are property of Indiana Members > Credit Union, are confidential, and are intended solely for the use of the > individual or entity to whom this e-mail is addressed. If you are not one of > the named recipient(s) or otherwise have reason to believe that you have > received this message in error, please notify the sender and delete this > message immediately from your computer. Any other use, retention, > dissemination, forwarding, printing, or copying of this email is strictly > prohibited. > > > Please consider the environment before printing this email.
