General Discussion

Highlighted

When accessing the network path with CIFS Server's hostname then by-default NFS exports are listed.

When accessing the network path with CIFS Server's hostname then by-default NFS exports are listed.

When accessing the network path with CIFS Server's IP then by-default CIFS shares are listed.

Why CIFS server is not opening  CIFS shares when accessed with hostname?
Why different behaviour when accessing with hostname and IP?

 

This issue occurs on ONTAP simulator v. 9.7.
With Cluster mode NetApp v.9.3 we are are getting same behavior when accessing CIFS server with both hostname and IP.


Host file entry is done like this:
10.***.**.*** CIFSNFSBOTH_FP.domain CIFSNFSBOTH_FP

Network provider order has NFS in last position.

 

How to resolve this and get same behavior when accessing CIFS Server with both hostname and IP?
Please check attached images for more details.

2 REPLIES 2
Highlighted

Re: When accessing the network path with CIFS Server's hostname then by-default NFS exports are list

Hi

 

Just to make sure it's clear. You are happy for the NFS exports to be shown?

 

As for the problem accessing by hostname.

Can you check the delegation exsits with the windows setspn tool? (setspn.exe -L AD_Object_Name). and that the name shown in the ONTAP command "vserver cifs show -display-netbios-aliases"

 

Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK
Highlighted

Re: When accessing the network path with CIFS Server's hostname then by-default NFS exports are list

Hello Gidon,

 

Thanks for reply.

We just want that what gets listed when we access hostname over the network must be controlled by "Network Provider Order".
In our setup we have "Microsoft Windows Network" at top and "NFS Network" at bottom. Image attached.
So when we access the SVM with its CIFS Server's hostname over the network then we expect CIFS Shares to be listed and not NFS exports.

With IP we get CIFS shares list and with CIFS server's hostname we get NFS exports, this is not an expected behavior.
We want same behavior when accessed using IP and hostname.

 

Below are the results of commands you mentioned:

1.

>> setspn.exe -L CIFSNFSBOTH_FP
Registered ServicePrincipalNames for CN=CIFSNFSBOTH_FP,CN=Computers,DC=***,DC=*****:
HOST/cifsnfsboth_fp.***.*****
HOST/CIFSNFSBOTH_FP

 

2.
Netapp-FabricPool::> vserver cifs show -display-netbios-aliases -vserver cifsnfsboth_fp

Vserver: cifsnfsboth_fp

Server Name: CIFSNFSBOTH_FP
NetBIOS Aliases: -

NetApp Insights To Action
All Community Forums