Well, a clarification I guess. I have seen the log entries on the Intels but it is the Broadcoms that have been causing bigger usability problems. I've been through a variety of different driver versions and settings for auto-negotiation, although I haven't tried anything like "wait for link." I'm not seeing a setting like that on the Broadcom drivers. I've been loathe to disable allowing Windows to turn off the NIC because that also means my ability to Wake-on-LAN the computers goes away.
A question: With this issue are you just seeing the log entries and/or Group Policy failures or are you getting real logon errors? For the Broadcoms, when users try to logon I will intermittently get "no logon server is available to service the logon request" if they try to use a domain account. As I mentioned above, if I login with a local account Windows acts like it is trying to get an IP/identify the network then it seems to give us and say we're unplugged.