NetApp FAS270 CIF shares unavailable

I have a NetApp FAS270, it was working perfectly, and now after a reboot, the CIFS shares are unavailable.

When I try to use UNC to get to the shares \\atlas1\xxx, I get the following error message: "Windows cannot find \\atlas1. Check the spelling and try again..."

I can ping the FAS270 just fine and also can access webui no problem.
scott_aberleAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

robocatCommented:

Use the filerview webui, CIFS section to verify the status of CIFS (is it running?) and the status of your shares.

0
scott_aberleAuthor Commented:
CIFS is started and shares are mounted. I think the issue is related to the filer not accessing the domain properly, but I don't know how to fix it.
--
If I do a cifs domaininfo at the command line, I get the following:

                   Windows 2000
Filer AD Site:            modesto

Not currently connected to any DCs
Preferred Addresses: None
Favored Addresses:
                          192.168.254.1   MODESTODC1       PDCBROKEN
                          192.168.254.2   MODESTODC2       PDCBROKEN
                          192.168.254.5   ZEUS             PDCBROKEN
Other Addresses:
                          192.168.254.126 SCOTTDC1         PDCBROKEN
                          192.168.254.138 COPPERDC1        PDCBROKEN
                          192.168.52.1    FRESNODC1        PDCBROKEN
                          192.168.1.2     TRINITYDC1       PDCBROKEN
                          192.168.53.2    CARSONDC1        PDCBROKEN

Not currently connected to any AD LDAP server
Preferred Addresses: None
Favored Addresses: None
Other Addresses: None
--
And the CLI spits out the following every second:

Fri Mar 26 18:25:13 PST [atlas2: nbt.nbss.socketError:error]: NBT: Cannot connect to server 192.168.254.126 over NBSS socket for port 139. Error 0x40: Host is down.
Fri Mar 26 18:25:13 PST [atlas2: nbt.nbss.socketError:error]: NBT: Cannot connect to server 192.168.254.138 over NBSS socket for port 139. Error 0x40: Host is down.
Fri Mar 26 18:25:13 PST [atlas2: cifs.trace.GSS:error]: AUTH: Unable to acquire filer credentials: (0x96c73a25) Filer and domain time differ by more than 5 minutes.
0
robocatCommented:

Did you verify network connectivity between filer and DC ? (ping, ...)

Next, check that your filer has the accurate time.

(error: Filer and domain time differ by more than 5 minutes.)

0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

scott_aberleAuthor Commented:
Yes, I can ping.

The time on the filer and domain match.
0
scott_aberleAuthor Commented:
Looks like it had to do with the daylight savings time change. If the filer time is one hour earlier than the domain time, then the filer will connect to the domain and the shares are available. Any idea how to reconcile the times?
0
EddyJacksonCommented:
Go to FilerView > Filer > Set Date/Time
0
scott_aberleAuthor Commented:
Yes, I did set the time on the filer to the non-daylight savings time, and the filer it is now authenticating to the domain. However, the time on the filer is one hour different than the time on the domain. Any idea how to reconcile or sync the time, so that the filer is set with the same time as the domain?
0
EddyJacksonCommented:
You probably have the old DST schedule on your NetApp (1st Sunday in April - last Sunday in October).  I suspect the NetApp will probably stop working again this weekend until the time is manually changed to match the domain (an hour forward).
0
EddyJacksonCommented:
Follow these instruction to update your timezone info.
https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb20094
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage

From novice to tech pro — start learning today.