Any ideas why pcAnywhere breaks VB.NET remote debugging?

[Bihari Srinivasan]

I am using two PCs, say PC-1 and PC-2 in a networked environment (TCP/IP).
Both
of these run Windows 2000. PC-1 is a development platform and PC-2 is
a remote debug platform.

I have a very simply console application written in VB.NET that is built on
PC-1 using
VisualStudio.NE T. I set the VisualStudio.NE T debugging environment to
execute the application on PC-2. This works as long as pcAnywhere is NOT
installed on PC-2 (it does not matter whether or not I have pcAnywhere
installed on PC-1).

If I install pcAnywhere on PC-2 but don't reboot the PC when prompted at the
end of the pcAnywhere installation, the remote debugging continues to work.
However, as soon as I reboot, the remote debugging will not work. On PC-1
(where the debugger is running) I get a dialog box that indicates that the
debugger was unable to start the program. At this point, if I uninstall
pcAnywhere from PC-2 and reboot, the remote debugging works.

This seems to indicate that whatever pcAnywhere is installing or whatever
environment it is setting/changing interferes with whatever VisualStudio.NE T
uses for remote debugging.

I have verfiied the settings for the Remote Debug Manager before and after
pcAnywhere was installed. They don't seem to indicate any problem. I have
compared
the registry before and after installation, and the differences are too
numerous to even
consider looking at :-(

This is really getting in the way. Is there a fix? I am using
PCAnyWhere10.5.

Thanks.

Bihari

[Jim Gregoric]

Hello Bihari! This is your pal Jim G, formerly of Datamedic. Sorry I don't have an answer to your question, only a suggestion. Could you simply side-step the problem by using an alternative to pcAnywhere such as XP's Remote Desktop or even Webex?