First off, I have read through this post and a whole slew of non-SF posts which seem to address the same or a similar problem, however I was still unable to fix my problem.
I've got three machines in this situation:
- a domain-joined server that runs Server 2008 R2 Enterprise ("share server")
- a domain-unjoined test server running Server 2003 R2 SP2 ("test server")
- a domain-joined workstation running XP Pro SP3 ("workstation")
The share server is exposing a share on the network that the test server must access--it's a Source/Symbol Server share for our debugging purposes. I believe visual studio simply accesses the the share with its own credentials in this case, meaning that the share must be accessible anonymously since the test server isn't joined to the domain and there's no opportunity to supply domain authentication.
I've attempted a lot of things to avoid the authentication window when accessing the share:
- I've enabled the Guest account on the share server and given Guest full sharing/NTFS permissions for the share.
- I've given ANONYMOUS LOGON full sharing/NTFS permissions for the share.
- I've added my share to “Network Access: Shares that can be accessed anonymously” in LSP.
- I've disabled “Network access: Restrict anonymous access to Named Pipes and Shares” in LSP.
- I've enabled “Network access: Let Everyone permissions apply to anonymous users” in LSP.
- Added ANONYMOUS LOGON to “Access this computer from the network” in LSP.
- Added the Guest account to “Access this computer from the network” in LSP.
- Attempted to provision the share using the Share and Storage Management MMC snap-in.
Unfortunately when I attempt to access the share from the test server, I still see the prompt and I'm forced to enter "Guest" manually.
I also tried this workflow using the local administrator account on a workstation, and the same thing happens both with and without XP Simple File Sharing enabled.
Any idea why I'm getting these results, or what I should have done differently?
You did everything correct with the exception of the local account accessing the share cannot be on both systems. Essentially, if the non-domain account running your application is called "administrator" then you must not have a local account on the domain server named "administrator".
If the username you are using the login with exists on the server but has a different password it will always prompt for the password no matter what guest and anonymous settings you have created.
Try logging in with a username that does not exist anywhere on the server or it's domain.
The other option is the make the password on the stand alone server exactly the same as it is on the identical named user on the domain.
How about mapping a network drive, and utilizing a persistent connection syntax would be something like this.
net use H: \path\to\server\ PASSWORD_CLEAR_TXT /user:domain\user /persistent:yes
if at any time you want to delete it net use h: /delete
Possibly temp workaround . You can create local user account(an give share\ntfs permissions) on the "share server" with same name & password as account used on your "test server" for running app accessing shares.
I can't see that you've added EVERYONE to the network share/security permissions, Guest (once enabled) should be included in this group. As described here.
Also some good answers here, relating to a similar questions (2003).
Have you run through this article (below) in detail? It's not so much a list of steps, as a detailed top-bottom for how this functionality happens.
http://www.minasi.com/newsletters/nws0312.htm
Have you tried explicitly adding the computer account, i.e. computername$ to have permissions on the share and via NTFS? Obviously, this wouldn't work with non-domain joined machines.
It is always going to prompt until you do one of two things. Both acomplish the same task of caching the credentials (which ironically in this case do not matter but still need to be present).
One is to map the drive and make the mapping persistent. The other is to open up credential manager directly and add a login (any login) for the server you are connecting to. Credential Manager is accessed from the users control panel item or directly at "Control Panel\All Control Panel Items\Credential Manager".