It??™s possible
to overcome this particular error by including the required credentials as part of the RPCPing call. In
real-world testing, it??™s easy to forget that Server Core locks down just about everything so tightly that
running even simple tests is nearly impossible. For example, it??™s unlikely that you??™d see this error information
when working with Windows 2000 as long as you have an administrator account.
CHECKING CONNECTIONS USING RPC WITH THE RPCPING UTILITY 313
SChannel 14
Kerberos 16
-a authn_level Determines the authentication level that RPCPing uses to make the calls during
the test. You must provide the ??“u command line option when using this option. RPCPing doesn??™t
provide a default value for this option. You can use any of the following authentication levels.
? connect
? call
? pkt (packet)
? integrity
? privacy
-N server_princ_name Defines the server principal name. You use the same arguments as
you would when using the RpcBindingSetAuthInfoEx() function (see http://
msdn.microsoft.com/library/en-us/rpc/rpc/rpcbindingsetauthinfoex.asp for details
on this function). You can only use this option when you also specify the ??“a and ??“u options.
Pages:
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757