Hi, We have Windows 7 Enterprise 64X machine failing to mapped network drive when they start. even if you log off and log back on again. When I log on I can see for a second the network connect is disconnected and then it show its connected. Some time even the log script doesn't run. According this KB http://support.microsoft.com/kb/938449 if you have PortFast enable you should have this problem. We do have PortFast enable on all of our switchs and I also updated the network card drivers to latest drivers. Log Name: System Source: NETLOGON Date: 30/08/2012 10:09:01 Event ID: 5719 Task Category: None Level: Error Keywords: Classic User: N/A Computer: PC1 Description: This computer was not able to set up a secure session with a domain controller in domain DOMIAN due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="NETLOGON" /> <EventID Qualifiers="0">5719</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-08-30T09:09:01.000000000Z" /> <EventRecordID>8637</EventRecordID> <Channel>System</Channel> <Computer>PC1</Computer> <Security /> </System> <EventData> <Data>DOMAIN</Data> <Data>%%1311</Data> <Binary>5E0000C0</Binary> </EventData> </Event>

Hi, Firstly, please let us know if the issue occur with all your clients in your domain. And, have you tried other four solutions in the article? If not, please have a try. In addition, test the issue in Clean Boot Mode and see how it works. Hope this helps. Jeremy Wu TechNet Community Support

Hi, Thank you for replay I have try all of the solution in that article. Its happening to some user but its not the same user one day I might have and next day someone else might have this problem. I have reset the switch's chanage user location but still same problem for some users. Also the PC I'm having problem is brand new PC, which I have build with nothing on it. One thing I have notices when you log onto windows 7 machine the network card show disconnected for a second and the it show its connected.

Hi, Thanks for the update. However, I notice that the issue occurs randomly and even occurs with brand new machines. Im afraid that the issue is related to your networking configuration. Based on my knowledge, one of the possible causes can be that when a client starts, it will request or renew the lease of the its IP address. If the DHCP Server sends a DHCP negative acknowledgement (DHCPNAK packet) while the IP address that was offered is no longer valid or is now in use by another computer. The client must then begin the lease process again. In brief, it can be just an IP Address conflict issue. Therefore, Please kindly consider double checking the networking side. You can also try to assign some clients with static IP Addresses and see how it works. Hope this helps. Jeremy Wu TechNet Community Support

Its only happening to Windows 7 machine and the one I build its happening all the time. If it was IP conflict it should let me know once I have logged in. Can it be something in GPO

Hi Annie, Thank you for your reply. We have a login script which maps other drive but the home drive is set in AD for users. When users login the home drive gets mapped straight away but the other drives get mapped when login script runs. But for someone reason the home drive is not being mapped and the login script is not running. This is new build PC with latest drivers install from manufacturer.

If you are mapping the drives via script then how about including /persistent switch. Example: NET USE W: \\server\Share /Persistent:yes Face the fact tat we all have plenty to learn about this field. Deal wit the failures, use tem as motivation, learn something new everyday. Claiming false credentials & phantom skillsets will not get you far, especially when 63248651487512645876531864 people in the universe know how 2 use the internet Please remember to click Mark as Answer on the post that helps you, Please VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

In generally win7 boots faster before the network card initailize to be up and working, and did you apllied "Always wait for the network at computer startup and logon." Using group policy ?? In the Group Policy Object Editor (Gpedit.msc), in Administrative Templates\System\Logon, enable the policy setting Always wait for the network at computer startup and logon. The corresponding registry setting is HKLM\Software\Policies\Microsoft\WindowsNT\CurrentVersion\Winlogon!SyncForegroundPolicy This below two links will help you to torch up the way to resolve ur problem http://www.verdiem.com/kb/mapped-drives-do-not-connect-after-wake-low-power-state http://support.microsoft.com/kb/297684 Thanks, suren Face the fact tat we all have plenty to learn about this field. Deal wit the failures, use tem as motivation, learn something new everyday. Claiming false credentials & phantom skillsets will not get you far, especially when 63248651487512645876531864 people in the universe know how 2 use the internet Please remember to click Mark as Answer on the post that helps you, Please VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

Always wait for the network at computer startup and logon. already turn on. Sorry its not the net use in login script Even the personal drive is not mapping. Once you logged in and then run login script it works fine, when you log off and log back in again exactly same problem you have to run login script manually and script to create home folder. Its only Windows 7. Xp is working fine. The user I have does it exactly same every time he logs in.

