So we have two load balanced servers in the DMZ (Demilitarized Zone), these servers are not connected to our company domain, so there are no domain users or domain drives. Normally we would locate the files for a website on each server, there was a requirement for this particular website to locate the files on a shared location. What we did was to have the website files on one server in the DMZ and to configure the sites in IIS (Internet Information Services) on both servers to point to the single shared location.
This is how we configured the sites, on the main server.
- Create a local user
- Navigate to Control Panel > Administrative Tools > Computer Management > Local Users and Groups.
- Right-click Users and select New User from the context menu.
- Enter values for User name, Full name, Description, Password and Confirm password.
- Ensure User must change password at next logon is unticked.
- Ensure User cannot change password is ticked.
- Ensure Password never expires is ticked.
- Ensure Account is disabled is unticked.
- Create a local folder e.g. C:\Websites\MySite.
- Copy the website files to this new folder.
- Share the website folder
- On the properties of the newly created folder (right-click > properties)
- Select the Sharing tab.
- In the File Sharing dialog add the local user previously created and set appropriate permissions e.g. Read/Write.
- Click the Share button close the dialog.
- Click the Close button to close the Properties dialog.
- Set up IIS. After opening IIS
- Create a new application pool. Set the appropriate .Net version and application pool identity. On my setup this was .Net4.0 and AppPoolIdentity respectively.
- Create a new site. Set the Physical Location to be the shared folder e.g. \\Server1\MySite. Also set the application pool the one just created.
- Set bindings domain name bindings as required.
- In IIS click the new site to display the Features View.
- In the Features View, double click the Authentication icon. Right-click Anonymous Authentication and select Edit from the context menu.
- In the Edit Anonymous Authentication Credentials dialog select the Application Pool identity radio button and click the OK button to close the dialog.
The first server is now configured and the website should run at this point. Setting up the second server requires similar actions. Carry out the following on the second server in the DMZ.
- Create a local user by completing point 1 above. Ensure the same credentials and settings are used.
- Set up IIS. After opening IIS
- Create a new application pool. Set the appropriate .Net version, e.g. .Net4.0. Set the application identity as the local user created above.
- Create a new site. Set the Physical Location to be the shared folder from first server e.g. \\Server1\MySite. Also set the application pool the one just created.
- Set bindings domain name bindings as required.
That should be about it for the second server. Both the servers should serve up the sites.
Disclaimer: By posting this information I am not suggesting this as the ‘right way’ or ‘best practise’ it was something we did temporarily to quickly get a site up and running without opening up file wall ports in to the company domain servers.

You must be logged in to post a comment.