keep getting error and report error to ms after

Hmm, I'm more interested as to what program was listening on port 1784. The scan summary pasted above doesn't say. It's simply pointing out during its Port Scan phase that something is listen on 1784/TCP. But, that could be anything that uses a random or sequentially assigned port above 1024, not just that possible piece of malware.

On Windows 2000, I think you can run a "netstat -ano" in a CMD window, at least you can do this on Windows XP. The little "o" causes netstat to list the process id (PID) that is related to the open/listening ports. You can cross reference that to the process list in the task manager to identify the program using a port.

Or, a tool like Fport from Foundstone will show you the program name directly. Fport is a free tool available from the link below. One great thing about it (and most tools from Foundstone) is that you don't even need to install it. You just unzip it, and run Fport.exe from a CMD/DOS prompt, and it displays the information.

http://www.foundstone.com/knowledge/proddesc/fport.html

Knowing the program holding a port open is key to tracking down whether or not you have a Trojan or if that port being used is just a coincidence.