Hi, Based on my knowledge, when the user is log off, the session of map drive will be aborted. Then when you log on, the session will be created again. So, it is normal that you see the map driver is disconnected and connected in a second when you log on. The error event 5719 means the initialize of the NIC card is not fast enough to catch up the speed of logging on. It is not the problem at all, you can try updating your NIC card driver to the latest to resolve it. Or, you may need to change the NIC card to a new one which is much faster when it is initialized. You can verify it through the port of using for map drive. For example, when you log on Windows 7, it uses port 10001 to create the map drive to the server. Then when you log off, then log on, the port can be changed to 10002, which is not the same to the previous. I think Windows XP has the same behaviour as Windows 7, which is by-design. That is reasonable that the session is aborted when the user is logged off. However, Windows XP may be cannot found in the UI while Windows 7 shows the disconnection. Please understand that the Windows XP also uses another port for creating the new session when the user log on again. If you think this is a problem or issue, you can put the script from logon to the "startup", then it will be bound to the computer but not the user. Whenever which user logon or log off, the mapped drive persists. If you have any concern, please feel free to let me know. Best Regards, Annie

Hi Annie, Thank you for your reply. We have a login script which maps other drive but the home drive is set in AD for users. When users login the home drive gets mapped straight away buy the other drives get mapped when login script runs. But for someone reason the home drive is not being mapped and the login script is not running. This is new build PC with latest drivers install from manufacturer.

Hi, Thanks for the reply. Now you said that the map drive and the home drive is not being mapped when you login. Then at that time, if you log off and log on again, will these drives mapped again like normals? There are two issues can be considered in this problem: when you login, there is no map drive appears.When you login, the map drive got the red x on it. could you please help me verify which status you got from the drivers? Thanks. Best Regards, Annie

One drive does gets mapped sometimes by login script but the home drive is not being mapped does matter how many time user logs off. It works find on windows xp but not on windows 7. The drive are not getting the red X its the network card which is getting Red X but seem to be happening all over the company, other PC ( Windows 7) are mapping all of the drives its just few PC with this problem. Also I seem on some PC the %logonserver% is not being set that might be reason why the login script is not working.

Hi iamwpj, How do you add driver as stand user. When you install driver you have have admin rights to do that.

Hi, thanks for the post. I think this behaviour is related with the cached credntials logon. then we could try the test below: Please change the cached logon information controlled by the following key. Please change the cached logon information to 0: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon\ ValueName: CachedLogonsCount Data Type: REG_SZ Values: 0 This will enforce the user logon to connect the DC for authentication the password. After that, please check the status of the logon and mapped drives, and let me know the result. Thanks. Best Regards, Annie

Hi, When you change the registry, which result did you get? You can logon the computer but cannot get the drive mapped, all right? When we turn off the cached logon, then the user must send the password and username to the DC for login. If the network is not ready at this time, then it can cause the disconnect of mapping drive. But now, if you can logon and still cannot map drive, this can be the system issue. However, as I checked, you said that you could mapped it by using the command "net use" for that? If so, would you mind restarting the computer under the safe mode with networking to see if that works? Thanks. Annie

Sorry it didn't work. Try it on one of the user who home drive never gets mapped. When user logged in it had no home drive but when I use net use command to map the drive it worked fine.

In event logs this is what i'm see when logging in. Log Name: System Source: Microsoft-Windows-Dhcp-Client Date: 06/09/2012 11:03:20 Event ID: 50037 Task Category: Service State Event Level: Information Keywords: User: LOCAL SERVICE Computer: PCNAME.domain.com Description: DHCPv4 client service is stopped. ShutDown Flag value is 1 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Dhcp-Client" Guid="{15A7A4F8-0072-4EAB-ABAD-F98A4D666AED}" /> <EventID>50037</EventID> <Version>0</Version> <Level>4</Level> <Task>4</Task> <Opcode>69</Opcode> <Keywords>0x2000000000000000</Keywords> <TimeCreated SystemTime="2012-09-06T10:03:20.671417200Z" /> <EventRecordID>41141</EventRecordID> <Correlation /> <Execution ProcessID="308" ThreadID="1296" /> <Channel>System</Channel> <Computer>PCNAME.domain.com</Computer> <Security UserID="S-1-5-19" /> </System> <EventData> <Data Name="DwordVal">1</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Dhcp-Client Date: 06/09/2012 11:04:23 Event ID: 50036 Task Category: Service State Event Level: Information Keywords: User: LOCAL SERVICE Computer: PCNAME.domain.com Description: DHCPv4 client service is started Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Dhcp-Client" Guid="{15A7A4F8-0072-4EAB-ABAD-F98A4D666AED}" /> <EventID>50036</EventID> <Version>0</Version> <Level>4</Level> <Task>4</Task> <Opcode>68</Opcode> <Keywords>0x2000000000000000</Keywords> <TimeCreated SystemTime="2012-09-06T10:04:23.824855100Z" /> <EventRecordID>41205</EventRecordID> <Correlation /> <Execution ProcessID="304" ThreadID="1388" /> <Channel>System</Channel> <Computer>PCNAME.domain.com</Computer> <Security UserID="S-1-5-19" /> </System> <EventData> </EventData> </Event>

