none
Users shared network drives have stopped working

    Question

  • Let me begin by saying that I am not qualified to be in this forum. I would say that I am a highly experienced Windows user (thru version 7), but when it comes to networking I am out of my depth.  But I teach basic computer courses at a small school on the border of the Dominican Republic and Haiti and am the best they have to try to maintain their server (originally installed by IT pros).

    The basic network is the following:

     - Server: Windows Server 2012 Standard (Version 6.2.9200)

     - Desktops: Windows 8 Pro 64 (Version 6.2.9200)

    The probable cause of the problem: Electricity here is *mostly* stable but we only have electricity about 14 hours a day and the changeover time is not consistent.  The voltage is not always steady either - sometimes it comes in quite low and sometimes it comes in dangerously (to electronic equipment) high. The result is that we often lose power in the middle of class (at times several times because *mostly* stable means that at times it is not stable).  I have lost 2 power supplies (out of 25) due to this issue.

    The server, even with a UPS, has regular hard power offs due to power outages when no one is able to get to the lab quick enough to power it down or to get the generator powered on.  I am reasonably sure that one of the more recent dirty shutdowns has cause the problem.

    The problem: all of the shared networks drives are "broken".

    I realize that not all of this will be helpful, but better too much than too little information. Here is what I can tell you with my limited knowledge:

    - The shares are being done thru Group Policy.

    - There is no login script being utilized for users.

    - The home folder in Group Policy is \\ server-01\students\8\%username% and it is being assigned as drive "S" for each student. (space after the \\ to prevent this forum from preventing my post because it thinks I am posting a link)

    - The physical path to the shared "students" in the line above is E:\shares\users\students.

    - On booting any of the desktops with the server already booted, there is a long delay before Windows finally loads. It is clearly timing out on attempting to login to the server and pull the roaming profile.  The end result is that users are being assigned temporary profiles.

    - Remote desktop into the server does not function

    - If I login *on* the server console itself, the shared network drive "S" DOES get assigned correctly.

    - Profile are stored in E:\shares\profiles

    - I have browsed Event Viewer and have seen only two errors.  One is due to a backup driver being normally powered down while the backup service is always initialized on boot.  The other was DFSR Event 2213 due to a dirty shutdown.  This error has been resolved. There are a few warnings, but nothing that seems on point for this issue.

    - In Event Viewer, I do see Event ID 1003 - Start processing GPOs.  But since the "S" drive is assigned when booting from the system console, we knew that the GPOs are getting processed.

    I am hoping that there is a very simple resolution to this issue and that one of you kind folks can give me instructions on how to do it, or guide me to helping you find additional information on the issue.

    Many thanks.

    Wednesday, October 21, 2015 7:13 PM

All replies

  • Hi Tom Brock,

    Thanks for your post.

    I think this issue might be related corrupted\locked files or related regsitry entries or internet connection which prevent the load of the roaming profile. So that users are being assigned temporary profiles. And finally it leads to opening network share drives failure. I suggest you check log in event viewer in both the client side and the server side.

    Is there any other events in the server? According to the error you mentioned, it seems not to be an AD Authentication problem. And could you please test that if client could access to the file \\ server-01\students\8\%username% and test client could access to other share folder in other clients.

    Best Regards,

    Mary Dong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Tom Brock Thursday, October 22, 2015 5:18 PM
    • Unmarked as answer by Tom Brock Tuesday, November 03, 2015 1:08 AM
    Thursday, October 22, 2015 8:55 AM
    Moderator
  • What does the Application event logs say for a user logging into their workstation? The reason for the delay will be logged.

    You should configure your UPS to shut down the servers for you upon the event of powerloss. If the UPS cannot maintain enough charge to perform this task, consider checking the health of the UPS batteries.

    • Marked as answer by Tom Brock Thursday, October 22, 2015 5:18 PM
    • Unmarked as answer by Tom Brock Tuesday, November 03, 2015 1:08 AM
    Thursday, October 22, 2015 10:33 AM
  • Thanks to you both.  Knowing that the Group Policy without error on the server console, I should have thought to check the events on the client. Now that I have done so, I see that it is throwing two errors:

    Netlogon Event ID 5719:
    This computer was not able to set up a secure session with a domain controller in domain SanPatricio due to the following: There are currently no logon servers available to service the logon request.

    Group Policy Event ID 1129:
    The processing of Group Policy failed because of lack of network connectivity to a domain controller.

    I verified that the all hardware is powered up and all patch cables etc are in place. The switch is the Cisco GS200-50 and I hit its reset switch followed by a server reboot.  No change.

    These errors have wondering if we are dealing with a hardware issue due to the dirty shutdowns? Any more that I can/should check?

    Edited to add: Still thinking that the issue is the Cisco switch...

    Main server: 192.168.1.200
    Switch: 192.168.1.1

    Ping .200 = Success
    Ping .1 = Reply from .200: Destination host unreachable

    Also the green "System" LED on the switch (Cisco GS200-50) is continually blinking.  Meanwhile none of the traffic/speed LED's are lit.  Guessing the switch, is damaged.  (sigh)


    • Edited by Tom Brock Wednesday, October 28, 2015 7:42 PM
    Thursday, October 22, 2015 5:27 PM