It's probably bad security, (but if you're inside a LAN or connecting via VPN or SSH it likely doesn't matter) but have you tried going to the options dialog (inside remote debugger stub) and tick allow any user to debug?
On 8 August 2010 20:02, Michael Lyons <maill...@ittworx.com> wrote: > I'm needing to debug a Windows service to see why it is crashing after a > few > minutes. > I've setup the remote debugger on the host machine, but I receive the error > message "Unable to connect to the Microsoft Visual Studio Remote Debugging > Monitor named 'x'. Logon Failure: unknown username or bad password". > The issue is that my workstation is within a AD domain whilst the machine I > wish to debug is not. How can I go about debugging the remote machine > without disconnecting from the domain or connecting the remote machine to > the domain? > > The service has also for some reason or another stopped outputting to via > System.Diagnostics.EventLogTraceListener, would anyone have any clue why > this would happen? > > ------------- > Michael Lyons > > -- Meski "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills