Protocol Example This section provides an example of how the W32Time Remote Protocol is used. The client obtains the name of a server via an out-of-band mechanism. The client establishes a binding handle to the server at the well-known endpoint \\PIPE\W32TIME_ALT and performs the authentication checks, as specified in section . The client then invokes the method to query the time service status to check whether the time service provides a time source or a reliable time source. The server receives the W32TimeGetNetlogonServiceBits method invocation. In this example, it is assumed that the server allows clients to synchronize time with it by using NTP, as specified in , but that the server is not a reliable time source. In this case, the server returns the value 0x00000040 (DS_TIMESERV_FLAG) to the client. The client receives the return value 0x00000040 (DS_TIMESERV_FLAG), which informs the client that the server is a time source but not a reliable one.
Protocol Example This section provides an example of how the W32Time Remote Protocol is used. The client obtains the name of a server via an out-of-band mechanism. The client establishes a binding handle to the server at the well-known endpoint \\PIPE\W32TIME_ALT and performs the authentication checks, as specified in section . The client then invokes the method to query the time service status to check whether the time service provides a time source or a reliable time source. The server receives the W32TimeGetNetlogonServiceBits method invocation. In this example, it is assumed that the server allows clients to synchronize time with it by using NTP, as specified in , but that the server is not a reliable time source. In this case, the server returns the value 0x00000040 (DS_TIMESERV_FLAG) to the client. The client receives the return value 0x00000040 (DS_TIMESERV_FLAG), which informs the client that the server is a time source but not a reliable one.