Greetings to the group, I'm posting this every where I can think of in
hopes of finding a solution. Here's my scenario:
- Host OS: Windows XP Pro
- Guest OS: Windows 2000 Advanced Server, SP4
Host OS has Visual Studio .NET 2003 Pro installed, guest OS is running IIS
5.0 with an ASP.NET solution that I can successfully open and build from
VS.NET in the host. No firewall running for this exercise, using the
standard VMNet8 DHCP to provide an IP to the guest and NAT is enabled. What
I CANNOT do is debug the solution due to permissions errors. Host and guess
are both running in a workgroup named "DEBUG," with the same id/password
logged into both machines, both IDs with admin privileges. Visual Studio
.NET remote debugging tools are installed on the guest OS with IIS, the id
is a member of the Debugger Users group on the guest, ASPNET_WP.EXE is
running under the system account as defined in the machine.config on the
guest.
Based upon innumerable Google hits and MSDN KB articles' reading I suspect
my problem is with DCOM, but dcomnfg.exe keeps throwing "The parameter is
incorrect" modal dialogue errors whenever I try to do anything to the custom
access permissions for the Machine Debug Manager (MDM.EXE running as a
service) properties.
Any assistance appreciated in advance.
Help!!!
Steven Wilmot - 06 Aug 2005 21:24 GMT
> Greetings to the group, I'm posting this every where I can think of in
> hopes of finding a solution. Here's my scenario:
>
> - Host OS: Windows XP Pro
> - Guest OS: Windows 2000 Advanced Server, SP4
[...]
> Any assistance appreciated in advance.
>
> Help!!!
Have you had a look at the following
http://support.microsoft.com/kb/833977
How to turn on remote debugging in Windows XP with Service Pack 2
also:
http://blogs.msdn.com/mkpark/articles/86872.aspx
The VS7.x(Visual Studio 2002 Visual Studio 2003) Debugger doesn't work.
What can I do?
Steven
bpr1996 - 30 Oct 2005 06:11 GMT
Steven, thanks for digging up the references -- just what I needed, too.
> > Greetings to the group, I'm posting this every where I can think of in
> > hopes of finding a solution. Here's my scenario:
[quoted text clipped - 19 lines]
>
> Steven