Problems with network/DHCP/NIC?

[Sheridan]

In one of our ICT Suites we've got 15 machines, 4 of which are different makes to the others. All are connected to the same switch stack and are Xp Sp3.

 

We've noticed the 4 newer ones generate these sort of errors on every boot:

 

No Domain Controller is available for domain due to the following:

There are currently no logon servers available to service the logon request.

.

 

Then:

 

The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 15 minutes.

 

Then:

 

The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.

 

After several of these we finally get a message that the network card is connected to the network:

 

The system detected that network adapter Realtek...Controller - Packet Scheduler Miniport was connected to the network, and has initiated normal operation over the network adapter.

 

These set of errors mean we get all sorts of problems with Group policy not applying, startup scripts not running etc.

 

All of the PCs in this room are DHCP - the only thing that fixes the problem is switching the 4 dodgy ones to manual IP - then they function as normal.

 

I've tried updated drivers, new cables, swapping ports etc but the fixed IP is the ONLY thing that sorts it!

 

Anyone come across something like this? I thought it was the onboard NIC in these machines but I get the same errors with a seperate NIC installed!

[K.C.Leblanc]

Is the DHCP client service running?

[andyturpie]

I take it you deploy windows via PXE boot or RM CC3/CC4 onto your network, I'm wondering if the NIC driver is being updated via windows update after the initial build and knocking the NIC out a little later?

[SYNACK]

This is because XP is ancient junk and can't cope with faster systems with 1GB/s network cards, you need to turn off media sense:

How to disable the Media Sensing feature for TCP&

[Sheridan]

DHCP is fine - every other machine in the school is getting an address. These ones do get an address but obviously not quick enough!

 

These were created from an image (using WDS) -the drivers on them are correct (even updated to the manufacturers latest with no effect)

 

I'll check out the Media Sense option - although I already tried throttling the NIC back to 100Mbps

[Admiral208]

Have you checked the time on the clients compare to that of the DC?? I had this problem a little while ago and the clocks were about 90 seconds out from each other. changed the clock to a bit of a closer match and it was fine.

[SYNACK]

Yeap its not about a DHCP fault but rather a fault where the subsystems load up a tad quickly in the background and are ready before the NIC is all initilized and has grabbed an IP. This forces it to wait untill it has confirmed IP connectivity before it starts running network related stuff like GP and DC authentication.

 

This has a chunk to do with PCs faster than XP was ever designed to handle and a dodgey driver model that allowed a driver to bring up an interface and see it as ready just because the cable was in as opposed to doing any real checks on the conenctivity.

[chazzy2501]

Check the switch has RSTP/Fast start enabled on those ports.

[Sheridan]

Some good ideas to try thanks, will report back once I've managed to get some time on the PCs (students keep using them, tchoh!)

[HodgeHi]

Synacks media sensing should do the job. I had to do it to a few of my machines before. It's not all of them though (even though they are the same) which is a little odd but still.

[Sheridan]

Yep - had some time to test it out today and disabling the Media Sense worked a treat. I'll keep an eye on them but no errors after several boots now. Great stuff, thanks to all for their suggestions!