We have a .net web application running on iis 8 using windows authentication.
Everything was working fine until we installed a new version of our application without any changes to the iis settings or in the apps web.config file.
The problem is that ever since when we try to open up the app in a browser and fill out the windows authentication popup with valid user user information, it just wont authenticate and after the third try we get a 401.1 error message. This happens when we try to access the website from any pc even the pc that hosts iis and even when we try to launch the site through iis.
Any ideas on what could cause such a thing?
Related
I have a problem where a site runs okay on hosting server browser but not on my local browser.
It is a site I need to migrate from a windows 2012 server to a new windows 2019 server. I have ensured all IIS components are setup on the new Windows 2019 server. I copied over all files and re-created the site in IIS on new server with, as far as I can see, exactly the same IIS configurations except the Connection string is set to database on new server which was also migrated from old server. I have checked the websites root folder permissions are the same too
The site is built in ASP.NET and both ASP.NET authentication and windows authentication are enabled and anonymous authentication is disabled. The application pools' "identity" is set to "ApplicationPoolIdentity" as was the old site.
To ensure the site worked on new server I created a registry entry for "DisableLoopbackCheck" because the site continually asked for credentials and with registry change my credentials were accepted and site appeared
Lastly, I have asked ICT to ensure the local DNS is set to new site and the old site in old server is stopped. However I still continue to receive "HTTP Error 404. Resource not found" in both Edge and Chrome. I have also viewed the IIS logs for site but tell me very little
Why do I keep getting this 404 error please? I feel it is something simple I am missing
we have a web app hosted on IIS. The spn is set for hostname and works fine when negotiate, ntlm is set and user kerberos authentication. However, if we remove both of them and set negotiate:kerberos, the web app stops working.
On accessing the web page, we get error stating that the site cannot be reached. Even the app pool is also running. Still facing this prolem. Anyone have any idea on how to fix this.
I am building a Office 365 application using ASP.net Visual studio 2015 Enterprise. When I run the application in visual studio using IIS Express it run fine everything works. I am able to authenticate with Azure AD and be routed back to my start page. However, when I deploy it to the IIS SERVER, I am able to authenticate but after authenticating I am routed back to a WHITE screen.
FIREWALL is off
I DO NOT WANT TO HOST IN THE CLOUD!!
I tried using Fiddler but that didn't help me that much. Have anyone ever ran into this problem or similar? Were you able to get around it without hosting in the cloud?
I had this same problem - it worked fine in IIS Express, but in IIS I would get a 400-Bad Request (header too large) error and the page would just spin. To fix this:
Make sure your app login and your reply URL are the same in Azure. Make sure the PostLogoutRedirectUri in your app matches as well.
That URL in step 1 should not be a page! This is what got me I think. I had https://localhost/testdirectory/default.aspx when I should have only had https://localhost/testdirectory/. Once all 3 places matched, things started working in IIS as well.
You probably know this but make sure you're using HTTPS, not HTTP.
can anyone please tell me whether a asp.net mvc 5 web application can be hosted on IIS 7.5?seems has this issue:HTTP Error 503.
and the IIS application pool was stopped when request this web.
it's very strange,when I change website application pool named "A" to another named "B"("B" is an app pool for an asp.net mvc4 web application), then the site run well."A" is the same setting as "B".not really know what had happened.is related section of the web.config ?please help.
I had the same problem and found it was caused by permission problems creating the user profile in C:\Users. I gave ApplicationPoolIdentity full permissions to the C:\Users folder, started the site and everything worked, the profile must have been created properly, and my site worked as it should. I then removed access to C:\Users from ApplicationPoolIdentity.
Site wont start on local using ApplicationPoolIdentity, only when using NetworkService: "HTTP Error 503. The service is unavailable."
I have been using an open source WebDAV framework named "Sphorium" for quite some time to talk to my data repository.. I have been using Cassini web server to host my WebDAV server module and everything was working just fine if I map the server as a web folder in my system. However, i found that Cassini web server does not support "https". So, I started looking out for deploying my WebDAV server application in IIS.. So I built a website in ASP .Net which talks to the Sphorium WebDAV module and authorizes the user. And when I run my website using the VS Debugger, it gets hosted on the ASP .Net development web server, prompts for the credentials and works just fine. However, if I publish my web app and try to host in in IIS, and try to browse, it prompts me for the password for 3 times and finally says "Unauthorized"...
Could someone pls throw some light on how I can use IIS in this case? Do I have to give any permissions?