Remote debugging

Hi,
I want to debug from my notebook (XP Pro) as host to target (WinXPE) with MS
VS 6.0, so use it only as a client, not a server.
I've connected them directly throuhg ethernet and I can ping correctly XP
Pro to Embedded, and Embedded to Pro too.
I've done all what required in the MSDN for remote debugging:
- srarted the MSVCMON.exe with the proper notebook IP connection settings
- In the MS VS, I've done remote debugging with the proper target IP
settings and made the settings to the project: shared the exe folder, etc.

When I tried to start debug from the notebook host, I indeed saw the
"Connecting..." window disappear for a while but my host could not connect
and yielded error for the connection. Is there something I do wrong? Maybe
component missing in target?

Help will be appreciated.

Yoav

Yoav,

Just wondering if you included all the components mentioned in this article?
http://msdn2.microsoft.com/en-us/library/aa459140.aspx

Also, if you run the MSVCMON through DependencyWalker Profiler (Profile
menu) you may be able to see what's missing on the client side.

Regards,
KM

> Hi,
> I want to debug from my notebook (XP Pro) as host to target (WinXPE) with
> MS
> VS 6.0, so use it only as a client, not a server.
> I've connected them directly throuhg ethernet and I can ping correctly XP
> Pro to Embedded, and Embedded to Pro too.
> I've done all what required in the MSDN for remote debugging:
> - srarted the MSVCMON.exe with the proper notebook IP connection settings
> - In the MS VS, I've done remote debugging with the proper target IP
> settings and made the settings to the project: shared the exe folder, etc.
>
> When I tried to start debug from the notebook host, I indeed saw the
> "Connecting..." window disappear for a while but my host could not connect
> and yielded error for the connection. Is there something I do wrong? Maybe
> component missing in target?
>
> Help will be appreciated.
>
> Yoav

Thanks, KM. The DependencyWalker made the job (although the host notifies a
difference between kernel32.dll files - is it matter?).
One more: This works only when I copy the debugged application from host to
target. I'm trying to make share folder in host but when I try to connect one
to another (they see each other) there is a screen for 'user name' and
'password' to fill-in although I don't have any password login in the target.
How can I overcome this?

Yoav

"KM" wrote:

> Yoav,
>
> Just wondering if you included all the components mentioned in this article?
> http://msdn2.microsoft.com/en-us/library/aa459140.aspx
>
> Also, if you run the MSVCMON through DependencyWalker Profiler (Profile
> menu) you may be able to see what's missing on the client side.
>
> Regards,
> KM
>
> > Hi,
> > I want to debug from my notebook (XP Pro) as host to target (WinXPE) with
> > MS
> > VS 6.0, so use it only as a client, not a server.
> > I've connected them directly throuhg ethernet and I can ping correctly XP
> > Pro to Embedded, and Embedded to Pro too.
> > I've done all what required in the MSDN for remote debugging:
> > - srarted the MSVCMON.exe with the proper notebook IP connection settings
> > - In the MS VS, I've done remote debugging with the proper target IP
> > settings and made the settings to the project: shared the exe folder, etc.
> >
> > When I tried to start debug from the notebook host, I indeed saw the
> > "Connecting..." window disappear for a while but my host could not connect
> > and yielded error for the connection. Is there something I do wrong? Maybe
> > component missing in target?
> >
> > Help will be appreciated.
> >
> > Yoav
>
>
>

Yoav,

I couldn't completely understand your questions below.
But just to bring in another idea. Have you tried using "net use .." command instead? You can provide the right credentials with
that command.

The kernel32 differences. Are you running the same SP on both machines? E.g., XPe SP2 and XP Pro SP2?

--
=========
Regards,
KM

