"net.exe" and "cmd.exe" don't execute properly

[Paul R McHan Jr]

When I log onto my ".net" account, two files continue to
try to open (net.exe and cmd.exe.) I watch them on
the "Processes" tab of my "Task Manager." If left
unchecked, they will completely populate the list of
active processes until my system resources are completely
depleted causing my computer to come to a stand still.

I can force them to end and everything seems to come back
to normal, but if I don't watch for it, my programs will
slow to a snails pace over time as these programs try to
load.

I have uninstalled the "MSN Messenger" and reinstalled it
to no avail. I suspect it is a conflict between the two
messenger services (the windows one connected to IE, and
the MSN one that works independently.)

I also set up my initial log on screen to automatically
use my .net account, but was unable to undo that decision.

[Oliver Saal [MS]]

Sounds very odd - from your description, it sounds like a worm/virus. I
would recommend you scan your system for viruses using the latest
signatures/virus updates you can find. To my knowledge, I've never heard of
MSN/Windows Messenger using console apps "net.exe" or "cmd.exe".

--
Oliver
This posting is provided "AS IS", with NO warranties and confers NO rights


"Paul R McHan Jr" > wrote in message
...
> When I log onto my ".net" account, two files continue to
> try to open (net.exe and cmd.exe.) I watch them on
> the "Processes" tab of my "Task Manager." If left
> unchecked, they will completely populate the list of
> active processes until my system resources are completely
> depleted causing my computer to come to a stand still.
>
> I can force them to end and everything seems to come back
> to normal, but if I don't watch for it, my programs will
> slow to a snails pace over time as these programs try to
> load.
>
> I have uninstalled the "MSN Messenger" and reinstalled it
> to no avail. I suspect it is a conflict between the two
> messenger services (the windows one connected to IE, and
> the MSN one that works independently.)
>
> I also set up my initial log on screen to automatically
> use my .net account, but was unable to undo that decision.