Hi,
unfortunately Corona does not have nearly as sophisticated DR as Vray at this point in time. Improvements are planned of course, but these things are really hard to polish, because 90% of the problems with DR users have are either connected to 3ds Max, or network setup. Vray has already advanced mechanisms to work around them, like for example recently introduced automatic distribution of maps, where if there are some maps missing on slaves, Vray will send them from workstation on it's own.
Currently, most reliable way to use DR with Corona is to have all the shared assets, like texture, references, etc... on one remote drive that is accessible under same drive letter from all the machines. This requires high speed LAN connection though.
Basically you have all the assets scene uses stored on a network drive labeled Z: for example. So path from workstation to the file is for example Z:\Assets\Textures\Wood\Old\OldWoodPlanks_L_01.jpg
All the slave machines have then same network drive mapped as same letter. So once scene is transferred to slaves, they have exact same path to the texture - Z:\Assets\Textures\Wood\Old\OldWoodPlanks_L_01.jpg
If you already use this setup, and still have these problems, then the bug will be a lot harder to chase, because 3ds Max has many weird ways it works with paths. I would especially avoid the whole UNC thing.
