For security reasons, IIS6 does not allow any code to execute by default
(only static files with configured MIMEType can be served). A few
applications will detect IIS6 and add/enable themselves in Web Service
Extensions, but vast majority of applications require manual setup steps.
You will have to set up a Web Service Extension for your custom ISAPI and
enable it so that IIS6 will allow it to execute. Please search this
newsgroup, IIS documentation (from IIS Manager UI, F1 help Troubleshooting
section should be enough) about "404" errors and you should find the
solution.
FYI: ISAPI has always been able to retrieve the remote IP WITHOUT using
Winsock. Just use GetServerVariable() on "REMOTE_ADDR" and "REMOTE_PORT" as
documented on MSDN.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"joncao@cox.net" <joncao.DeleteThis@cox.net@discussions.microsoft.com> wrote in message
news:7D7602A7-C5EB-487D-9704-D8A0F34360F0@microsoft.com...
I have created an ISAPI dll file by using VC++ ISAPI Extension wizard.
I posted it into IIS 5 server, it worked fine. However, when I posted into
IIS6 server, it doesn't work.
When I said it works, it populated what i want: the HTML interface; dons't
work, the page can not be found error appearing.
I have posted this dll file into virtual "scripts" directories acording the
doucmentati, on both of IIS5 and IIS6 with the exact same steps and
procedures.
What this DLL does is that it gets information from remote IP through
WinSock and post thoese info into HTML.
Thnaks very much in advance!
>> Stay informed about: ISAPI Extension DLL don't work on IIS6