C:\Users\user\Downloads\NetApp\SDK\netapp-manageability-sdk-5.4\bin\nt>.\apitest.exe -r mynew8060 system-get-version <results reason="RPC Error - The RPC server is unavailable. " errno="13011" status="failed"/>
In SDK --> "Session Management APIs" --> na_server_style we have this:
If style=NA_STYLE_RPC, your code should run on the Windows system so that a native Windows authentication based on remote procedure call is used. This is applicable for Data ONTAP APIs only.
Question: Can someone comment and/or confirm if the cDOT NA_STYPE_RPC auth should work (or does somewhere?!?!?) and if so, how (options, SMB versions, special/new API capabilities, Windows version on the client and AD server, ...)
Thanks a bunch
P.S.: No, we don't have WAN optimization in that environment 😉
Well, strong indicator that it is not working, confirmed, but it's the APITEST docu only 😉 So in theory it could be that only the tool doesn't support it, right 😮
Could someone then send a statement how the same passwordless authentication can be done for both 7Mode and cDOT APIs? Because, you for sure understand, we talk "chicken/egg" here.. I can only know if the Netapp is 7Mode or cDOT AFTER I connected to it... and I cannot (passwordless) connect to check this because I don't know if WinRPC or CERT should work....
That's exaactly what I do... I check with "na_results_errno" for "13011", which is "ERROR (13011): RPC Error - The RPC server is unavailable." and then try to talk to a cDOT again, check result and so on... BUT the tools run much longer now and this is an ugly hack and very error prone!
I think NetApp can and should do better then this (offer the same consistent "passwordless" way!)...