“Also, removed old server that had owned that CNAME prior from the domain.”
Bingo! That will cause a failure every single time. That are Kerberos
problems when using an alias, but it should not have caused the problem you
experienced. It was only because of the old computer object.

On Tue, Oct 10, 2017 at 9:28 PM, David McSpadden <[email protected]> wrote:

> Still a failure.
>
> I am stuck waiting on a reboot.
>
> Will see then if the NETDOM worked.
>
> Also, removed old server that had owned that CNAME prior from the domain.
>
>
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Michael B. Smith
> *Sent:* Tuesday, October 10, 2017 5:58 PM
> *To:* [email protected]
> *Subject:* [EXTERNAL]RE: [NTSysADM] RE: Can not access cname
>
>
>
> Better information, provides better answers. J
>
>
>
> https://support.microsoft.com/en-us/help/3181029/smb-file-
> server-share-access-is-unsuccessful-through-dns-cname-alias
>
>
>
> CNAMEs break Kerberos unless you add the appropriate SPNs. See “netdom
> computername /add:cname.fqdn”.
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com <[email protected]>] *On Behalf Of *David
> McSpadden
> *Sent:* Tuesday, October 10, 2017 5:27 PM
> *To:* [email protected]
> *Subject:* Re: [NTSysADM] RE: Can not access cname
>
>
>
> 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 <[email protected]>
> 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:* [email protected] [mailto:listsadmin@lists.
> myitforum.com <[email protected]>] *On Behalf Of *David
> McSpadden
> *Sent:* Tuesday, October 10, 2017 4:58 PM
> *To:* [email protected]
> *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.
>
> 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.
>



-- 

Charlie Sullivan

Sr. Windows Systems Administrator

Boston College

197 Foster St. Room 367

Brighton, MA 02135

617-552-4318

Reply via email to