AppDomain for loading plugins changing when writing to network??

Question

I wrote a plugin loader that sets up a new AppDomain and loads the plugins from a directory inside the main application folder. The plugins write out various types of files to a given directory when requested.

Everything seems to be working fine, but when some users try and write to a valid network path, we're seeing errors in loading the plugins. It appears the domain is trying to load the plugin from the network path (tacking on the plugin folder to the path), so of course it can't find the dlls.

I'm setting up the plugin domain to have a BaseDirectory of the executable's folder, and then setting the PrivateBinPath to the plugin directory.

Is there some way that writing to the network overrides whatever domain context I have created???