Hi Yann,
after doing an IISRESET are you able to connect to the webserver? (Ignoreing
netstat for the moment).
I ask this, because IIS has a tendancy not to start up again until a request
comes in and I think it's the IISAdmin process that arbitrates the incoming
connection, fires up IIS (mtx or whatever it is in Win2000) which then
handles the request.
You could either point your browser at the webserver, or use a port scanner
like nmap to probe port 80 (or whatever is appropriate).
This all changes again in Win2003 where HTTP.sys is part of the kernal and
it handles the incoming requests.
Hope that helps.
Later'ish
Craig
--
Craig dot Humphrey at ChapmanTripp dot com
"Yann" wrote:
> Hi,
>
> My server is a stand-alone Windows 2000 Advanced Server SP4 (but not
> up-to-date with all the patches) that runs IIS 5.
>
> I use a dll redirector in IIS to redirect HTTP to other weblogic
> applications, sometimes the redirector hangs up (usually when the dllhost.exe
> process is around 1.6GB of memory) and I have to restart IIS.
> Stopping the IIS Admin service doesn't work so well, and then I have to use
> the iisreset.exe command-line which works fine... except that after running
> this command, netstat doesn't display anything anymore.
> I have the same problem if I use TCPView from Sysinternals: only a few
> connections are displayed but the server seems not to be listening on the
> port 80 (but it is because the redirection works back again). Using Process
> Explorer from Sysinternals, and displaying the properties of inetinfo.exe
> shows the same results: no port listening.
>
> Are there other people who experience this problem?
> If so, have you succeeded resolving it and how?
>
> A reboot of the server resolves everything... but it is a reboot on a
> critical server, so the less we use it the better it is.
>
> Thanks
> Yann
|