Strange problem with Group Policies and machine startup.

[maniac]

OK, this one has me stumped. Windows XP, Server 2003 based network - old but reliable up until now that is!

 

I seem to have some issues surrounding group policies applying properly at machine startup, but only on my nice new batch of desktops. The odd thing is it's only doing it on some of them and not all of them, it really is the most odd problem.

 

There are no problems for any of the other workstations on my system, other machines in the same room are fine while other are not.

 

The error I get at machine startup is this.

 

Event Type: Error

Event Source: NETLOGON

Event Category: None

Event ID: 5719

Date: 26/08/2010

Time: 10:05:25

User: N/A

Computer: 17-12

Description:

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

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

Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.

 

For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

Data:

0000: 5e 00 00 c0 ^..À

 

Together with this.

 

Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1054

Date: 26/08/2010

Time: 10:05:25

User: NT AUTHORITY\SYSTEM

Computer: 17-12

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.

 

For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

 

The odd thing is as soon as the logon prompt comes up, I'm able to logon to a domain account with no problems. It's also processing some of my group policies as my startup scrripts run fine, and all the user group policies process fine at logon.

 

Has anyone got any ideas? There are no DNS issues on my system, both domain controllers are running ok with no errors reported on them and I've re-booted them for good measure as well, no cabling issues I've tried other network ports and switches just incase it was a duff switch or something like that, and all other workstations in the school are fine apart from this small selection of new ones. Indeed 6 out of this batch of 20 new workstations are also fine, it's really most odd.

 

Any help much appreciated

 

Mike.

[SYNACK]

Probably the mediasense issue, if it is its a combo of XP being really old and its network stack being a bit iffy along with messy drivers/NIC cards. This sounds like the mediasense issue where the network card driver does not force the computer to wait until the NIC has fully brought up IP, this is exaserbated by fast machines that can outpase the network card with regards to being in a ready state. There is a reg fix for it though so give it a go:

How to disable the Media Sensing feature for TCP/IP in Windows

 

MS Explaination: http://support.microsoft.com/kb/326152

 

Quite a common fault with some newer machines and also certain 'brands' on network cards (I'm glareing at you SiS 900 series). Happily they have fixed this in newer versions of Windows.

[maniac]

Probably the mediasense issue, if it is its a combo of XP being really old and its network stack being a bit iffy along with messy drivers/NIC cards. This sounds like the mediasense issue where the network card driver does not force the computer to wait until the NIC has fully brought up IP, this is exaserbated by fast machines that can outpase the network card with regards to being in a ready state. There is a reg fix for it though so give it a go:

How to disable the Media Sensing feature for TCP/IP in Windows

 

Quite a common fault with some newer machines and also certain 'brands' on network cards (I'm glareing at you SiS 900 series). Happily they have fixed this in newer versions of Windows.

 

MS Explaination: Cannot connect to domain controller and cannot apply Group Policy with Gigabit Ethernet devices

 

 

You sir are officially a legend, that worked a treat!

 

I've been scratching my head for almost a day trying to solve that one, and you come up with the solution in 5 minutes, brilliant!

 

Mike.

[3s-gtech]

Nvidia nForce network cards are also prone to this, as fitted to many machines with onboard Geforce graphics (including Macs I think).

[sted]

Nvidia nForce network cards are also prone to this, as fitted to many machines with onboard Geforce graphics (including Macs I think).

 

yes but they are just awful nics period. Ive also had similar issues fixed by setting pcs to 100mb 1/2 duplex rather than auto/ firmware flashing hp switches it seemed to affect some older dells with intel gb cards on 100mb hp switches but either forcing to a set speed or flashing the switch seemed to solve it