If you are still stuck then I would give windbg a try (see earlier post ' Unable to diagnose a crash') as it may be able to give you enough info to fix the problem
-----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Michael Lyons Sent: Monday, 9 August 2010 9:12 AM To: ozdotnet@ozdotnet.com Subject: RE: Remote debugging outside of domain No luck. Same result. Liked the idea though. I also made sure that the user was in the VS remote debugger permissions and they had debugging permissions under the local security policies. ------------- Michael Lyons -----Original Message----- From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Sunday, 8 August 2010 9:50 PM To: Michael Lyons Subject: RE: Remote debugging outside of domain One option to try: Connect to shared folder on the remote machine first (e.g. c$ admin share) using Explorer Then VS. NET might use your established credentials to attempt to connect to the remote debugger service Cheers Ken -----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Michael Lyons Sent: Sunday, 8 August 2010 8:03 PM To: 'ozDotNet' Subject: Remote debugging outside of domain 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
