Hi!
In a Windows 2003 Active Directory environment I have
several Windows Server 2003 machines installed with two
Gigabit network adapters, configured for fault tolerance
(fail over)
NIC #1 is connected to switch #1 and NIC #2 is connected
to switch #2. (Both on same subnet) The network adapters
are configured for 100/FULL.
When a start up a Windows server 2003 machine it logs
userenv 1054 "Windows cannot obtain the domain controller
name for your computer network. (A socket operation was
attempted to an unreachable host.) Group Policy
processing aborted."
Because of this error, the startup script fails to run.
I have done to following to try to isolate the problem:
- Checked DNS config. Everything works fine and group
policies are applied after a periodical gpo refresh or
initiated manually with gpupdate.exe. (But gpo fails in
the system startup)
- Updated my gigabit nic drivers.
- Added the DisableDHCPMediaSense=1 key.
None of the above tasks helped.
But when I dropped the NIC teams on the servers the
startup script was executed as expected and the 1054
userenv log did not appear anymore.
My customer is not satisfied with this resolution and
demands to get the NIC teams to work together with the
GPO.
Can anybody help me with this case? Or should I contact
MS support right away?
|
Similar Threads
Linear Mode
