The scenario is as follows.
I am working on local XP machine. My resource folders like App_Themes, wanted to place on a servers shared location. I am setting up my asp.net site as default in IIS.
Any thoughts?
Let me know if you have any queries.
You need to enable Identity Impersonation in your web.config and then set up local IIS to use a (domain) account that has rights to the server's share.
Related
Usually, I give access rights to folder based on the app pool identity, in the format of:
IIS AppPool\[app_pool_name]
On this particular new server, when I try to edit the security settings of a folder, and add that particular user entry, I am getting a
"object IIS AppPool\XXXXXX cannot be found"
Any idea why is this? I verified that the application pool is set to ApplicationPoolIdentity.
I am using IIS 7.5 and Windows Server 2008 R2.
By default whenever you try to add a new account on a machine that joined a domain the accounts are only searched on the domain controller for your domain.
This said, if you want to add the IIS AppPool account, you need to click on "Locations..." and scroll up to the top where you'll find the name of your local machine.
Choose this as your location and you'll be able to add your AppPool account.
This sort of question is a first for me, because I'm wondering if something that IS working SHOULD be working.
We have:
Server 1 - Win2K3 file server, which is also our domain server.
Server 2 - Win2008 R2 server where our MVC3 site is deployed, which is also joined to the domain.
I have code on server 2 that uses .NET file system (IO) classes to access server 1 using UNC paths that point to network shared directories, such as \\10.1.1.1\FileDirectory\.
This code works just fine, and we're not using impersonation or delegation. I'm wondering if this SHOULD work, or if it points to bad network permissions setup on server 1. I thought the MVC3 site ran as a local server system account of some sort that wouldn't have any domain access, which is why I'm confused.
Here are 2 screen shots of the permissions for the shared directory on server 1.
Share Perms
NTFS Perms
Thanks for any input. Let me know if I can clarify further or provide more information.
It would appear the the user your site runs as (App Pool Identity?) counts as an 'Authenticated User' from the perspective of the server with the share.
http://www.windowsitpro.com/article/user-management-and-profiles/understanding-the-authenticated-users-group
I need to use nodejs to write file to a password protected shared folder on a remote machine running Windows server 2008 r2, how can I do impersonation things within nodejs like .net app does?
Thx in advance!!!
PS:
Sorry for the unclear description. The folder is set to shared across the internal network on the remote windows server system, the folder is set to "readonly" for the windows account explicitly created by the admin. The nodejs server is on the same internal network and need to access the remote shared folder, thus I think nodejs need to impersonate the windows account on the remote machine to read contents from the shared folder. My question is how to do the sorry for the unclear description. The folder is set to shared across the internal network on the remote windows server system, the folder is set to "readonly" for the windows account explicitly created by the admin. The nodejs server is on the same internal network and need to access the remote shared folder, thus I think nodejs need to impersonate the windows account on the remote machine to read contents from the shared folder. My question is how to do the impersonation stuff for nodejs?
Late to the party - but since there is no accepted answer...
You'll need to launch your node process using the account that has access to the network share. How this is done differs based on your setup. For example, if you're runnning node on a lLinux server trying to connect to the remote Windows server, then it's not going to be straightforward with node.
However; if you're running node on a Windows server, trying to connect to a remote share on another Windows server (which is what it sounds like your situation probably is). Again, you'll have to run your node script as a user with access to the remote share. If you need to do it from code, I'd suggest taking a look at my module node-windows. It doesn't provide remote share access specifically, but it will allow you to run command line code with a different account from within your node script.
I have a service ALOADER which constantly accesses a shared network folder \\10.10.1.100.
Before starting the service ALOADER, i have to make the \\10.10.1.100 visible to the service ALOADER.
The problem is that, the access account of \\10.10.1.100 could not be logged on the service ALOADER, since the \\10.10.1.100 and the server running ALOADER are in different domains.
Instead, I use the "net use \\10.10.1.100" with a local account, and then log on that local account to the service ALOADER.
It works on some servers, but not the others. (the \\10.10.1.100 is accessible on Explorer, but not on the service.)
All the server settings are similar, and the OS is Windows Server 2008 R2.
Looking for your help.
Sincerely,
Jun
In your service you should call NetUseAdd to connect to the network share.
I am familiar with Linux, less with IIS. I have been using Linux/Apache to share user directories for a while set up like this:
/home/user1/public_html
/home/user2/public_html
etc.
...and users can type in a URL to view their public files at:
http://www.mycompany.com/~user1/
http://www.mycompany.com/~user2/
etc.
Combined with SMB sharing and drive mapping on client windows boxes makes it very convenient for corporate users to drop files into a publicly available folder temporarily for someone else to download. They just email the other person the URL.
Searching the internet for "IIS public folders" and variants, yields OWA and Exchange results which I don't want. What is the proper terminology for this setup in Windows/IIS? How do you do it in Windows for all domain users?
In IIS you have to create a virtual directory for each user. IIS does not have an equivalent of the Apache UserDir directive. That's because IIS does not have a concept of users (in the sense of a subscriber to a webserver host).
Of course you could roll your own definition of who users are in IIS. In IIS 7, things like virtual directories are stored in an XML file ApplicationHost.config. You can either create the virtual directories manually via the ISS console, or programmatically via the ApplicationHost.config file.
Reference:
(1) http://www.advancedinstaller.com/user-guide/tutorial-iis.html#virtual-directory
(2) http://httpd.apache.org/docs/2.0/mod/mod_userdir.html#userdir
(3) http://learn.iis.net/page.aspx/124/introduction-to-applicationhostconfig/