You can use the System.ServiceProcess.ServiceController class, from the System.ServiceProcess.dll assembly. Bear in mind that you generally need administrative privileges to stop or start a service, which your ASP.NET code will not normally have. You'll typically have to change the user that the code runs under. On Windows 2000 or Windows XP, you configure this with the <processModel> element in the Machine.config file, and it affects all ASP.NET applications on the server; on Windows Server 2003 you configure it through the Internet Information Services administration console, all applications in the same application pool share the same worker process. Stability. What an interesting concept. -- Chris Maunder