UNSOLVED

HansVing

updated

24 years ago

H

HansVing

1 Rookie

•

4 Posts

0

31107

July 10th, 2002 12:00

Network startup problem GX260 Intel PRO/1000 MT

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.

  • droid256

    73 Posts

    964

    0

    Posted July 11th, 2002 16:00

    Try this registry setting I found on Intels site.

    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.


  • daddyroo2k

    10 Posts

    964

    0

    Posted July 19th, 2002 09:00

    So in the registry do you need to look for the Intel "Kenai-32M" string or just the mention of the Intel Pro 1000 MT card

  • daddyroo2k

    10 Posts

    964

    0

    Posted July 30th, 2002 08:00

    This is fixed with the new A01 drivers on the dell website

    http://support.ap.dell.com

  • rahermon

    2 Posts

    964

    0

    Posted October 21st, 2002 23:00

    I have the same problem and have not been able to resolve it.

    1. 60 machines and a DC on the same subnet.
    2. 20 of the 60 are GX260 and no luck with gpo at boot.
    3.  The other 40 ok, not one error.
    4. I have used 3 different drivers(xp,intel,and dell) with no success.
    5. Adding another nic works like a charm not a single error.

     The updated drivers showed improvement by ;

    1. taking longer at the starting network connections message but the event viewer still shows the error.
    2. Also with the new drivers logon into the domain after boot is now possible where as before it will take about 2mins for the computer to locate the DC.

    Has anyone resolved this problem or am I the onlyone having it. Any suggestions will be greatly appreciated.

    Regards,

    Ramon

  • rahermon

    2 Posts

    964

    0

    Posted October 24th, 2002 11:00

    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.

    Some feedback will be nice.

    Regards,
    Ramon

  • Bully_de

    1 Message

    964

    0

    Posted November 7th, 2002 08:00

    Hai All,

    i have exactly the same Prob:

    GX260 w Intel Pro 1000 MT onboard , WinXP / Sp1 didnt work well with my W2k (SP3) DC's.

    The Client (NETLOGON) can't find any DC for the machines authentication.

    So the (Machin-related) GPO's dont work.

    Rest off the network (including User-related) GPO's and GX260 with Win2k Prof. works very fine.

    Deaktivating the (1000MT) NIC and inserting a 3c905B NIC -> Works very fine...

    I Think it's a Timing Problem between Win XP and the Intel 1000MT NIC.

    Different drivers for the intell 1000 MT dind't help.

    If i see  some solution i will take it here...

    greetings

    Andreas

    PS.: Sorry about my bad english...

     

     

     

  • droid256

    73 Posts

    964

    0

    Posted November 7th, 2002 16:00

    Take a look at Microsoft article Q326152

        http://support.microsoft.com/default.aspx?scid=kb;en-us;Q326152

     

    It looks like MS is admitting there is a problem with their OS.

    Droid

  • hmc6422

    1 Message

    964

    0

    Posted December 20th, 2002 08:00

    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.

    Is any one kwon a solution.

    Regards.

  • blackened

    2 Posts

    964

    0

    Posted February 18th, 2003 15:00

    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!

  • pepperguy

    9 Posts

    350

    0

    Posted February 25th, 2003 16:00

    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]).

    Anyone have a solution?!?!