Solved

Windows File Shares not accessible after DC Reboot

Posted on 2014-01-22
6
67 Views
Last Modified: 2016-05-20
I have a four DC Windows 2003 Server Environment.  One of my DC's ran out of virtual memory and needed to be rebooted.  It took three reboots before the there were no errors and all services started.  During this time, none of my windows file shares that are presented off of my Storage array are accessible by anyone who reboots and re-authenticates.  All of my DHCP reserved IP addresses including Servers, Clients, Printers, and other devices are accessible on login as is all browsing and email access.  

I have reviewed all of my DC's and they are all clear of errors for over an hour in Eventvwr, but my clients are unable to access these file shares.  The storage unit you can ping and perform forward/reverse DNS lookups through NSLOOKUP.  Response is 1ms or 2ms so very typical performance.  My ERP is IP based and my users are having no issues connecting to the system.

I am stumped, I don't know where to look or think.  I cannot join and remove 200+ client PC's to the domain so this is not an option as 50% of my environment are remote using VPN based connections.

I hope someone has information on how to resolve.
0
Comment
Question by:MSodolak
  • 2
  • 2
6 Comments
 
LVL 7

Expert Comment

by:Ned Ramsay
ID: 39801659
Do you use Distributed File Systems (DFS) windows shares?
0
 

Author Comment

by:MSodolak
ID: 39801674
No - Running CIFS Shares off of a NetApp Filer.

Been doing this for 3+ years and had the DC go down once or twice, but this has never happened.
0
 
LVL 7

Expert Comment

by:Ned Ramsay
ID: 39801716
Have you tried rebooting a different DC and seeing if it does this too? Could credentials have changed that authenticate your users against the netapp?

Im kinda clutching at straws here, my initial thought was something to do with the FSMO roles on your DCs. But that seems unlikely.
0
 
LVL 21

Expert Comment

by:robocat
ID: 39802288
Did you look for errors in the NetApp system logs?

Things you can also try on the NetApp are:

cifs domaininfo
cifs testdc

Post output here.
0
 

Accepted Solution

by:
MSodolak earned 0 total points
ID: 39803270
Robocat - you were on the right track.  I had to do a CIFS Setup as some of the information (arbitrary) was lost.  Once I ran that the broken segments to LDAP were fixed and the CIFS Shares were immediately available.

The problem was caused by the NVMEM Battery on the Netapp filer running out of power and the failure caused the AD information to drop.  Everything is back online now and I am performing updates to the firmware.
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Occasionally you run into the website or two that will not resolve properly using your own DNS servers.  Some people simply set up global forwarders for their DNS server.  I don’t recommend doing this because it can cause problems resolving addresse…
If, like me, you have a lot of Dell servers in the estate you manage this article should save you a little time. When attempting to login to iDrac on any server I would be presented with two errors. The first reads "Do you want to run this applicati…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question