S
Steve
Hi All:
Last week we set up a new win2K server running IIS5.0. We
applied the MS Lockdownt tool, along with URLScan after
obtaining all needed udates, including the new service
pack 4. We also followed the MS Security guidelines, and
ran the baseline security analyzer. We made a few changes
to things based on the analyzer report.
The problem we now have it that when we try to register a
com dll with a long file name, the path to the file is
being truncated in the registry. For instance, if the path
is temp/something_5_4.dll it is being changed to
temp/somethi~1.dll, apparently using the 8.3 naming
convention.
We've backtracked everything we have done, including re-
running the lockdown tool to remove the changes it made,
but are absolutely having no luck in correcting this.
Would anyone have any ideas as to what we might check next?
Thanks
Steve
Last week we set up a new win2K server running IIS5.0. We
applied the MS Lockdownt tool, along with URLScan after
obtaining all needed udates, including the new service
pack 4. We also followed the MS Security guidelines, and
ran the baseline security analyzer. We made a few changes
to things based on the analyzer report.
The problem we now have it that when we try to register a
com dll with a long file name, the path to the file is
being truncated in the registry. For instance, if the path
is temp/something_5_4.dll it is being changed to
temp/somethi~1.dll, apparently using the 8.3 naming
convention.
We've backtracked everything we have done, including re-
running the lockdown tool to remove the changes it made,
but are absolutely having no luck in correcting this.
Would anyone have any ideas as to what we might check next?
Thanks
Steve