Novell Home

Starting the WWW Service, Hands-free

Novell Cool Solutions: Tip
By George Iosif

Digg This - Slashdot This

Posted: 16 Feb 2005
 

Here's a tip from Cool Solutions contributor George Iosif on avoiding Middle Tier authentication problems by getting control of your WWW service.


Problem

When using eDirectory (8.7.x) and ZENworks for Desktops (4.0.1) with Middle Tier on the same Windows 2000 Server server, sometimes after restarting the server, the Middle Tier authentication fails. For example, if you go to the http://your_server_IP_address/onenet/nsadmin, you are prompted with an authentication dialog that has "Auth-Xtier" as the Realm, instead of your NDS tree.

The actual problem is that the WWW service starts before the NDS service on the same machine.

Solution

One solution, which I believe has already been presented in a TID, is to manually restart the WWW service. However, this might prove unacceptable for some of us, since it requires human intervention every time.

The other solution is to make the WWW service (actually, its name in the registry is "W3SVC") to be dependent on the NDS service. That way, the WWW service won't start before NDS. In order to do that, you have to edit the registry of the Windows server. Here are the steps:

  1. Go to the HKLM\System\CurrentControlSet\Services\W3SVC key.
  2. Edit/add the (Multi-String Value)REG_MULTI_SZ key named "DependOnService". As the value of the key, you add the registry name of the NDS service (in my case, it was "NDS Server0").
  3. Close the registry editing window
  4. .
  5. To verify that you have things set right, check the WWW service dependency (in the "Properties" window of the WWW service from the Services window), which should now list your NDS service.

From now on, everything should run smoothly :).


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell