Update: I think I figured it out. It appears that the service is started before the rest of the networking subsystem is up.
I manually added the following within the <service/> block to C:\Program Files (x86)\Jenkins\Jenkins.xml: <depend>DNS</depend> Then stopped the Jenkins service, and unregistered and registered the service using the following in an administrative command prompt: > cd \Program Files (x86)\Jenkins > net stop jenkins > jenkins uninstall > jenkins install > net start jenkins Now Jenkins seems to come up properly each time I reboot. Disclaimer: I'm not sure if that is the correct dependency, but it works for me. John -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f840d91a-9eb3-4e68-b78e-e65a5759dd95%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
