Looks like http://beergivr.com/ would work. ;)
Or since I’m local there are other options. ☺ DAMIEN SOLODOW Systems Engineer 317.447.6033 (office) 317.447.6014 (fax) HARRISON COLLEGE From: [email protected] [mailto:[email protected]] On Behalf Of Richard Stovall Sent: Thursday, July 24, 2014 10:57 AM To: [email protected] Subject: Re: [NTSysADM] RE: 2012 shares? Dude! On Thu, Jul 24, 2014 at 10:55 AM, David McSpadden <[email protected]<mailto:[email protected]>> wrote: Go right ahead and point. I said I would abide. ☺ From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Damien Solodow Sent: Thursday, July 24, 2014 10:51 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: 2012 shares? Usually it’s my last name that gets mangled. ☺ Maybe I should send you to one of those “send a brew” sites so you can buy me a beer. ;) DAMIEN SOLODOW Systems Engineer 317.447.6033<tel:317.447.6033> (office) 317.447.6014<tel:317.447.6014> (fax) HARRISON COLLEGE From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Thursday, July 24, 2014 10:31 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: 2012 shares? Damien, I apologize for the butchering of your first name. I will abide by whatever punishment you detail. I need more sleep and/or coffee I believe. Thanks for the help. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Thursday, July 24, 2014 10:26 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: 2012 shares? Add Daniel’s method works folks. No reboot required. Thanks LIST This has been a headache. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Damien Solodow Sent: Thursday, July 24, 2014 10:19 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: 2012 shares? You’re welcome. ☺ It was something I was really happy to discover as the DisableStrictNameChecking was a headache. This trick is also part of the “supported” method to safely rename a domain controller, which is how I learned it in the first place. DAMIEN SOLODOW Systems Engineer 317.447.6033<tel:317.447.6033> (office) 317.447.6014<tel:317.447.6014> (fax) HARRISON COLLEGE From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, July 24, 2014 10:15 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: 2012 shares? Thanks for teaching an old dog a new trick! From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Thursday, July 24, 2014 10:08 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: 2012 shares? Genius From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Damien Solodow Sent: Thursday, July 24, 2014 10:08 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: 2012 shares? Yes it does. DAMIEN SOLODOW Systems Engineer 317.447.6033<tel:317.447.6033> (office) 317.447.6014<tel:317.447.6014> (fax) HARRISON COLLEGE From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, July 24, 2014 10:02 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: 2012 shares? That’s very interesting. Does it add an SPN? (I don’t have time to test right now, but I can later. I’m happy to learn something new!) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Damien Solodow Sent: Thursday, July 24, 2014 9:49 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: 2012 shares? There is another (easier) solution that doesn’t require a reboot. ☺ 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<tel:317.447.6033> (office) 317.447.6014<tel:317.447.6014> (fax) HARRISON COLLEGE From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Thursday, July 24, 2014 9:43 AM To: '[email protected]<mailto:[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-name-checking-and-authentication-loopback-enterprise-vault-server From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, July 24, 2014 9:39 AM To: [email protected]<mailto:[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]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Thursday, July 24, 2014 9:34 AM To: '[email protected]<mailto:[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]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, July 24, 2014 9:27 AM To: [email protected]<mailto:[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]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Thursday, July 24, 2014 9:20 AM To: '[email protected]<mailto:[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<file:///\\Computername\Files> I have a DNS A record for this as appserver and would like to access the share as \\AppServer\Files<file:///\\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. 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.