> Thanks, KM. The DependencyWalker made the job (although the host notifies a
> difference between kernel32.dll files - is it matter?).
> One more: This works only when I copy the debugged application from host to
> target. I'm trying to make share folder in host but when I try to connect one
> to another (they see each other) there is a screen for 'user name' and
> 'password' to fill-in although I don't have any password login in the target.
> How can I overcome this?
>
> Yoav
>
> "KM" wrote:
>
>> Yoav,
>>
>> Just wondering if you included all the components mentioned in this article?
>> http://msdn2.microsoft.com/en-us/library/aa459140.aspx
>>
>> Also, if you run the MSVCMON through DependencyWalker Profiler (Profile
>> menu) you may be able to see what's missing on the client side.
>>
>> Regards,
>> KM
>>
>> > Hi,
>> > I want to debug from my notebook (XP Pro) as host to target (WinXPE) with
>> > MS
>> > VS 6.0, so use it only as a client, not a server.
>> > I've connected them directly throuhg ethernet and I can ping correctly XP
>> > Pro to Embedded, and Embedded to Pro too.
>> > I've done all what required in the MSDN for remote debugging:
>> > - srarted the MSVCMON.exe with the proper notebook IP connection settings
>> > - In the MS VS, I've done remote debugging with the proper target IP
>> > settings and made the settings to the project: shared the exe folder, etc.
>> >
>> > When I tried to start debug from the notebook host, I indeed saw the
>> > "Connecting..." window disappear for a while but my host could not connect
>> > and yielded error for the connection. Is there something I do wrong? Maybe
>> > component missing in target?
>> >
>> > Help will be appreciated.
>> >
>> > Yoav
>>
>>
>>

I have everything setup per the article mentioned.

I am using visual studio 2005.

When I execute:
msvcmon.exe -anyuseran error box pops up with:"Invalid command line
argument"When I try mscvmon.exe /? it shows anyuser as an
argument.msvcmon.exe start it up fine, but I get a message on my host
saying:msvcmon.exe does not seem to be running on the target
machine.Ideas?"KM" <konstmor@nospam_yahoo.com> wrote in message
news:%23bq6uI8SHHA.1036@TK2MSFTNGP03.phx.gbl...
> Yoav,
>
> I couldn't completely understand your questions below.
> But just to bring in another idea. Have you tried using "net use .."
> command instead? You can provide the right credentials with that command.
>
> The kernel32 differences. Are you running the same SP on both machines?
> E.g., XPe SP2 and XP Pro SP2?
>
> --
> =========
> Regards,
> KM
>
>> Thanks, KM. The DependencyWalker made the job (although the host notifies
>> a
>> difference between kernel32.dll files - is it matter?).
>> One more: This works only when I copy the debugged application from host
>> to
>> target. I'm trying to make share folder in host but when I try to connect
>> one
>> to another (they see each other) there is a screen for 'user name' and
>> 'password' to fill-in although I don't have any password login in the
>> target.
>> How can I overcome this?
>>
>> Yoav
>>
>> "KM" wrote:
>>
>>> Yoav,
>>>
>>> Just wondering if you included all the components mentioned in this
>>> article?
>>> http://msdn2.microsoft.com/en-us/library/aa459140.aspx
>>>
>>> Also, if you run the MSVCMON through DependencyWalker Profiler (Profile
>>> menu) you may be able to see what's missing on the client side.
>>>
>>> Regards,
>>> KM
>>>
>>> > Hi,
>>> > I want to debug from my notebook (XP Pro) as host to target (WinXPE)
>>> > with
>>> > MS
>>> > VS 6.0, so use it only as a client, not a server.
>>> > I've connected them directly throuhg ethernet and I can ping correctly
>>> > XP
>>> > Pro to Embedded, and Embedded to Pro too.
>>> > I've done all what required in the MSDN for remote debugging:
>>> > - srarted the MSVCMON.exe with the proper notebook IP connection
>>> > settings
>>> > - In the MS VS, I've done remote debugging with the proper target IP
>>> > settings and made the settings to the project: shared the exe folder,
>>> > etc.
>>> >
>>> > When I tried to start debug from the notebook host, I indeed saw the
>>> > "Connecting..." window disappear for a while but my host could not
>>> > connect
>>> > and yielded error for the connection. Is there something I do wrong?
>>> > Maybe
>>> > component missing in target?
>>> >
>>> > Help will be appreciated.
>>> >
>>> > Yoav
>>>
>>>
>>>
>
>

