1) Use the CREATEFILE this API function, the application submits a request to the local operating system, requiring to open //myserver/myshare/sample.mp3.2) According to the information obtained from the UNC path description, the local (native) operating system The file system determines that the destination of the I / O (input / output) request is a remote machine, named // myServer, so pass this request to MUP. 3) MUP investigates the I / O request is sent by an MSNP provider because the online // MyServer machine is using the NetBIOS name parsing mechanism. 4) I / O request is then passed to the redirector of the MSNP provider. 5) The redirector formats this request into an SMB message, requiring the Sample.mp3 file contained in the remote / myshare directory. 6) The formatted SMB message is finally sent to the network through a network transfer protocol. 7) The server named // myServer receives this SMB request from the Internet and transmits the request to the server's MSNP redirector server service. 8) The server's redirector service submits a local I / O request, I hope to open the sample.mp3 file at the / MyShare this shared location. 9) The server's redirector service formats a SMB response message indicating that the I / O request of the local open file is success or fail. 10) This SMB response message of the server returns the client through a network transfer protocol. 11) The MSNP redirector receives this SMP response message of the server and passes a return code to the native operating system. 12) Native operating system returns the code to the CreateFile API request for the original application.
