Sounds like functionally you were trying to run with 2 computers having the
same name. I've never found a way to do that.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of David McSpadden
Sent: Wednesday, October 11, 2017 8:02 AM
To: ntsysadm@lists.myitforum.com
Subject: RE: [NTSysADM] RE: Can not access cname
Reboot fixed.
Also, in hindsight.
Old server owns cname and ip.
new server is built and upgraded application is installed and ready to go.
Changed cname and change ip on new server to match old server.
DID NOT decommission old server just gave dhcp address.
All of the googlefu in the world assume old server is dead and off domain.
I think.
Because using the link below did not help even after reboot until old server
was removed from domain. (Changed the name as well.)
Thank you all for your insight.
And I will give better information before posting in the future.
Sugar was low and I was under the gun because we were rolling in production.
List is still the best thing I have joined in 21 years.
From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith
Sent: Tuesday, October 10, 2017 5:58 PM
To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com>
Subject: [EXTERNAL]RE: [NTSysADM] RE: Can not access cname
Better information, provides better answers. :)
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: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of David McSpadden
Sent: Tuesday, October 10, 2017 5:27 PM
To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com>
Subject: Re: [NTSysADM] RE: Can not access cname
Not
Root
E:\files
Then cannot access\\cname\files
Can access \\ip\files<file://ip/files> and
\\computername\files<file://computername/files>
Sent from my iPhone
On Oct 10, 2017, at 5:21 PM, Michael B. Smith
<mich...@smithcons.com<mailto: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>
[mailto:listsad...@lists.myitforum.com] On Behalf Of David McSpadden
Sent: Tuesday, October 10, 2017 4:58 PM
To: ntsysadm@lists.myitforum.com<mailto: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.
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.
