Okay, here's the deal. .Net has it's own security model. By default, .Net apps running on remote servers are given a limited security context. You're able to go into the .Net configuration and raise the security for a particular server. However, the .Net tool does not allow you to raise the security for a 'hidden' server like .PSF. It won't take the name. The net effect is that if you've got a .Net app or you're a .Net developer and you want to host your project file on the .PSF share, you're screwed. I'd love to see a workaround if anyone has one. Other than that, I think Parallels needs to have a config option to allow me to change the name of the .PSF server to something else. Yes, I could set up a SAMBA connection back to my host (I'm doing that right now) but the .PSF share is more than twice as fast as going through SAMBA, so there's a huge performance hit from doing that. Ok, Parallels, Go Fix.
Well I tried mounting \\.PSF\MyHome to drive H: but .Net is too smart for that. It saw that H: was coming from .PSF If you mean sharing from OSX using Windows File Sharing, well that's SAMBA, and that incurs a huge performance penalty.
No - in the Parallels VM editor there is a User-defined Share option. I may be wrong but I thought that used the same technology as the global share. I didn't see a performance hit when I experimented with it earlier.
Well I see the user defined shares, but that only allows me to set the share name not the server name. So it allows me to create any number of \\.PSF\Whatever shares, but the problem is the .PSF. It doesn't seem to be a legal machine name, so .Net won't let me configure .PSF as a trusted remote server... Really, the only way is to change .PSF to something else. But that may affect other users negatively, so it would be nice if it were a config setting, perhaps something in the PVS file for advanced ppl..
Ok, so I am able to manually disable .Net security and everything works fine. But, when I disable security, it's disabled for the entire machine, meaning some web site has a bad .Net user control, it could take over my machine and not prompt, which isn't a good thing. So it still needs to be fixed, but at least I can hobble along for now..