We have a similar issue on our Enterprise system. We have found that when a machine has admin rights it tends to lose the networked drives upon restart. However if you add the drives as a standard user then they will be maintained upon restart.gone fishing;you can find me on the internet

I will try this on monday and post the results.

I am working on the same problem. What I have learned so far is: Netlogon errors go away if you change the link speed on the Network Adapter to 100 mb full duplex. (for your environment you may have to try few other speed options until you get one that works) However that doesnt always fix the problem with mapped drives. After installing 3 different hotfixes (I dont have names here, I will update the post on Monday) I get mapped drives now to map each time, but they do randomly show up with disconnected Red X throughout the day. When you click on them they do re-connect. This part seems to be related to Windows 7 sync center trying to synchronize the files from local cache with network and when detecting low network speed it switches to the offline mode which marks the network drives that are on the same server as the redirected My Documents as disconnected network drives.

Hi Annie, One of the PC I have started PC in Safe mode with network. Still no drives were being Mapped. On same PC I have updated all of the network card drivers. check the network connection which is running on full duplex. Still same problem.

Hi Brano Lukic, Please do let me know these hotfix.

Here is what i have used. Try them one by one you may not need all 3 of them and i had to use registry keys as well. kb2459530 kb2551503 kb2663418 Hive HKEY_LOCAL_MACHINE Key path SYSTEM\CurrentControlSet\Control\NetworkProvider Value name RestoreConnection Value type REG_DWORD Value data 0x0 (0) Hive HKEY_LOCAL_MACHINE Key path SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System Value name EnableLinkedConnections Value type REG_DWORD Value data 0x0 (0)

Thank you for the link. I think I'm close to figuring this out now. We have global file path on our servers. the main path we have is domain.com/file-to-path/ but in ad and login script we put the path as domain/file-to-path/ if I change it to this domain.com/file-to-path/ it works fine but when we change to this domain/file-to-path/ it fails. I just reading on wins and dhcp now to see if I can fix this. I keep you lot up to date.

Hi, I want to know if now the issue is that the mapping drive run with script cannot show up when you logon the computer? Even the safe mode or update the hardware of the NIC card cannot help to resolve the issue? This issue only happens with all Windows 7 or just part of them? And, are you still getting the error 5719 when you logon after updating the NIC card? Thanks. Annie

One of the laptop I have update NIC drivers which was working fine, I will monitor it. the other PC we updated nic drivers and started in safe mode but still same problem.

I monitoring PC. What is e1cexpress I never see this or heard of this. I have seen netlogon in event logs but e1cexpress never seen this. Where do I find this. thank you.

I check few PC with they network card settings. Link Speed & Duplex is set auto and I can see the link speed is 1GB. Wait for Link is set to Auto Detect

HI, If you change the NIC card to these two laptop, will you get the different result? I am still considering if the NIC card is not ready for you logon. If we change the NIC cards on the health computer and the bad computer to check the result, we can narrow down if the problem is related with the NIC card or not. Thanks. Best Regards, Annie

In our case "Wait for Link" only works when you set it to "ON" Changing the "Link Speed & Duplex" to "100 mb full duplex" makes the netlogon go away. Just look under Event Viewer - System and you should be able to see "e1kexpress" as a source for the event. It looks like that certain cards have problem with "Auto" settings http://communities.intel.com/thread/23859

http://support.microsoft.com/kb/983620 Did you try the settings in the picture

One of the PC i'm seeing lot of logs which refer to this event. This happen every day when user turns the PC and trys to log in. Log Name: System Source: NETLOGON Date: 12/09/2012 08:01:54 Event ID: 5719 Task Category: None Level: Error Keywords: Classic User: N/A Computer: pc1.domain.com Description: This computer was not able to set up a secure session with a domain controller in domain dmain due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="NETLOGON" /> <EventID Qualifiers="0">5719</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-09-12T07:01:54.000000000Z" /> <EventRecordID>109355</EventRecordID> <Channel>System</Channel> <Computer>pc1.domain.com</Computer> <Security /> </System> <EventData> <Data>domain</Data> <Data>%%1311</Data> <Binary>5E0000C0</Binary> </EventData> </Event>

Hi Brano, Do you know I just change some setting regrading DFS (I think system can't decode the dfs thats why its failing to run login script or map home drive.). I will try this for day or two and If still doesn't work I will try your hotfix. I post my results. Thank you

Hi Annie, We have problem on desktop PC. I have updated some PC NIC drivers and now they working fine but few PC still causing same issues even they are brand new PC and old PC has same problem.

You are probably facing the same problem then. System is booting to fast, "always wait for network doesn't seem to work" check your event viewer, look for NETLOGON and e1cexpress See which comes first. If netlogon is first then you are trying to resolve the name before the network is ready, and then windows will wait for 45 sec (i think) before attempting to resolve it again. if e1cexpress is first then network is ready but you are having DNS (name resolution) problems.