Unable for remote debugging after Win XP SP2 installed

Unable for remote debugging after Win XP SP2 installed

Post by Brane Brod » Sun, 12 Sep 2004 22:10:02


After I installed Win XP SP2, I'am unable to get list of available processes
on remote machine. After a period of waiting, I get message: "Unable to
connect to the machine 'MACHINE_NAME'. Not enough storage is available to
complete the operation."

My developing machine is WinXP Pro with SP2 and debugging machine is Win2000
Server with SP3 installed. I had no problems with remote debugging before I
installed XP SP2 on my developing machine.

I've already tried some solutions discussed in this forum but neither worked
for me.

I added following to the registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Rpc]
"EnableAuthEpResolution"=dword:00000001
"RestrictRemoteClients"=dword:00000000

on my developing machine as suggested in

http://www.yqcomputer.com/ ;en-us;841893

I ran Remote Procedure Call (RPC) Locator service which was not running.

Is there some additional things I overlooked?
It's very essential for me to be able for remote debugging and I'm very
short in time, so help would be very appreciated.

Regards,
Brane Brodnik
 
 
 

Unable for remote debugging after Win XP SP2 installed

Post by Brane Brod » Fri, 17 Sep 2004 17:44:23

Hi again,

I found an utility called "De *** FirewallConfiguration.EXE" for remote
dubugging configuration. So "Not enough storage is available to complete the
operation." disapeared but unfortunately a message "Unable to connect to the
machine 'MACHINE_NAME'. Access is denied." appeared instead.

To resume: Tested machine is Win2000, developing machine is WinXP SP2. There
must be problem on developing machine, since I can remote debug from some
other Win2000 machine to the same tested machine.

I can see processes in remote machine if I use TCP/IP or PIPE transport that
supports native code, but I would like to debug managed code.

Can anyone help me configure WinXP SP2 for remote debugging?

Thanks in advance.



"Brane Brodnik" < XXXX@XXXXX.COM > je napisal v sporolo

 
 
 

Unable for remote debugging after Win XP SP2 installed

Post by Zeid » Sun, 19 Sep 2004 20:08:08

I did the same by running the program but apparently it didn't open up all
the required ports. For example it didn't open up UDP 4500 and 500 & it
didn't configure the dcom security usage on the PC running VS.Net
properly.

Here's the article that you should follow. I didn't change anything on the
server (Win2K)

http://www.yqcomputer.com/

Zeid
 
 
 

Unable for remote debugging after Win XP SP2 installed

Post by Brane Brod » Fri, 24 Sep 2004 03:20:04

Hi, Zeid,

I followed instructions in article and I can do remote debugging again.

Thank you very much.
Brane


"Zeid" < XXXX@XXXXX.COM > je napisal v sporolo