I have a NW server running a couple of drivers and one of them refuses to auto-start, and then start.
I have only noticed this in the last couple of weeks and this server has been running for many months.

The problem only manifests itself when the server is rebooted. The drivers running on the box are the eDir and AD and it's the eDir driver that doesn't fire up.
I'm not aware of any changes to this box, it just sits there and does it's thing reliably. The only way I can get the driver to fire up is to unload dirxml and reload it.

Has anyone seen this?