I have a server that takes several minutes for the NIC to bind itself to the network upon startup (it has a statically-configured IP). This causes the WINS and Intersite Messaging services (and sometimes DNS) to fail to start, since they're dependent on a network connection, and they must be started manually. I've done firmware updates and checked for any odd drivers/services, but no luck so far. The server is running Server 2008 R2 SP1 and only has one NIC installed.
(On a side note, there are two other small but odd problems occuring with the server. The server had the issue described in KB2298620, which I've fixed. The other problem occurs in Windows Server Backup. No events appear in the upper portion of the window, despite the fact that backups are running in the background. Whenever I attempt to modify the backup schedule, it gives me the error "Not enough storage is available to process this command" and appears to fail, when, in fact, it actually succeeds. These may be separate issues, but something tells me that some of these might share a common root cause.)