I don't know if you noticed the link was provided to the article describing remote debugging setup using VS6 or .Net.

With VS2005 you've got some steps modified. You may want to follow this:
http://msdn2.microsoft.com/en-us/library/bt727f1t(vs.80).aspx

--
=========
Regards,
KM
>I have everything setup per the article mentioned.
>
> I am using visual studio 2005.
>
> When I execute:
> msvcmon.exe -anyuseran error box pops up with:"Invalid command line argument"When I try mscvmon.exe /? it shows anyuser as an
> argument.msvcmon.exe start it up fine, but I get a message on my host saying:msvcmon.exe does not seem to be running on the target
> machine.Ideas?"KM" <konstmor@nospam_yahoo.com> wrote in message news:%23bq6uI8SHHA.1036@TK2MSFTNGP03.phx.gbl...
>> Yoav,
>>
>> I couldn't completely understand your questions below.
>> But just to bring in another idea. Have you tried using "net use .." command instead? You can provide the right credentials with
>> that command.
>>
>> The kernel32 differences. Are you running the same SP on both machines? E.g., XPe SP2 and XP Pro SP2?
>>
>> --
>> =========
>> Regards,
>> KM
>>
>>> Thanks, KM. The DependencyWalker made the job (although the host notifies a
>>> difference between kernel32.dll files - is it matter?).
>>> One more: This works only when I copy the debugged application from host to
>>> target. I'm trying to make share folder in host but when I try to connect one
>>> to another (they see each other) there is a screen for 'user name' and
>>> 'password' to fill-in although I don't have any password login in the target.
>>> How can I overcome this?
>>>
>>> Yoav
>>>
>>> "KM" wrote:
>>>
>>>> Yoav,
>>>>
>>>> Just wondering if you included all the components mentioned in this article?
>>>> http://msdn2.microsoft.com/en-us/library/aa459140.aspx
>>>>
>>>> Also, if you run the MSVCMON through DependencyWalker Profiler (Profile
>>>> menu) you may be able to see what's missing on the client side.
>>>>
>>>> Regards,
>>>> KM
>>>>
>>>> > Hi,
>>>> > I want to debug from my notebook (XP Pro) as host to target (WinXPE) with
>>>> > MS
>>>> > VS 6.0, so use it only as a client, not a server.
>>>> > I've connected them directly throuhg ethernet and I can ping correctly XP
>>>> > Pro to Embedded, and Embedded to Pro too.
>>>> > I've done all what required in the MSDN for remote debugging:
>>>> > - srarted the MSVCMON.exe with the proper notebook IP connection settings
>>>> > - In the MS VS, I've done remote debugging with the proper target IP
>>>> > settings and made the settings to the project: shared the exe folder, etc.
>>>> >
>>>> > When I tried to start debug from the notebook host, I indeed saw the
>>>> > "Connecting..." window disappear for a while but my host could not connect
>>>> > and yielded error for the connection. Is there something I do wrong? Maybe
>>>> > component missing in target?
>>>> >
>>>> > Help will be appreciated.
>>>> >
>>>> > Yoav
>>>>
>>>>
>>>>
>>
>>
>
>

Thanks for the link.

Still gettting the same response.

I disabled the firewall on the host and remote machine.

I noticed there is a process svchost.exe listening on port 135 all the time,
even if i don't have msvsmon.exe installed

I can ping the system and telnet can open port 135 on the remote machine
from the host machine.

Any ideas?

