>This is Windows Server 2000. Basically, we ended up with the same situation than Windows Server 2003.

I'm not sure, but if ASP isn't running then it's not a Web Connection problem.

It seems there's some problem with the network environment that's causing your server to run into these weird problems. The only thing that Web Connection does that could potentially hurt these issues is the auto-DCOM configuration. Which you shoulud be able to undo easily by setting the default DCOM permissions of the system. Remove all the default DCOM bindings and add them back in - this makes sure that everything is properly bound to a current user account on the system.

Other than that nothing in WWWC has any effect on a system globablly...

+++ Rick ---