>>One of our directory on the IIS server need to have basic authentication. When a user access the directory, he is prompted to enter a username. In our case, the usernames are coming from a domain which is not on the NT server. Let assume the domain name is TEST. IIS server is configured to map to this domain for the basic authentication. This domain is also the default domain for the NT server. However, when someone access the directory, we can see in the basic authentication window that the name of the resource is the NT server itself and not the domain TEST.
>>
>>Is this a bug in IIS not to be able to map to other domain even if this is an option in its configuration?
>
>Sorry, I don't have the answer for you, but I do have an observation...
>
>Isn't it odd that most people (programmers, some I know anyways) always think that if something SHOULD work and doesn't, there MUST be a bug, but not in their code/setup, but rather in the development tool/software they're using! I don't know if you've noticed, but many questions/comments start out along the lines (or quickly get to this question and/or point) "Is it a bug", "I think I found a bug", "... I don't know why... everything's done right/coded properly, must be a bug in
", that is, until they notice a line that's commented out that wasn't supposed to be... "Ooops, must've hit the key by accident!"
It's not a bug but it is close.
In Internet Service Manager, when we apply basic authentication to a directory and want the users to come from a domain, where the list of users is not on the current NT server, the domain name entered is case sensitive. We entered it manually and it was not working. We finally entered it from the list and we saw that the first letter is uppercase. There is worked.
But, one thing for sure, we did entered the domain in lowercase when it was created. However, to have it work, we had to select from the list, where the list is shown with the uppercase as the first letter.
Weird.
