**TCP FIN Scan** Infected or what?

Discussion in 'System Security & Infection Support' started by Vaskar, Jun 20, 2011.

  1. Vaskar

    Vaskar

    Joined:
    Jun 20, 2011
    Messages:
    1
    Likes Received:
    0
    So ive been doing some reading about what this thing is and a lot of people have been saying it Virus related but i ran my AVG and nothing came up so what do i do?

    06/19/2011 15:26:21 **TCP FIN Scan** 192.168.2.101, 50237->> 72.21.91.19, 80 (from WAN Outbound)
    06/19/2011 15:25:41 **TCP FIN Scan** 192.168.2.101, 50127->> 72.21.91.19, 80 (from WAN Outbound)
    06/19/2011 14:11:01 NTP Date/Time updated.
    06/19/2011 13:56:35 **TCP FIN Scan** 74.122.121.14, 80->> 192.168.2.101, 65195 (from WAN Inbound)
    06/19/2011 13:56:35 **TCP FIN Scan** 188.117.37.149, 80->> 192.168.2.101, 65206 (from WAN Inbound)
    06/19/2011 13:56:35 **TCP FIN Scan** 46.137.106.213, 80->> 192.168.2.101, 65105 (from WAN Inbound)
    06/19/2011 13:56:35 **TCP FIN Scan** 69.171.228.39, 80->> 192.168.2.101, 65064 (from WAN Inbound)
    06/19/2011 13:56:35 **TCP FIN Scan** 66.220.146.46, 80->> 192.168.2.101, 65205 (from WAN Inbound)
    06/19/2011 13:56:35 **TCP FIN Scan** 74.201.117.247, 80->> 192.168.2.101, 65178 (from WAN Inbound)
    06/19/2011 13:56:35 **TCP FIN Scan** 184.73.185.71, 80->> 192.168.2.101, 65166 (from WAN Inbound)

    thanks
     
    Vaskar, Jun 20, 2011
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.