That is to be set only if you're using a proxy, otherwise don't mess with it. You said you're not using a proxy, so other than checking the domain restrictions on the computers in your test lab, I really don't know what to tell you. Have you tried running the app as a privileged user in the test lab, like some domain admin or the local computer admin? Even with such elevated permissions, the local or domain security policy might be disallowing certain things that are necessary. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

Well, I've solved this problem. The remoting object was passed by-reference, but the remoting object was a collection of benchmark tests. The tests themselves were marked serializable, so they were run locally. Changing the tests to derive from MarshalByRefObject solved the problem. --Dacris

Oops..ok i'll fix that. download again in about 5 minutes. sorry