clynch302
asked on
Internal VB .NET web application asking for network credentials every time.
Hello all -
I have an internal web application that runs VB .NET in a Windows Active Directory environment. I have no knowledge of .NET just to be upfront. When a user on the network access the web address it always ask for their credentials. Where do I look to remedy that? Users are using IE 9 or above. The web app runs in IIS 7 on a Win 2K8 R2 box.
Thanks in advance.
I have an internal web application that runs VB .NET in a Windows Active Directory environment. I have no knowledge of .NET just to be upfront. When a user on the network access the web address it always ask for their credentials. Where do I look to remedy that? Users are using IE 9 or above. The web app runs in IIS 7 on a Win 2K8 R2 box.
Thanks in advance.
It may be hosted internally, but is the website name the same as the active directory domain? What are the authentication settings for the site in IIS?
ASKER
We have the the website name listed in DNS name.company.corp as well as name.comapny.,com
Does the application use a SQL Server backend?
Is the SQL Server on a different server to the IIS?
If all the above is true then you are probably running into a Kerberos double hop problem, this is where the client credentials are allowed (by default) to hop once i.e. between the DC that authenticates the logon to the webserver but then cannot use the credentials to hop to the SQL Server.
Understanding kerberos double hop problem
Is the SQL Server on a different server to the IIS?
If all the above is true then you are probably running into a Kerberos double hop problem, this is where the client credentials are allowed (by default) to hop once i.e. between the DC that authenticates the logon to the webserver but then cannot use the credentials to hop to the SQL Server.
Understanding kerberos double hop problem
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks. It was Domain User permission issue on the web folders.