Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 944
  • Last Modified:

VS2008 remote debugging cross domain error


I'm trying to do some remote debugging with Visual Studio 2008 from my laptop (Vista 64) to a testing server (Windows Server 2008 32 bit).  My laptop is not a member of any domain as I connect it regularly to my clients networks and have had issues in the past if it's a member of my own domain.  The testing server is a member of my office domain (separate Windows 2008 Small Business Server X64).

I have followed the instructions to install the remote debugging tools on my testing server and this all went successfully.  When I try and debug from my Vista 64 laptop, I get the following error.  My laptop is named Gary-Vista64, hence the domain of the same name being workgroup based.  My username is "gary" and a domain based user with same name and password exists on the domain which the testing server belongs to.  I understand that "Gary-Vista64\Gary" doesn't exist in the active directory used by the test server, but don't know what to do from here.  I really don't want to make my laptop part of the domain.

Any ideas ?

Thanks ... in advance!

Event log information follows (from the testing server event log):

An account failed to log on.

      Security ID:            NULL SID
      Account Name:            -
      Account Domain:            -
      Logon ID:            0x0

Logon Type:                  3

Account For Which Logon Failed:
      Security ID:            NULL SID
      Account Name:            gary
      Account Domain:            Gary-Vista64

Failure Information:
      Failure Reason:            Unknown user name or bad password.
      Status:                  0xc000006d
      Sub Status:            0xc0000064

Process Information:
      Caller Process ID:      0x0
      Caller Process Name:      -

Network Information:
      Workstation Name:      GARY-VISTA64
      Source Network Address:
      Source Port:            50971

Detailed Authentication Information:
      Logon Process:            NtLmSsp
      Authentication Package:      NTLM
      Transited Services:      -
      Package Name (NTLM only):      -
      Key Length:            0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
      - Transited services indicate which intermediate services have participated in this logon request.
      - Package name indicates which sub-protocol was used among the NTLM protocols.
      - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
1 Solution
G-BurgessAuthor Commented:
OK, being as no-one had any better ideas - I went ahead and made my laptop a member of the domain and logged on to my laptop using the domain account, and remote debugging now works.  It's a but of a pain (small I guess) that I now must logon local when out and about at my clients networks, but logon to the domain when I wish to remote debug - it seems to be the only thing that need "real" security.  I generally rely on my user name and password matching, but this also requires the domain to match.

All fixed as far as I am concerned.

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now