"KM" <konstmor@nospam_yahoo.com> wrote in message
news:%23zLf7kHgHHA.1216@TK2MSFTNGP03.phx.gbl...
>I don't know if you noticed the link was provided to the article describing
>remote debugging setup using VS6 or .Net.
>
> With VS2005 you've got some steps modified. You may want to follow this:
> http://msdn2.microsoft.com/en-us/library/bt727f1t(vs.80).aspx
>
> --
> =========
> Regards,
> KM
>>I have everything setup per the article mentioned.
>>
>> I am using visual studio 2005.
>>
>> When I execute:
>> msvcmon.exe -anyuseran error box pops up with:"Invalid command line
>> argument"When I try mscvmon.exe /? it shows anyuser as an
>> argument.msvcmon.exe start it up fine, but I get a message on my host
>> saying:msvcmon.exe does not seem to be running on the target
>> machine.Ideas?"KM" <konstmor@nospam_yahoo.com> wrote in message
>> news:%23bq6uI8SHHA.1036@TK2MSFTNGP03.phx.gbl...
>>> Yoav,
>>>
>>> I couldn't completely understand your questions below.
>>> But just to bring in another idea. Have you tried using "net use .."
>>> command instead? You can provide the right credentials with that
>>> command.
>>>
>>> The kernel32 differences. Are you running the same SP on both machines?
>>> E.g., XPe SP2 and XP Pro SP2?
>>>
>>> --
>>> =========
>>> Regards,
>>> KM
>>>
>>>> Thanks, KM. The DependencyWalker made the job (although the host
>>>> notifies a
>>>> difference between kernel32.dll files - is it matter?).
>>>> One more: This works only when I copy the debugged application from
>>>> host to
>>>> target. I'm trying to make share folder in host but when I try to
>>>> connect one
>>>> to another (they see each other) there is a screen for 'user name' and
>>>> 'password' to fill-in although I don't have any password login in the
>>>> target.
>>>> How can I overcome this?
>>>>
>>>> Yoav
>>>>
>>>> "KM" wrote:
>>>>
>>>>> Yoav,
>>>>>
>>>>> Just wondering if you included all the components mentioned in this
>>>>> article?
>>>>> http://msdn2.microsoft.com/en-us/library/aa459140.aspx
>>>>>
>>>>> Also, if you run the MSVCMON through DependencyWalker Profiler
>>>>> (Profile
>>>>> menu) you may be able to see what's missing on the client side.
>>>>>
>>>>> Regards,
>>>>> KM
>>>>>
>>>>> > Hi,
>>>>> > I want to debug from my notebook (XP Pro) as host to target (WinXPE)
>>>>> > with
>>>>> > MS
>>>>> > VS 6.0, so use it only as a client, not a server.
>>>>> > I've connected them directly throuhg ethernet and I can ping
>>>>> > correctly XP
>>>>> > Pro to Embedded, and Embedded to Pro too.
>>>>> > I've done all what required in the MSDN for remote debugging:
>>>>> > - srarted the MSVCMON.exe with the proper notebook IP connection
>>>>> > settings
>>>>> > - In the MS VS, I've done remote debugging with the proper target IP
>>>>> > settings and made the settings to the project: shared the exe
>>>>> > folder, etc.
>>>>> >
>>>>> > When I tried to start debug from the notebook host, I indeed saw the
>>>>> > "Connecting..." window disappear for a while but my host could not
>>>>> > connect
>>>>> > and yielded error for the connection. Is there something I do wrong?
>>>>> > Maybe
>>>>> > component missing in target?
>>>>> >
>>>>> > Help will be appreciated.
>>>>> >
>>>>> > Yoav
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
>>
>
>

DCOM RPC is sitting on port 135.

You may want to check the steps from this article: http://support.microsoft.com/kb/908099

--
=========
Regards,
KM

