steve_o76
asked on
IIS 6.0 prompting for Windows Authentication when accessing CITRIX Web Interface 5.1
Hello all,
I have a Windows 2003 Server /SP2 with CITRIX Web Interface 5.1 installed (I have PS on another server as well). The server is part of a domain. When I try to access the site, I keep getting prompted for a username and password by Windows Authentication. I am trying to allow any user access to the web interface page and then they enter credentials to access published applications.
If I cancel the WinAuth, I get 401.3 ACL error. The issue is that I cannot have my users authenticating 3 times to get published applications.
For Troubleshooting, I have done the following:
1. Added IUSR (NTFS permissions) to C:\Inetpub\wwwroot - Full control
2. Removed Windows Authentication from the entire website in IIS Manager
--*Doing this gets rid of the WinAuth, but it goes straight to the 401.3 error
I have run the IIS troubleshooting application from Microsoft, no help
I have changed permissions more times than I can count.
I have changed my browser settings on my laptop because I read that it can cause problems like this by the way it is configured.
On the flip side, if I enter an ID and PW at the WinAuth, I immediately get to the Web Interface Logon page. I enter my credentials there as well and I get to my published apps. I click my published app and I have to authenticate again, and it comes up.
This is the behavior I want except for the WinAuth when you first hit the site. I have a certificate for the site as well. If you need any more information about the setup, I will be happy to share what I can.
I am at the end of my rope.
I have a Windows 2003 Server /SP2 with CITRIX Web Interface 5.1 installed (I have PS on another server as well). The server is part of a domain. When I try to access the site, I keep getting prompted for a username and password by Windows Authentication. I am trying to allow any user access to the web interface page and then they enter credentials to access published applications.
If I cancel the WinAuth, I get 401.3 ACL error. The issue is that I cannot have my users authenticating 3 times to get published applications.
For Troubleshooting, I have done the following:
1. Added IUSR (NTFS permissions) to C:\Inetpub\wwwroot - Full control
2. Removed Windows Authentication from the entire website in IIS Manager
--*Doing this gets rid of the WinAuth, but it goes straight to the 401.3 error
I have run the IIS troubleshooting application from Microsoft, no help
I have changed permissions more times than I can count.
I have changed my browser settings on my laptop because I read that it can cause problems like this by the way it is configured.
On the flip side, if I enter an ID and PW at the WinAuth, I immediately get to the Web Interface Logon page. I enter my credentials there as well and I get to my published apps. I click my published app and I have to authenticate again, and it comes up.
This is the behavior I want except for the WinAuth when you first hit the site. I have a certificate for the site as well. If you need any more information about the setup, I will be happy to share what I can.
I am at the end of my rope.
ASKER
Sorry,,,
CTX124022-1.gif
CTX124022-1.gif
I would add wi.domain.com to your local intranet zone in IE by going to Tools-->Internet Options-->Security. Click on Local Intranet-->Sites-->Advance
After that it should allow you to authenticate to the site without a prompt when using Integrated Authentication. It sounds like your permissions are fine since you said it allows you in when you manually type in the username and password.
After that it should allow you to authenticate to the site without a prompt when using Integrated Authentication. It sounds like your permissions are fine since you said it allows you in when you manually type in the username and password.
ASKER
Thanks for the suggestion Tray896, unfortunately that did not solve the issue. I had tried that solution before and it didn't prove to be successful.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Steve o --- Can you give a little more explanation to what user rights issue was causing the problem and what you did to fix this? I am having EXACTLY the same problem. It just popped up after stopping and starting IIS one day. This is killing me. Any help would be greatly appreciated.
ASKER