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]> 
[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<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.

Reply via email to