There always seems to be a bit of confusion setting up remote
debugging in a cross domain environment. In my current
contract, there is the domain we log into (domain1), and then the
development domain (domain2) which we have control over. Perhaps
not all of these items are required and it is definitely not a
secure method, but if they are set, then it should work.
Domain1
==
LM1 (Local machine)
User1 (your login account)
Domain2
==
RM1 (Remote machine to be debugged)
* On RM1, create local account RM1\User1 Assign to local
administrators group.
* Make sure that Domain2\Administrator has the same password as
LM1\Administrator. Also, neither account should be locked
out.
* Turn off firewalls on both machines (make sure to do in the
windows firewall setting - the service still needs to run)
* Login to RM1 as Domain2\Administrator
* Start (install in necessary) the Remote Debug Monitor (run as
an app, not as a service).
** Tools/Permissions, Add RM1\User1 with Debug permissions.
** Tools/Options, set server name to: RM1\User1@RM1
* On LM1, Visual Studio, Attach to Process, Transport Default,
Qualifier = RM1\User1@RM1. Note that @RM1 can be replaced by
@RM1_IPAddress, however, it's better to add RM1 to the hosts
file.