Cause: You cannot access DFS junctions if you login to the desktop as Active Directory user and map the CIFS drive as eDirectory user.
Action: To access DFS junctions, it is recommended to map the CIFS drive with the same Active Directory user credentials as you login in the Windows workstation.
Cause: Junction target has changed, but the Windows client is still pointing to the old target as it caches junction target information.
Action: To refresh the Windows environment, do the following:
Restart the Windows client.
or
Download the DFSUTIL utility from the Microsoft download site.
Disconnect from the mapped drive and clear the cache using the following DFSUTIL commands:
DFSUTIL /PKTFLUSH DFSUTIL /SPCFLUSH
Remap the drive.
Cause: The Windows client is not able to resolve the target OES server's IP address through NetBIOS.
Action: Add an entry with the CIFS server IP address and the NetBIOS name in the HOSTS and LMHOSTS files on the Windows client.
Windows does not prompt the server to resolve the junction every time it is accessed. It prompts the server only the first time and then caches it. When the junction is accessed the next time, Windows does not prompt the CIFS server to resolve the junction; instead it uses the target location that it received previously.
On a restart of the Windows machine, if the same mapping is used, it points to the correct location. Because there is no cached value, it prompts the CIFS server to provide the location of the target that the junction points to and retrieves the latest value from the CIFS server.