C
Chelvan
Hello all,
We have around 200 Win2K Pro. desktops installed on our
campus. The erratic behavior was first brought to our
attention last fall, and then it re-appeared again earlier
this year, and for the third time this past week.
The erratic behavior,
1. Spontaneous reboots. The user can be in any application
and the system will simply restart.
2. Losing mapped network drives.
Next, the reason I mentioned the specific times is
because, it was then that the campus, faculty, staff and
students machines were hit hard by viruses. Blaster in the
fall, MyDoom at the start of this year and this week,
Bagel and Netsky.
When we have infected computers on our network, Win2K pcs
exhibit the above behaviors. These erratic pcs *are not*
infected with the virus. When we do finally eradicate the
virus from our internal network, these pcs are stable
again.
Anyone have any ideas as to what's going on and what it is
that we could do? Until we clean all the infected pcs,
this problem will go on.
TIA
Chelvan
We have around 200 Win2K Pro. desktops installed on our
campus. The erratic behavior was first brought to our
attention last fall, and then it re-appeared again earlier
this year, and for the third time this past week.
The erratic behavior,
1. Spontaneous reboots. The user can be in any application
and the system will simply restart.
2. Losing mapped network drives.
Next, the reason I mentioned the specific times is
because, it was then that the campus, faculty, staff and
students machines were hit hard by viruses. Blaster in the
fall, MyDoom at the start of this year and this week,
Bagel and Netsky.
When we have infected computers on our network, Win2K pcs
exhibit the above behaviors. These erratic pcs *are not*
infected with the virus. When we do finally eradicate the
virus from our internal network, these pcs are stable
again.
Anyone have any ideas as to what's going on and what it is
that we could do? Until we clean all the infected pcs,
this problem will go on.
TIA
Chelvan