Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WMP54G and group policies

Status
Not open for further replies.

basspro

IS-IT--Management
Jul 12, 2002
137
US
Installed WMP54G in Gateway E4100 running Windows 2000 Pro.
Multiple users access PC. We are using group policies to determine desktop settings.

It seems that about half the time the user logs on before the wireless connection is made to the network, thus the user does not receive the group policy settings. If the user powers off the PC one or two times the policy settings will eventually occur. Obviously, we would prefer that the policy settings take affect immediately.

Is there any way to ensure that the wireless card will make its network connection upon startup prior to the user signing on?

Thanks.
 
Asynchronous processing of logon commands.

You may experience issues when logging into domains using Windows XP Pro. This is caused by the asyncronous loading of networking during the boot up process. This speeds up the login process in a stand-alone workstation by allowing the user to log in with cached logon credentials before the network is fully ready.

To disable this "feature" and restore your domain logons to "normal", open the MMC and add the group policy snap-in. Under Computer Configuration-->Administrative Templates-->System-->Logon, change "Always wait for the network at computer startup and logon" to ENABLED.

This can be fed to clients via a group policy from a Windows 2000 server by upgrading the standard policy template with the XP policy template. Since this is an XP only command, non-XP systems will ignore it in a domain distributed group policy.

 
Thanks bcastner, already tried that. Did not have any effect or I should say still have problem.
 
Thanks again bcastner. GPO changes are going into effect. Once I finally get connected I can see other GPO settings that are within same policy.

To clarify situation, if user powers on PC may or may not connect to network prior to user signing on, thus will not get GPO for desktop settings. If user signs off and then signs back on (not a power off/power on) then user connects to network and gets GPO.
 
. Identify the service components of the adapter as you are using it

. move these as a WSH Script or .BAT or .CMD to a single startup file, using Scheduled Tasks set to the 'at Startup' schedule, and pass at local Admin user priviliges at logon

. In the alternative, move the clients to XP and install only the Broadcom portion of the driver. Use the native XP Wireless Zero Configuration Service to handle the adapter initialization and logon

My belief is that you need to initialize some Service entries, and it is not possible to do so until the user logon occurs. Either force the Service entries earlier at Startup as suggeted above, or use the native XP Wireles service features.
 
Hi There,

I'm having the same problem with my group policy software installation settings.

I have a netgear WG311.

When the PC Boots, the driver is incorrectly reporting to the system that the network adapter and tcp/ip is up.

The client then tries to contact the domain controller, and fails. A netlogon event is made, with the error message.

About 20 seconds later, tcp/ip is established and then network connectivity is available.

I have found NO work around for this, and have given up. I will be trying to use a normal network card with a dlink gateway / access point in client mode to get it to work.

Good luck.



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top