Re: Urgent! Anyone could give me a picture of openafs client for windows architecture?

The Multiple UNC Provider (MUP) queries all of the file system drivers
to find out which one handles requests for "\\AFS".  The SMB redirector
says that it does.  From that point forward all requests for files whose
path begins with "\\AFS" gets sent to the smb redirector.

The rest is roughly correct except that the AFS cache manager does
not download files.  It reads 4K chunks of files as required to satisfy
the incoming requests.

hedgepiggy wrote:
> correct me if I am wrong or miss something...what I understand is:
> 1.when user want to operate on AFS files
> 2.the operation was directed (by who?)to smb redirector
> 3.then the smb redirector passes the request to NetBIOS
> 4.NetBIOS passes it in a smb packet to smb fileserver
> 5.smb filesserver solve the request and talk to cache manager
> 6.if no files in local disk, cache manager use RX protocol to download file
> from remote server
> 7.the downloaded file was passed back to smb fileserver by loopback.
> 
> Is it a general process for a operation? 
> 
> Jeffrey Altman-2 wrote:
>> hedgepiggy wrote:
>>> Thank you Bharat and Jeffrey. Thanks for your explanation.
>>> But there is still another question confused me. You meant that
>>> filesystem
>>> request would be passed by NetBIOS in SMB packet to SMB server. But how
>>> could NetBIOS receive this filesystem request(read/write)?
>>> Does it receive request from I/O Manager? Then how could I/O Manager know
>>> it
>>> should be passed to NetBIOS?
>> Netbios receives the request from the smb redirector (mrxsmb.sys)
>>
>>
>>  
>>
>