> Apart from the quasi-Italian at the end, it normally means that the Guardian can't start the Superserver because the network service isn't available yet. Since Windows makes its own decisions about which services to start first, AFAIR, there isn't an obvious solution, as long as you are running both network and Firebird services on the same box.
>
> However, I do recall someone suggesting that it's possible to enumerate the dependencies in the service definition, so that Windows won't even try to start Firebird until the network is running.

Thanks for the reply.

I have set Firebird to be dependent on the LanmanServer (Server) service. Hopefully by the time this has started Windows will have its act together enough to actually start Firebird. Won't know until we get a chance to reboot.