asked on

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.

robocat

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

scott_aberle

ASKER

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.

robocat

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.)

scott_aberle

ASKER

Yes, I can ping.

The time on the filer and domain match.

scott_aberle

ASKER

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?

EddyJackson

Go to FilerView > Filer > Set Date/Time

scott_aberle

ASKER

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?

EddyJackson

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).

ASKER CERTIFIED SOLUTION

EddyJackson

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial