• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6083
  • Last Modified:

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.
0
scott_aberle
Asked:
scott_aberle
  • 4
  • 3
  • 2
1 Solution
 
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
Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

 
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

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now