Link to home
Start Free TrialLog in
Avatar of Marisa Stevenson
Marisa StevensonFlag for United States of America

asked on

IIS Windows Authentication doesn't authenticate properly with alias

I have a web app (ESI WebEOC) residing on an IIS server called oeppoim.  It is invoked by typing http://oeppoim/webeocapp.  An alias was created in Active Directory that's called webeoc.  To invoke the app through the alias we type  Both worked fine.  Then we installed a single sign-on add-on that required we disable Anonymous Authentication.  Only Windows Authentication is enabled in IIS.  Http://oeppoim/webeocapp still works great.  However, now when we type, the Windows OS prompts us for credentials.  We have to specify the domain with the userID (US\user1), because otherwise it defaults to the local server, oeppoim.  Once we enter credentials, it goes to the app, as it should.  I can no longer dup the problem on my machine - after invoking oeppoim, entering credentials when prompted (after typing, it seems something is cached, and both work fine.  However, all our other users have the same problem.  Does the alias have to somehow be configured in IIS now that only Win authentication is enabled?  The alias resolves just fine - I can ping it and it returns the server ip address.
Avatar of Chrissalter
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Marisa Stevenson


Does this mean we should be able to access via http://webeoc/webapp (since we aren't entering the fully qualified credentials?  How would I enable users to access it using the webeoc alias?  Thanks - your explanation is a great help