I have to say it would be really nice if it just worked similar to what you were saying but popped up with an authentication dialog where you could actually logon remotely using the debugging account.
------------- Michael Lyons -----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Wallace Turner Sent: Monday, 9 August 2010 11:52 AM To: 'ozDotNet' Subject: RE: Remote debugging outside of domain Condolences++ <rant> Why do you make it so damn hard to debug a process on a remote machine (listen up Microsoft) As always, I'm sure there is a good reason for everything but this is what would be nice: a) you install remote debugging on remote machine b) you forward port on firewall (optionally) c) enter remote machine name a la SQL connections (myhost.com,5000) and start debugging Yes I know it doesn't work this way. Geez it would be nice tho. No messing around with users, one port only. Security could be controlled per process via the remote debugging frontend on the remote machine (yes that would require some work) -----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Monday, 9 August 2010 11:47 AM To: 'ozDotNet' Subject: RE: Remote debugging outside of domain "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor names 'x'. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. Authentication failed. Please see Help for assistance." Hi Michael, my condolences. I spent many solid hours of suffering one afternoon last year trying every trick I could think of to get around this exact problem ... I failed. I gave up with remote debugging and used windbg on the server machine to attach to the troublesome process and I eventually found the problem (missing resource files). Sorry I can't offer any more than sympathy. Greg
