Hi Carlos and Alexander,
To answer your questions, I am using the FePEST in-built parallelization feature as outlined in the 6.2 manual. I understand it is not necessary to set up a network drive, but this network drive is where we store all of our FEFLOW files so that all computers connected to the network can easily access them. This network drive is the only drive that is backed up, so storing anything on the local drives is not ideal.
Both the slave and the host machine have licensed copies of FEFLOW 6.2 with FePEST utilities all set up.
I can across possibly a related issue when trying to run a file created by another user. When I was trying to run FePEST, it said that the fem file could not be found on the drive. The problem is that the path I set and the path it looks at does not exist. For example, if I point to \\networkdrive\myfile.fem it instead points to \\networkdrive\myfile\myfile.fem when running, which is not a valid path...