Jeffrey Altman wrote: > Jason Cowart wrote: >> We've traditionally had Widows users mount AFS drives by mapping to a >> drive letter using the Net Use command. Recently we've begun >> experimenting with instead using UNC paths to create a connection in "My >> Network Places." >> >> In testing this a couple of our staff have run into a problem where they >> have to manually refresh Windows explorer to see updates to the AFS >> directory. This only occurs for them when both of the following are true: >> >> * They're using the UNC path to access the directory >> * They're logged into our Windows domain >> >> If they log directly into the local machine, the problem does not >> occur. If they log into the domain, but map the directory to a drive >> letter it doesn't occur. >> >> This is using OpenAFS for Windows 1.5.10. >> >> Any thoughts? > > Sounds like a bug somewhere. This should probably be debugged by > adding some custom logging to the SMB Notification routines and the > AFS Callbacks so that the differences between the various scenarios > can be narrowed in scope. > > Jeffrey Altman
Looks like a bug in Windows. When the none domain account is used
OpenAFS receives:
smb_ReceiveNTTranNotifyChange fidp 0x03833EA8 scp 0x102AB834 file "\Private"
Request for NotifyChange filter 0x17 fid 112 wtree 0
Notify Change File Name
Notify Change Directory Name
Notify Change Attributes
Notify Change Last Write
When the domain account is used, it does not.
If OpenAFS doesn't receive a request for notification, there is nothing
for it to respond to with a notification.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
