We're running a Tomcat application that grabs the system IP addresses. Tomcat is installed as a Windows service and is set to start automatically when Windows starts. The box is set to have a static IP address. We've been noticing that the IP address is often not assigned to the adapter by the time Windows starts up, as indicated by a diagnostic JSP page we have running in our web application. We show a 169. IP address for the adapter when the Tomcat service starts. Can anyone shed some light on the timing of Windows services startup? Is there any way to guarantee that one particular service (in this case Tomcat) does not start until IP address assignment is complete? We could code around this in the web application, but it would be ideal to solve it at the OS level. Thanks!

I noticed VMWare as your Manufacturer/Model. Is this a Virtual Machine? "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

Yeah, it's running inside ESX server.

That may have something to do with it. I'm not an expert in troubleshooting oddities with ESX or VMWare in general...yet. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

Well, the network adapter is indeed a VmWare adapter, but it has a static IP address assigned to it and seems to just be in a weird state for a short period of time. I suspect that's all Windows.

I disagree. I've never seen a Windows server do that on a physical server, and I have ton of experience with Windows. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"