<authentication mode="Windows"></authentication >
In IIS : anonymous – disabled ; windows – enabled !
Internet Information Services 7.5
HTTP Error 401.1 – Unauthorized
You do not have permission to view this directory or page using the credentials that you supplied.
this one worked for me:
Method 1: Specify host names (Preferred method if NTLM authentication is desired)
To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:
- Set the
registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
281308 Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
- Click Start, click Run, type regedit, and then click OK.
- In Registry Editor, locate and then click the following registry key:
- Right-click MSV1_0, point to New, and then click Multi-String Value.
- Type BackConnectionHostNames, and then press ENTER.
- Right-click BackConnectionHostNames, and then click Modify.
- In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
- Quit Registry Editor, and then restart the IISAdmin service.
Create a new WebSite at IIS 7 (no , virtual directory is not good enough)
- Define site name
- Connect to physical path
- Define redirect site name – Host Name
The Host Name is the new url address for your site . It”ll work through port 80 , as defined at the picture.
You can enter another port , if you wish.
Port 80 is a default port for http protocol unsecured traffic . (Second default port is 8080)
Port 443 is a default port for https ssl enabled , secured with certificates traffic .
New Website called WebDDD
Edit Site(right pane) –> Bindings… –> YourNewRedirectName “DDD” on port 80
Add –> You can add more redirects with different names and ports.
Now we should see the IP of our server
Start –> run –> cmd –> ping YourServerName –> get the YourServerNameIP
Goto –> Your local terminal –> C:\Windows\System32\drivers\etc –> open hosts with Notepad –>
add a line
Now you’ve connected the Local Terminal with the Server Binding .
That’s it . On your local PC you can access the web site through http://DDD
and you’ll go to http://WebDDD .
If you get some security message from IIS – > check in the File System –> Your WebSite folder –> properties –> security –> Domain Users
If you are working with Server you should define the DNS in your Active Directory also..
So the scenario today , is upgraded to IIS 7 and using now the Application Pool Identity as defined in the best practice of Microsoft .
In the IIS 7 , standing on MY APPLICATION POOL
press Advanced Settings :
We’ve deployed the application and it tries to access some shared folder on some other server .
Once we were Network Service , IIS IUSR and so on , but not any more..
So who are we now ? How can we access the folder ?
Who is that mysterious ApplicationPoolIdentity guy ?
So the answer is quite simple :
Go to the Shared Folder –> right click –> properties -> security –>edit –> add (so far as usual ) -> choose object types –> check on computers –> now enter the computer name where your application is working from , where you published your application.
That’s it – now you have the access to the Shared Folder!