R
ray breen
Hi Guys,
got a wierd problem and all i can do is try to solve it
from a technical angle as senior management aint delaying
with the reason.
Basically one of the members of staff has been browsing
on 'dody sites' and has downloaded something to his pc,
that is scanning the whole lan at intermittent intervals
and shortly there after our windows 2000 server is either
being rebooted or shutdown. I have gone to the extreme
measure of having to firewall each users pc so at least
they do not go down, but cannot do this to windows 2000
server for obvious reasons.
The server has all the latest updates installed, along
with the users pc. This has happened inumerable times and
after rebuilding his pc, the problem goes away until he
decides to browse the 'sites' again.
The ports that are scanned are to do with netbios over
tcp/ip which I cannot disable due to other services being
dependant upon them. Ports 139 and both 445 are scanned,
so all i can assume is that some information is available
via these ports that causes the server to be rebooted.
There is nothing in any of the log files or any other
record of the reboot, so its very difficult to narrow the
exact cause.
Does anyone have any thoughts?
Cheers
Ray
got a wierd problem and all i can do is try to solve it
from a technical angle as senior management aint delaying
with the reason.
Basically one of the members of staff has been browsing
on 'dody sites' and has downloaded something to his pc,
that is scanning the whole lan at intermittent intervals
and shortly there after our windows 2000 server is either
being rebooted or shutdown. I have gone to the extreme
measure of having to firewall each users pc so at least
they do not go down, but cannot do this to windows 2000
server for obvious reasons.
The server has all the latest updates installed, along
with the users pc. This has happened inumerable times and
after rebuilding his pc, the problem goes away until he
decides to browse the 'sites' again.
The ports that are scanned are to do with netbios over
tcp/ip which I cannot disable due to other services being
dependant upon them. Ports 139 and both 445 are scanned,
so all i can assume is that some information is available
via these ports that causes the server to be rebooted.
There is nothing in any of the log files or any other
record of the reboot, so its very difficult to narrow the
exact cause.
Does anyone have any thoughts?
Cheers
Ray