Server 2008 odd network card behaviour
We've got a bit of an odd one here.
Over the summer we started upgrading our servers to 2008 server. The DC's have all gone across fine (were DCpromo'd down, rebuilt from scratch rather than upgraded, and DCpromo'd back up) and the fileservers went likewise.
Some stuff is still on 2003 server, for instance our Exchange box, but the core domain infrastructure and file servers are all now migrated to 2008 server.
Now last week we had one of the student file servers - a Stone Computers "intel clone" rack job with dual Intel Pro 1000MT server adaptor and Windows Server 2008 standard - reporting that both network cards were disabled even though they weren't. The affected server could access the network and surf the internet, ping other hosts, open up shares, worked a treat as you'd expect BUT try to access it from any other device and it refused to respond to a ping and you couldn't access any shares on it or even start a RDP session. Just as if the firewall had reenabled itself (it hadn't - it's disabled via a GPO).
Right-click the card, select "enable" as normal, and the server showed the enabling dialogue box but then re-reported the card as disabled. All very odd. Two reboots finally cured it.
Today we've just had the same thing but on another server. This time a HP Proliant DL180 G5, brand new this summer, single Broadcom gigabit card onboard - running Windows Server 2008 enterprise (it's one of our DCs)
The server stopped responding on the network and investigation showed the NIC to have "disabled" itself - even though the server could still access resources on the network.
As with the other server, a reboot cured it - but we shouldn't have to be doing this sort of thing to a server!
Neither server has any power management features enabled on the NIC (why would you want a server to switch a NIC off?) but they are connected into the same stack of Cisco 3750G switches.
Anyone else had this sort of problem or behaviour with their Win 2008 boxes?