> Thanks for the link.
>
> Still gettting the same response.
>
> I disabled the firewall on the host and remote machine.
>
> I noticed there is a process svchost.exe listening on port 135 all the time, even if i don't have msvsmon.exe installed
>
> I can ping the system and telnet can open port 135 on the remote machine from the host machine.
>
> Any ideas?
>
> "KM" <konstmor@nospam_yahoo.com> wrote in message news:%23zLf7kHgHHA.1216@TK2MSFTNGP03.phx.gbl...
>>I don't know if you noticed the link was provided to the article describing remote debugging setup using VS6 or .Net.
>>
>> With VS2005 you've got some steps modified. You may want to follow this:
>> http://msdn2.microsoft.com/en-us/library/bt727f1t(vs.80).aspx
>>
>> --
>> =========
>> Regards,
>> KM
>>>I have everything setup per the article mentioned.
>>>
>>> I am using visual studio 2005.
>>>
>>> When I execute:
>>> msvcmon.exe -anyuseran error box pops up with:"Invalid command line argument"When I try mscvmon.exe /? it shows anyuser as an
>>> argument.msvcmon.exe start it up fine, but I get a message on my host saying:msvcmon.exe does not seem to be running on the
>>> target machine.Ideas?"KM" <konstmor@nospam_yahoo.com> wrote in message news:%23bq6uI8SHHA.1036@TK2MSFTNGP03.phx.gbl...
>>>> Yoav,
>>>>
>>>> I couldn't completely understand your questions below.
>>>> But just to bring in another idea. Have you tried using "net use .." command instead? You can provide the right credentials
>>>> with that command.
>>>>
>>>> The kernel32 differences. Are you running the same SP on both machines? E.g., XPe SP2 and XP Pro SP2?
>>>>
>>>> --
>>>> =========
>>>> Regards,
>>>> KM
>>>>
>>>>> Thanks, KM. The DependencyWalker made the job (although the host notifies a
>>>>> difference between kernel32.dll files - is it matter?).
>>>>> One more: This works only when I copy the debugged application from host to
>>>>> target. I'm trying to make share folder in host but when I try to connect one
>>>>> to another (they see each other) there is a screen for 'user name' and
>>>>> 'password' to fill-in although I don't have any password login in the target.
>>>>> How can I overcome this?
>>>>>
>>>>> Yoav
>>>>>
>>>>> "KM" wrote:
>>>>>
>>>>>> Yoav,
>>>>>>
>>>>>> Just wondering if you included all the components mentioned in this article?
>>>>>> http://msdn2.microsoft.com/en-us/library/aa459140.aspx
>>>>>>
>>>>>> Also, if you run the MSVCMON through DependencyWalker Profiler (Profile
>>>>>> menu) you may be able to see what's missing on the client side.
>>>>>>
>>>>>> Regards,
>>>>>> KM
>>>>>>
>>>>>> > Hi,
>>>>>> > I want to debug from my notebook (XP Pro) as host to target (WinXPE) with
>>>>>> > MS
>>>>>> > VS 6.0, so use it only as a client, not a server.
>>>>>> > I've connected them directly throuhg ethernet and I can ping correctly XP
>>>>>> > Pro to Embedded, and Embedded to Pro too.
>>>>>> > I've done all what required in the MSDN for remote debugging:
>>>>>> > - srarted the MSVCMON.exe with the proper notebook IP connection settings
>>>>>> > - In the MS VS, I've done remote debugging with the proper target IP
>>>>>> > settings and made the settings to the project: shared the exe folder, etc.
>>>>>> >
>>>>>> > When I tried to start debug from the notebook host, I indeed saw the
>>>>>> > "Connecting..." window disappear for a while but my host could not connect
>>>>>> > and yielded error for the connection. Is there something I do wrong? Maybe
>>>>>> > component missing in target?
>>>>>> >
>>>>>> > Help will be appreciated.
>>>>>> >
>>>>>> > Yoav
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>