Re: How to find out the(the first machine) source machine being infected of infected virus
From: Steve N. (me_at_here.now)
Date: 01/14/05
- Next message: George Koger: "Windows installer:"
- Previous message: Harry Ohrn: "Re: Incoperating XP SP2 onto the original disc"
- In reply to: hon123456: "How to find out the(the first machine) source machine being infected of infected virus"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 14 Jan 2005 14:52:15 GMT
hon123456 wrote:
> Dear all,
> My company's network is become so slowly, I believed that it is infected
> by virus. How can I find out which machine is the first machine being infected.
>
> Please help.
Depends on the "virus" (more likely a worm, like Sasser or Blaster), but
what I've done is install one of the free firewalls on a clean PC, leave
it unconfigured and when ICMP hits occur note the IP address they
originate from, then use a port/IP scanner (like NMapWin) to help ID the
source machine, track it down and disinfect accordingly. On a normally
"secure" network (firewalled at the backbone) the most likely culprits
in my experience are stinking craptops that bozo users take home, get
infected, come to work and infect other unprotected PCs on the network.
However, even if all other machines are protected the infected
machine(s) can saturate your network with ICMP packets, degrading
network performance.
Another tool you can use is a packet-sniffer/protocol analyzer like
ehtereal to look for inordinate amounts of ICMP requests, but that won't
work on a switched network because not all traffic goes to all ports in
a switched environment.
Another cause might be some idiot doing music/file sharing services or
hosting network game services on a machine (a "rogue" server). Find it
basically the same way, look for high traffic sources.
Of course if your machines on the net were adequately protected with up
to date a/v, patched with all security updates and stupid users followed
security and usage rules (like _NO_ machines put in the net without
going through IT first, ever, _PERIOD_) none of this would have
happened, would it?
Ask your organization bosses how much your time costs? Is it worth
keeping on stupid users who don't folllow the rules? It is PEOPLE that
cause infections and network problems. In my mind such behaviour is
excuseless and grounds for termination. Of course my bosses don't listen
to me either, so good luck on that.
Steve
- Next message: George Koger: "Windows installer:"
- Previous message: Harry Ohrn: "Re: Incoperating XP SP2 onto the original disc"
- In reply to: hon123456: "How to find out the(the first machine) source machine being infected of infected virus"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|