Hi System Specs: I have DC: Server 2008 R2 Enterprise running AD and a Second Server Running File services.12 Client Machines are laptops and use wireless access points to get to the network.All other machines connect to a network switch. Problem: On all the wireless client machines there are specific folders that need to appear as mapped drives, using GPM i created the maps of which has worked successfully the first time. However i have noted the following issues: Mapped drive's do not reconnecting at logon.Each user will need to initiate a connection to the DC example: \\server1 {enter their username and password} and secondly \\server2 (enter their username and password}----> intermittent problem.When updating GP using gpupdate /force, i notice that the group policy does not update. Tests Conducted: I connected the Laptops using cables and all works well.With wireless on i tried writing a script with {Net use}, which still did not work. Findings: I fond this error in the event viewer with event ID: 1129 {The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.} where the ErrorDescription is: The Network is not present or not started. Help Needed: I know people have encountered this problem before and the feedback is that it is problem when windows is logging on and the Network takes long to initialize.Is there a way i can resolve this problem. Any help will be appreciated.

1. Unles you show the gpo settings it is hardlz possible to find solution. 2. For wireless system I would recommend start here http://www.petri.co.il/creating_wireless_gpo_settings.htm 3. Try to limit number of parameters that affect the wireless behaviour, starting with disabling firewall (for test only) Regards Milos

Hi, If you connect Windows 7 via wireless, try to manually map network server for test. Or use \\Ipaddress\foldername or \\servername\foldername to access share folder to see if any issue occur. And you can also try to temporary disable firewall and check if any firewall configuration on network switch. Furthermore, you can also check "Always wait for the network at computer startup and logon" policy is enabled under Computer Configuration/Administrative Templates/System/Logon in the Group Policy. Hope that helps. Regards, Leo Huang TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Leo Huang TechNet Community Support

Hi, Any update? Please feel free to let me know if it works. Thanks. Regards, Leo Huang TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Leo Huang TechNet Community Support

Hi, i apologise for the late response, i was involved in accident and away for a bit. However i will test this method today. Here is a snap shot of the Group Policy Settings. http://imageshack.us/photo/my-images/205/gpsettings.png/ Thank you guys for the replies, i will update you accordingly.Jermaine Dorasamy

Hi Milos, Thank you for the reply, i have read through the link it is interesting, however was not the resolution to the issue i am having. Well now i learned something new with group policies in that article, "I am fairly new to all of this and willing to learn" I tried with the firewall off and it did the samething so that was eliminated. Jermaine Dorasamy

Hi Leo, As stated in my response to Milos "I am fairly new to this", I did exactly as you have said and it has seemed to have worked, I have forced the new settings onto three other laptops as well as my own and the drives have mapped, i have noted another problem being resolved in doing this "When on wireless the administrative tools on my laptop always gave me hassles to connect to the DC, but now it is working". Thank you for a quick and easy solution. Settings that worked from your suggestions was: Changing the GP - "Always wait for the network at computer startup and logon" policy is enabled under Computer Configuration/Administrative Templates/System/Logon in the Group Policy. Jermaine Dorasamy