Re: Group Policy loading
From: modrejpes (modrejpes.1klka4_at_mail.mcse.ms)
Date: 02/17/05
- Next message: Malik: "USB"
- Previous message: jc: "Setting Proxy settings using Group Policy"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 17 Feb 2005 03:41:42 -0600
This is quite an old thread, but I recently experienced the same
behaviour connecting the new Intel D915GUX motherboard based computer
to a domain.
I tested it in several different configurations, starting with a "live"
network and ending with a freshly installed W2003 DC and the XP
workstation connected directly with a crossed cable (forced 100Mbps
full duplex to eliminate speed negotiation) - the result was always the
same. The OS on the workstation was Win XP (tested with SP1 and SP2,
same results).
The motherboard utilizes an on-board Marvell Yukon 1GB network card.
When I disabled this on-board card and installed an additional PCI
network adapter, the error messages disappeard and group policies were
applied correctly. The same (without problem) with a different
motherboard with an on-board Intel chip based network card.
My conclusion is that this behaviour is not (only) caused by Win XP but
has something to do with network drivers.
Christopher Hill wrote:
> *I have also experinced this problem with almost exactly=20
> the same setup. Here is a copy of a support incident that=20
> I have just set up with Microsoft. There is a fix you can=20
> put in in the mean time. (NB You might find a copy of this=20
> message on an Internet forum saying that I think it's the=20
> Dell drivers. I posted that yesterday but after research=20
> it seems to be a problem with XP, not the Dell drivers):
>
> My support incident to Microsoft starts here:
>
> I am experiencing a problem with a Dell OptiPlex SX270 and=20
> a Dell TrueMobile 1180 USB 802.11b wireless card,=20
> connecting to a Buffalo WLA-G54 Wireless Access Point. I=20
> have installed the latest wireless rollup (826942) and the=20
> latest Dell and Buffalo firmware and drivers but to no=20
> avail. This is a clean RIS install of Windows XP SP1 with=20
> all the latest hotfixes using the Microsoft Wireless Zero=20
> Configuration service, so there's no dodgy software or=20
> settings. I am also using the SyncForegroundPolicy=20
> ('Always wait for the network at computer startup and=20
> logon') option to make Windows XP wait for the network to=20
> start up before attempting to apply Group Policy.
>
> I have also tried using another manufacturer's drivers=20
> (SiteCom's WL-012 driver) by editing the PCIID in the .inf=20
> file to match that of the Dell TrueMobile card. These=20
> SiteCom drivers are a lot more up to date and work fine on=20
> the Dell card for normal network operations but still have=20
> the problem described below. This makes me think that the=20
> problem is not with the drivers but with Windows XP itself.
>
> The problem is that Group Policy objects are not applying=20
> to the system when the system is booted with only the=20
> wireless card connected. The Application Event Log=20
> contains the following error:
>
> Event Type: Error
> Event Source: Userenv
> Event Category: None
> Event ID: 1054
> Date: 17/03/2004
> Time: 11:09:17
> User: NT AUTHORITY\SYSTEM
> Computer: CON01
> Description:
> Windows cannot obtain the domain controller name for your=20
> computer network. (The specified domain either does not=20
> exist or could not be contacted. ). Group Policy=20
> processing aborted.=20
>
> For more information, see Help and Support Center at=20
> http://go.microsoft.com/fwlink/events.asp.
>
> And the System Event Log contains the following error:
>
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5719
> Date: 17/03/2004
> Time: 11:09:17
> User: N/A
> Computer: CON01
> Description:
> No Domain Controller is available for domain CRGS due to=20
> the following:=20
> There are currently no logon servers available to service=20
> the logon request. .=20
> Make sure that the computer is connected to the network=20
> and try again. If the problem persists, please contact=20
> your domain administrator.
>
> For more information, see Help and Support Center at=20
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 5e 00 00 c0 ^..=C0 =20
>
> Once the system has fully booted up, however, any user is=20
> able to log on to the network and use the network=20
> resources without problems.
>
> If I boot up with the wired connection the GPO *does*=20
> apply properly and everything works as it should.
>
> It seems that Windows XP does not wait long enough for the=20
> wireless card to initialize, negotiate a speed and set up=20
> WEP before attempting to apply Group Policy. But the=20
> wireless card setup does finish in time for the Ctrl-Alt-
> Del logon screen so users are still able to log on without=20
> problems. The wired connection does not have this problem=20
> because it does not take so long to start up.
>
> There is one 'easy' method of fixing the problem, but it=20
> has a side effect. If I follow the instructions at MSKB=20
> article 239924 to enable the DisableDHCPMediaSense key=20
> it'll fix the problem but the side effect is that the=20
> computer takes a *long* time on the 'Preparing network=20
> connections' section of starting up Windows XP, which is=20
> not acceptable. My theory is that this doesn't fix the=20
> problem but just makes the computer wait so long to=20
> prepare the network connections that the wireless card is=20
> able to fully initialize before Group Policy starts.
>
> I think it is to do with XP itself rather than the Dell=20
> drivers. I had this problem when we first started using=20
> Buffalo WLA-CB-G54 PCMCIA wireless cards in our laptops=20
> here, but the problem seems to have largely cured itself.=20
> I did update the Buffalo drivers, which seems to have=20
> helped, but sometimes the problem still occurs even on the=20
> Buffalo cards. However it is intermittent, whereas the=20
> Dell cards do it 99% of the time. Maybe the newer Buffalo=20
> drivers are faster than the older Buffalo drivers and the=20
> Dell drivers at connecting to the wireless network, so=20
> they do not show this problem?
>
> The problem may also manifest itself when the computer has=20
> bad wireless coverage - as when the coverage is poor XP=20
> doesn't wait long enough for the card to negotiate down to=20
> the lower speed so that packets can get through.
>
> It may also have something to do with the fact that I use=20
> a Buffalo WLA-G54 802.11g wireless access point and the=20
> TrueMobile 1180 USB is an 802.11b card. Maybe it takes=20
> that little bit longer to negotiate the lower speed? In=20
> any case, either the TrueMobile drivers or XP itself=20
> shouldn't be giving the 'all clear' to start the GPO=20
> application until the network negotiation is successful.
>
> It may also be related to how 'loaded up' the computer is=20
> (a race condition). Most of the laptops that have Buffalo=20
> cards also have Visual Studio .NET 2003 installed and a=20
> whole load of other stuff: they never have this problem.=20
> Other laptops with Buffalo cards that don't have so much=20
> software installed sometimes have this problem. The Dell=20
> computers with the TrueMobile 1180 have similar amounts=20
> of 'stuff' as these laptops but always have the problem.=20
> Of course, all of the computers have different processor=20
> speeds. This makes me think it might be a combination of=20
> the USB drivers taking longer to start up properly and an=20
> XP race condition.
>
> One other interesting registry key that I would *expect*=20
> to fix the problem is the one documented in these MSKB=20
> articles:
>
> http://support.microsoft.com/default.aspx?scid=3DKB;en-
> us;202840
> http://support.microsoft.com/default.aspx?scid=3DKB;en-
> us;163204
>
> The ExpectedDialupDelay key is supposed to make Windows=20
> wait longer before trying to contact the domain=20
> controller, which is exactly what we need it to do.=20
> However, this key seems to have no effect on the Group=20
> Policy applicator for Windows XP, and in fact XP isn't=20
> listed under the 'The information in this article applies=20
> to' section of the articles. Has the key been removed or=20
> moved under XP, or does it simply not apply to the Group=20
> Policy applicator at startup time?
>
> The best fix would be to put a wait condition so that the=20
> computer checks that all wireless cards (and indeed other=20
> network cards) and the Wireless Zero Configuration Service=20
> (or other client software) have had a chance to fully=20
> initialize before Group Policy starts. Alternatively, the=20
> Group Policy applicator could be configured to use the=20
> ExpectedDialupDelay registry entry or another, new=20
> registry entry, to wait for a certain number of seconds=20
> before attempting to connect to the network. If a new=20
> registry key is created, it would be extremely helpful if=20
> it was possible to set this key inside Group Policy just=20
> as you can with ExpectedDialupDelay, but I do not see why=20
> ExpectedDialupDelay could not be used for both purposes.
>
> Thank you very much for your attention. Please contact me=20
> if you are unsure about any of the above.
>
> >-----Original Message-----
> >Hello everyone,
> >
> >Here is the problem that I am having. I have a system=20
> >that I am working on now that is a Dell OptiPlex SX270=20
> >computer running Windows XP Pro. The system has a built=20
> >in Intel Gig NIC, I have also connected a Dell TrueMobile=20
> >1180 USB Wireless Network Adapter which connects via=20
> >USB. The issue that I have is that GPO's assigned to the=20
> >computer are not loading if the system is using the=20
> >wireless adapter only. If the system is connected via=20
> >the Ethernet cable then the computer GPO's process. We=20
> >currently install and update our antivirus software using=20
> >the Software Installation option on the computer=20
> >configuration section to assign the software to the=20
> >computers in the domain.
> >
> >If the computer only has the USB NIC and no wired network=20
> >connecter the following errors are in the event log.
> >
> >System
> >Netlogon Event ID: 5719
> >No Domain Controller is available for domain due to the=20
> >following:
> >There are currently no logon servers available to service=20
> >the logon request...
> >
> >Application
> >Userenv Event ID: 1054
> >Windows cannot obtain the domain controller name for your=20
> >computer network. (The specified domain either does not=20
> >exist or could not be contacted.) Group Policy=20
> >processing aborted.
> >
> >If the system has the wired Ethernet connection then I do=20
> >not get these error messages in the event log during=20
> >startup and the GPO's process and the software installs. =20
> >I have had no problems with logging into the domain with=20
> >a domain user account with the computer on wireless only.
> >
> >Is there a problem with using USB NIC's and computer=20
> >GPO's? Is the USB port and USB network adapter not=20
> >getting initialized in time for the GPO's get loaded?
> >I don't know what the timeline is for drives to get=20
> >loaded and Active Directory processing.
> >
> >So far I have checked another system that we have just=20
> >like this one and it is having the same problems. =20
> >However it appears that we have not had this problem with=20
> >desktops using PIC wireless NIC's and laptops that use=20
> >mini PCI or PCMICA wireless NIC's.
> >
> >Thanks for anyone's help.
> >Brent
> >
> >.
> > *
-- modrejpes ------------------------------------------------------------------------ Posted via http://www.mcse.ms ------------------------------------------------------------------------ View this thread: http://www.mcse.ms/message473988.html
- Next message: Malik: "USB"
- Previous message: jc: "Setting Proxy settings using Group Policy"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
