<div>
I think that would be a workaround that would be pretty permanent. However it seems like the server is trying to connect to the domain controller before the server is connected for some reason. Any reason that this would happen?<br />
<br />
Thanks for the response.
</div>


<div>
Again that may be a workaround. There are only two servers (VMs) having this issue. The other one's that use the same logon account are not having the issue. I am trying to find out why the server is trying to authenticate before there is network connectivity. It's just weird.
</div>


<div>
&quot;<i>Again that may be a workaround.</i>&quot; - yes - as your question was<br />

<blockquote>
Is there a way to set the service to start after the network is connected? Or just change it so it starts after the server is online?
</blockquote>
&quot;Delayed start&quot; is the easiest option you have.<br />
You can use a triggered start on network startup as well, but that's back to the command line:<br />

<pre><code class="code-1 nolinks" id="code-20-42049368-1"><span>sc.exe triggerinfo &quot;SomeService&quot; start/networkon</span>
</code></pre>
<br />
That said, it's not &quot;the server is trying to authenticate before there is network connectivity&quot; - the Service Manager will be starting the services as soon as possible, and that's that.<br />
If the service in question happens to be using a domain account, and the domain is not available yet, then, well, the service won't start, the same way you won't be able to logon if the domain isn't available (and cached credentials are not available). <br />
In other words: this seems to be more a networking issue than an issue with the server itself. Different hosts, different NICs, different switches, different routers, different firewalls, different networks, all kinds of arbitrary reasons.<br />
If you don't have network problems once the machines have fully rebooted, and &quot;Delayed Start&quot; fixes the issue, then I would only investigate this further if you're really bored.<br />
<br />
On a side note: when you say &quot;<i>When you start them manually they start and run with no issues.</i>&quot;: do you have to re-enter the password for the services to start, or can you just start them without doing anything else?
</div>


<div>
Yeah i just set it to delayed start. It's weird. The two servers with the problem are on different hosts but in the same cluster. The one that is working is on a different host in a different cluster. They are all running on the same HP gen 9s, in the same vlan. <br />
<br />
Crazy. <br />
<br />
Our tech in the UK will be rebooting the test server tonight to make sure that everything is working now.
</div>


<div>
The delayed start worked on all the services except for three of them. They are &quot;hung&quot; on startup. I talked to the owner of the server and he informed me that these services take in upwards of a minute to start. So I changed the startup timeout to two minutes. They are still hanging. When started manually they still work fine.
</div>


<div>
Either set to delay start, add service to depend on or enabled cached logons.<br />
<br />
Selected delay start as best because it is easiest and delay can be configure
</div>


<div>
<div class="content wysiwyg-content">
There are several services that are failing to start at the server boot. When you start them manually they start and run with no issues. The service account is a domain account which is giving an error in the event log saying that no domain controller can be found. This lets me know that the service is trying to start before it's connected to the network. Is there a way to set the service to start after the network is connected? Or just change it so it starts after the server is online? We also cannot do cached creds. <br />
<br />
Thanks in advance<br />
Josef
</div>
</div>


There are several services that are failing to start at the server boot. When you start them manually they start and run with no issues. The service account is a domain account which is giving an error in the event log saying that no domain controller can be found. This lets me know that the service is trying to start before it's connected to the network. Is there a way to set the service to start after the network is connected? Or just change it so it starts after the server is online? We also cannot do cached creds. 

Thanks in advance
Josef

Start a windows service after there is network connectivity

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.