Integrated Intel PRO/1000 MT and DELL R42108.exe driver. The computer have a startup problem on Windows XP. The initialization is to long. The Windows 2000 Domain can not be found fast so the computer policy don’t load.
Even viewer log:
Event ID: 1054
Source: Userenv
Type: Error
Description:
Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted). Group Policy processing aborted.
A ping to this machine give response two seconds after the logon popup display. To fast logon gives a error on the display: The domain is not available. Wait 3 seconds and y can logon wel.
The gigabit NDIS5 driver supports a registry parameter called WaitAutoNegComplete which causes enough of a delay to allow the network connection to be running when the operating system attempts to apply Group Policy.
*y represents the network adapter instance corresponding to the Intel Kenai-32M. There will be many network adapter instances listed ranging from 0000 to possibly 0012. You will need to find the Intel instance and add the following Value: DWORD WaitAutoNegComplete. The default setting will be 0, set the value to a 1.
I forgot to mention that when using the new drivers the gpo's work.
Once, immediately after boot That is it. That one time. And about once every 20 reboots after that, with luck.
I heard rumors that the new drivers will fix the gpo problems. So I can only assume that I am overlooking something. If anyone has any ideas I will be most grateful.
I Have an Optilex GX260 with an Intel Pro / 1000 MT Network Connection under Windows XP Pro. That I configured to connect to my LAN but I can not Ping any one of the group.
The physical connection is OK. I mean between the Switch and the PC. But the ping not responding.
The Switch is a planet one 10/100 Mbps and the status of the network connection in the PC is 100.0 Mbps.
Has anyone come up with a resolution to this problem? It really annoys me that the only 2 options is to disable media sense or put in a different network adapter! There is absolutely no reason that I should have to buy 26 network adapters (which will use up my only PCI slot) to fix this problem. Not to mention the fact that they will have to be low profile.
While this problem is affecting my machines, I might as well throw our company's security out the window! Almost ALL of the security related GPO settings fall under the Computer side of the GPO, and, although the "Resultant set of policy" shows that the correct GPO's are being applied, all the settings are Not Configured. Unacceptable!
That's what's really frustrating to me, it WORKS the first time you install or re-install the updated drivers. From there on out though, it's the same problem as before.
Once the system boots up though, a log off/log on fixes things, it's only bringing it up from a cold state when it fails (at least for us [150 pc's]).
droid256
73 Posts
964
0
Posted July 11th, 2002 16:00
Droid
The gigabit NDIS5 driver supports a registry parameter called WaitAutoNegComplete which causes enough of a delay to allow the network connection to be running when the operating system attempts to apply Group Policy.
Location:
HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-xxxx-xxxx-xxxx-xxxxxxx
xxxxx}\y*
*y represents the network adapter instance corresponding to the Intel Kenai-32M. There will be many network adapter instances listed ranging from 0000 to possibly 0012. You will need to find the Intel instance and add the following Value: DWORD WaitAutoNegComplete. The default setting will be 0, set the value to a 1.