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.

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

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

http://support.ap.dell.com

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

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

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

 

 

 

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

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.

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

Anyone have a solution?!?!

I just disabled the integrated NIC on my GX260 in the BIOS and installed an Intel Pro/100 S PCI NIC instead...The problem is COMPLETELY gone!  It logs in successfully, finds the domain controller and pulls the group policies w/o fail 10 out of 10 times!!  This is definitely a problem with the on-board Intel Gigabit NIC and its drivers.  Dell/Intel needs to address this ASAP, because I'm not buying 150 new NICs! 

Try it yourself!!

Grant

Hi

There is more simple solution, but not suitable for every network infrastructure.

If You also have problem with DHCP server (check workstation event log), just set on every workstation static IP and domain DNS address, and that's it. No driver reinstalation, registry modification needed.

Has anyone been able to finalize these fixes and suggestions? I have tried a few to no avail and am going to try the registry edit next. What is the deal here? The triangle fingerpointing? Dell says it's Intel, Intel says it's Cisco, Cisco says it's Dell?

 

What gives?

 

Anyone?

I just had this pop up again on a gx270 after I thougn I'd seen the last of it. Seems like the faster the machines get , the greater chance of a problem. The reg key did't fix it this time. Nor did changing the link speed. Disabling DHCP media sense isn't an option for this machine. The machine is currently plugged into a 10/100 unmanaged switch, so there's no spanning tree going on.

Any suggestions ?

 

I have been getting errors where clients could not download the GPO and clients not being able to see the domain. I tried all the fixes posted here to no avail.  What I came by that fixed my issue was that windows 2000 servers and windows xp sp1 clients that require server signatures do not communicate.  The fix microsoft recommends is on the domain conroller policy turing the following to DISABLE or installing a security patch on the domain contollers and on all the clients. http://support.microsoft.com/default.aspx?scid=kb;en-us;Q329170

1. Digitally Sign Client Communications (Always)
2. Digitally Sign Client Communication (When Possible)
3. Digitally Sign Server Communication (Always)
4. Digitally Sign Server Communication (When Possible)

I just set these to DISABLE and all the errors dissapeared.  I did not install the patch cause that would require me gettig up and we do not want that :)

Hope this helps resolve some issues.