Excellent. This is very cool. Kurt
On Thu, Jul 24, 2014 at 10:30 AM, Damien Solodow <[email protected]> wrote: > You should delete the existing A record because when you add the name to the > server using netdom, the server will try to create the A record per normal > DNS registration. If the record already exists, it will most likely not be > able to over-write that existing record and give an error. > > Yes, there will be two A records for the same IP. > > DAMIEN SOLODOW > Systems Engineer > 317.447.6033 (office) > 317.447.6014 (fax) > HARRISON COLLEGE > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Thursday, July 24, 2014 1:26 PM > To: [email protected] > Subject: Re: [NTSysADM] RE: 2012 shares? > > Just to be explicit about all this: > > o- Why delete the A record for the machine getting the alias? > o- After this procedure, will there be two A records pointing to the same IP > address? > > Kurt > > On Thu, Jul 24, 2014 at 6:48 AM, Damien Solodow <[email protected]> > wrote: >> There is another (easier) solution that doesn’t require a reboot. J >> >> Skip the DisableNameChecking. >> >> Delete the existing A record for AppServer from the primary DNS server >> configured on ComputerName. >> >> On ComputerName, open an elevated command prompt and run: netdom >> compuername ComputerName /add:addserver.full.dnsname >> >> >> >> Done. >> >> >> >> DAMIEN SOLODOW >> >> Systems Engineer >> >> 317.447.6033 (office) >> >> 317.447.6014 (fax) >> >> HARRISON COLLEGE >> >> >> >> From: [email protected] >> [mailto:[email protected]] >> On Behalf Of David McSpadden >> Sent: Thursday, July 24, 2014 9:43 AM >> >> To: '[email protected]' >> Subject: [NTSysADM] RE: 2012 shares? >> >> >> >> Ok. >> >> Fair enough. I would not have thought to google Disable Strick Name >> Checking. >> >> But doing so brought this one up. >> >> I have added the second reg as well. >> >> About to reboot. >> >> Let everyone know but I am sure this will fix it. >> >> Thanks. >> >> >> >> http://www.symantec.com/connect/blogs/why-you-might-disable-strict-nam >> e-checking-and-authentication-loopback-enterprise-vault-server >> >> >> >> >> >> >> >> From: [email protected] >> [mailto:[email protected]] >> On Behalf Of Michael B. Smith >> Sent: Thursday, July 24, 2014 9:39 AM >> To: [email protected] >> Subject: [NTSysADM] RE: 2012 shares? >> >> >> >> It’s not just a SQL trick. It’s a LanMan trick. >> >> >> >> That just happened to be the first complete set of directions that >> popped up when I googled it. >> >> >> >> From: [email protected] >> [mailto:[email protected]] >> On Behalf Of David McSpadden >> Sent: Thursday, July 24, 2014 9:34 AM >> To: '[email protected]' >> Subject: [NTSysADM] RE: 2012 shares? >> >> >> >> Ok MS, why does a SQL trick apply to this situation? >> >> Other than it isn’t really a SQL trick is it. >> >> It is a LanManServer trick that they have mangled with a SQL issue as well? >> >> Am I close to understanding . >> >> I am trying this now. >> >> And thank you >> >> >> >> From: [email protected] >> [mailto:[email protected]] >> On Behalf Of Michael B. Smith >> Sent: Thursday, July 24, 2014 9:27 AM >> To: [email protected] >> Subject: [NTSysADM] RE: 2012 shares? >> >> >> >> http://technet.microsoft.com/en-us/library/ff660057(v=ws.10).aspx >> >> >> >> >> >> From: [email protected] >> [mailto:[email protected]] >> On Behalf Of David McSpadden >> Sent: Thursday, July 24, 2014 9:20 AM >> To: '[email protected]' >> Subject: [NTSysADM] 2012 shares? >> >> >> >> I have member server standard 2012. >> >> I have a file share of Files and it shows up as \\Computername\Files >> >> I have a DNS A record for this as appserver and would like to access >> the share as \\AppServer\Files but get access denied? >> >> What tree should I be barking up? >> >> AppServerUser has full on the folder permissions and share permission >> and I have turned UAC off for now trying to trouble shoot? >> >> Why can I not access the A record \ share name??? >> >> Thanks >> >> 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. > >
