I have a system where the remote transport is acting strangely... The 'transfer runtime files' is working fine, however the 'start / stop' runtime doesnt appear to do anything on the cleint (Although no error is logged on the server). If I manually launch the runtime on the client it works ok.

Are there any other settings to be aware of? I assume everythings happen over the 1101 (default) port so if the files are transfered it cannot be an issue of firewalls etc.

Client machine is using a different user account (non-administrator) so is it possible that somehow the runtime is being started under the wrong user context or in a different session ID? Is there any way to define which user context is used to lauch the runtime?

I'm not currently in front of the system which has the issue, however will investigate further (check logs etc) when I can next attend site.