nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Component react.community-search had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.

Change in CIFS functionality since upgrade to ONTAP 9.1

andyberry

We upgraded our 2 Clusters from ONTAP 8.3.2 to 9.1

Since upgrading we have noticed a change when trying to access a CIFS share when the user connecting is logged onto a different AD domain to the SVM.

The end user no longer get challenged for a user ID and password. Instead because the user ID is the same it tries to use the users credentials including password to connect and after a while the end user gets the following errors

System error 64 has occurred.

The specified network name is no longer available.

If the end user keeps trying to access it, their account on the AD domain that the SVM is on will become locked.

However if they specify their credentials including password from the command line, i.e. net use \\CIFS_SVM\share_name /user:{user_id} {password}

then it works and they can then access the share. They can also do this from the GUI and it also works.

so we have a workaround, but just wondered why the difference between 8.3.2 and 9.1 is it a bug or intentional?

Find more posts tagged with

CIFS and SMB

Comments

Sahana

Hi,

Refer KB https://kb.netapp.com/support/s/article/ka11A0000000s6A/clients-cannot-access-the-filer-anymore-after-migrating-from-one-trusted-domain-to-another-error-64

andyberry

Hi Sahana,

Even though I have licensed support with Netapp I don't seem to have access to that article.

Sahana

Hi,

You need a customer login account to access it. If you do not have one, you can register and create an account.

andyberry

I do have an account but it tells me I don't have access to the knowledgebase.

liu

If you look at that The specified network name is no longer available.

Please check out this link Unable to access CIFS share with error: The specified network name is no longer available - NetApp Knowledge Base

Password in "net use" syntax is entered after the username.

Mapping a drive using "net use" fails with error "System error 67 has occurred" - NetApp Knowledge Base