Hi Vicky,
the mapping for the .htr extension is correct=20
(C:\WINNT\System32\inetsrv\asp.dll).
Related to my original posting, i want to clarify that all=20
my servers are up to date (SP4 + all current security=20
fixes)
Another thing that i've noted, is that if i disable=20
the "annonymous access" option from Directory Security=20
options the following occurs:
1) integrated authentication enabled only:
domainname\username is displayed with the first letter=20
truncated.
2) basic authentication enabled only or both enabled:
username is displayed with the first letter truncated.
thanks for your support.
Alvaro
adltorre DeleteThis @sadesa.com
=20
>-----Original Message-----
>Hi Alvaro,
>
>Researching your problem I've found the following=20
regarding the SP4 version=20
>of the ACHG.HTR file:=20
>
>The SP4 version of ACHG.HTR contains this function:
>
> function IsInvalidUsername(username)
> dim re
> set re =3D new RegExp
> ' list of invalid characters in a user name.
> re.Pattern =3D "[/\\""\[\]:<>\+=3D;,@]"
> IsInvalidUsername =3D re.Test(username)
> end function
>
>If any of these characters in the re.Pattern line exists=20
then the user name=20
>will fail.=20
>
>From your original posting I understand the following:=20
>
>You have recreated the iisadmpwd VirDir following the=20
steps in Q269082
>You replaced all the htr files from a server that has not=20
been updated and=20
>is currently functioning
>You ran the ISM2ASP tool that updates the .htr script=20
mapping to ASP.dll;=20
>I'm assuming per the steps in Q331834
>
>None of these three steps were successful, is this=20
correct?=20
>
>One thing I'd like to confirm is the current script=20
mapping for the .htr=20
>extension. Please go to the Internet Service Manager=20
console, right-click=20
>on the Server node, click the Edit button across from WWW=20
Services field=20
>and select the Home Directory Tab. From Home Directory=20
click the=20
>Configuration button. Scroll down to the .htr entry,=20
doubleclick and verify=20
>the mapping which should be to "C:\WINNT\system32
\inetsrv\asp.dll"=20
>
>If this is the mapping is as expected, another=20
possibility is that for some=20
>reason it didn't propogate to all the websites. This can=20
be easily fixed by=20
>making a change to the path (i.e. changing asp.dll to=20
asp.dlx) and=20
>attempting to commit the change. Because the path is=20
invalid it will fail.=20
>Change the path back to the original entry and commit.=20
You will be prompted=20
>to propogate to the child nodes (all existing configured=20
website); Click=20
>the Select All button or select only those websites to=20
which this change=20
>should be applied.
>
>Let me know if this works. If not, I'll need to do some=20
more research. I'll=20
>check for a posting from you daily and if nothing is=20
returned by close of=20
>business Friday 10/31, I'll assume that all is OK and the=20
post can be=20
>closed as resolved. =20
>
>Thank you,
>
>Vicki Stearns [MSFT]
>Microsoft IIS
>vickis@online.microsoft.com
>
>Please do not send email directly to this alias. This=20
>is our online account name for newsgroup participation=20
only.
>
>This posting is provided "AS IS" with no warranties, and=20
confers no rights.=20
> You assume all risk for your use. =A9 2001 Microsoft=20
Corporation. All rights=20
>reserved.
>
>.
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Invalid characters