Cable Forum - View Single Post - Problem with incorrect asigned static IP on NTL...

grubbymitts · 31-03-2006, 22:58

Just read the first post again properly. Thousands of requests for a port would not be because you have a new IP and that IP used to be a server for a P2P package. You have either a) peed off an IRC script kiddy somehow or b) someone has got a phished/hacked pc and your IP range is being bombarded with requests by it. If your box was compromised (usually due to not updating Windows regularly or spyware/viruses) then something would have been listening at that port and accepted the requests. It looks like this hasn't happened.

Best advice is to tell your firewall to deny all access attempts to that port. In a couple of days the attack vector will move on to another IP range. It happens alot with the Sasser worm.

31-03-2006, 22:58	#9
grubbymitts Inactive Join Date: Mar 2005 Posts: 544	Re: Problem with incorrect asigned static IP on NTL... Just read the first post again properly. Thousands of requests for a port would not be because you have a new IP and that IP used to be a server for a P2P package. You have either a) peed off an IRC script kiddy somehow or b) someone has got a phished/hacked pc and your IP range is being bombarded with requests by it. If your box was compromised (usually due to not updating Windows regularly or spyware/viruses) then something would have been listening at that port and accepted the requests. It looks like this hasn't happened. Best advice is to tell your firewall to deny all access attempts to that port. In a couple of days the attack vector will move on to another IP range. It happens alot with the Sasser worm.