![]() Setspn.exe -A HTTP/ domain\iisservice Setspn.exe -A HTTP/vieval domain\iisservice I then created an SPN using the hostname of the newly migrated site. I created a new application pool, assigned the web application to that pool and ran the pool as a domain user. I recalled experiencing something similar with another application I'd written and the problem had to do with Kerberos' restrictions on double-hop authentication. I checked the server again - local login works just fine, remote logins do not. I tried a registry change and even rebooted the server to no avail. I checked the web server logs and saw HTTP 401 errors failing with the IIS specific code " 2148074254." Searching the web turned up nothing useful. Our SharePoint sites which Windows Authentication and Kerberos were authenticating properly, so it wasn't the server. Logging in from the server itself, however, worked just fine. Different types of domain accounts, even Domain Admins, were attempted and none were able to login successfully from remote machines. ![]() ![]() I checked the NTFS permissions and double checked the IIS properties for both the Web site and the Virtual directory and everything was setup properly. ![]() We were able to run the application successfully using Anonymous Access but we were unable to authenticate from remote computers when Anonymous Access was disabled. The web application is a custom built ASP/ASPX app that supports Integrated Windows Authentication. Recently, we migrated a web application to a SharePoint server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |