I have seen a trend in our servers, and totally confirmed it with the install of MSSQL2, it goes like this, install Windows 2003 with SP1, configure your network.
Reboot, and you will see network comes up as one of the first services up, network is even up and pinging if a chkdsk were to run(not tested on sp2 yet, but I am 99% sure it would be done now). So in Windows 2003, and 2003 sp1, it comes up not exactly at pre-boot, but as one of the earliest services.
Fast forward, install SP2, and it will load the login screen and all, then launch network services like it is any regular service in the order.
I noticed on win23 when ping "did not come up", it was actually going fine, just had to get fully booted, then I confirmed with MSSQL2 OS install/patching process.
So, it is not a game changing issue, just one that can be a bit of a difference and get you worried if you are used to ping coming back in 20 timeout or less, and now it is taking 30 or so on a reboot.
Reboot, and you will see network comes up as one of the first services up, network is even up and pinging if a chkdsk were to run(not tested on sp2 yet, but I am 99% sure it would be done now). So in Windows 2003, and 2003 sp1, it comes up not exactly at pre-boot, but as one of the earliest services.
Fast forward, install SP2, and it will load the login screen and all, then launch network services like it is any regular service in the order.
I noticed on win23 when ping "did not come up", it was actually going fine, just had to get fully booted, then I confirmed with MSSQL2 OS install/patching process.
So, it is not a game changing issue, just one that can be a bit of a difference and get you worried if you are used to ping coming back in 20 timeout or less, and now it is taking 30 or so on a reboot.