Hello !
I have done a lot of researches over the Internet, but without success.
After having spent a whole day trying to make Sice ( DS 3.2 ) function properly on remote under VMWare ( Host : XP SP2, Target : Win2k SP4 ), I obtained an error message from the SIRemote program at the very last step :

_________________________________________________________
Attempting direct link connection over named pipe to \\.\pipe\com_1
Initialized
Opened
Authenticating...Unable to connect to target machine on pipe

(Press any key to continue)
_________________________________________________________

I really don't see from where the issue is coming.
Nevertheless, the remote debug with WinDBG was working well.
I tested loads of parameters, like adding /DEBUG options in the boot.ini, different configurations of the virtual serial ports/pipes, and even in Filemon I saw that the requests to the pipe were successful.

Authentication... network ?? Don't know, and there is the problem.

If u guys know a solution... Thanks anyway.

All I can tell you is I was able to set up the remote system you are describing using Neitsa instructions and It worked OK, at least initially

check this site:

http://silverstr.ufies.org/lotr0/windbg-vmware.html

See if you are doing all the steps depicted there.

Have you played with the network settings of VMWARE??

The website doesn't work...
I followed exactly Neitsa instructions.
But yes, I played with the network settings... Because my Win2k in VMWare is to be used in a virtual network of VM's.
If you know which parameters have to be fixed...

Website is working well from here. I'' try to attach the page in a readable format with it's pictures.

Regards,

Thanks but... some times after my last post I succeeded into accessing to this website.
Okay, it is about WinDBG... I said in my first post that I had NO PROBLEMS with WinDBG ; I just want to try the siremote thing.
And reset the network settings of my VMWare... doesn't work.

naive questions:

Is WinDBG deactivated in the guest system??
It can "hog" the pipe and prevent Sice from connecting.

Is Sice server (The one in the guest sytem) configured for remote debugging and to start at boot?

By the way, I did get this remote debug configuration working at one point in time, but the results were less than impressive:

Some BPX did not "stick", the rate of communication between server an host system was Slooooooooowwwwwww. . .

And VMware would complain and close the guest machine at random when you were finally able to trace.

OKay, I think I've found the solution to my issue.
Thanks to naides, I reinstalled my VM and the problem was coming ( I think ) from my /DEBUG option for windbg at bootup, which was blocking everything but Windbg.
Thanks to all for your replies.