I've set up a DFS namespace using a CIFS URL, and I initially expected all file access to route through the DFS node. However, I found that if I open a file via that namespace from a remote Windows system and subsequently shut down the DFS server, I can still write to the file and confirm that the changes are saved on the backend hosting the CIFS share. This suggests the I/O operations aren't going through the DFS node at all. Is there a way to ensure all file accesses and I/O operations do go through the DFS node, or is CIFS limited to acting merely as a redirector?
1 Answer
Yeah, that's pretty much how DFS works. It uses referral UNC paths to point clients to the actual file locations. So when you access a file, your client gets directed to the backend directly, which is why it continues to work even after shutting down the DFS node.
Totally agree! It's like a smart DNS for file access.