Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

TCP/IP Exhaustion?


  • Please log in to reply
9 replies to this topic

#1 adfdg344

adfdg344

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:12:30 PM

Posted 02 November 2015 - 05:46 PM

Hi, recently my modem has started rebooting when a torrent client is active. I've been able to rule out power and hardware issues, my router remains fine, this really only occurs with the modem when torrent software is active. The event viewer usually has event id 4227 with the message below:

TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.

I've tried reducing all network settings within the torrent client, adjusting the tcp delay to 60 seconds, and increasing max user ports in regedit but this does not solve the issue. I also tried resetting a lot of TCP settings, reinstall Intel network driver etc but this issue is persistent, any help would be appreciated. Here is what netstat shows, both when the torrent client is paused, and when it is active.

  TORRENT CLIENT INACTIVE

  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:27015        activate:49268         ESTABLISHED
  TCP    127.0.0.1:27015        activate:49272         ESTABLISHED
  TCP    127.0.0.1:27015        activate:49524         ESTABLISHED
  TCP    127.0.0.1:49268        activate:27015         ESTABLISHED
  TCP    127.0.0.1:49272        activate:27015         ESTABLISHED
  TCP    127.0.0.1:49524        activate:27015         ESTABLISHED
  TCP    127.0.0.1:49627        activate:49628         ESTABLISHED
  TCP    127.0.0.1:49628        activate:49627         ESTABLISHED
  TCP    127.0.0.1:49899        activate:49900         ESTABLISHED
  TCP    127.0.0.1:49900        activate:49899         ESTABLISHED
  TCP    127.0.0.1:49902        activate:49903         ESTABLISHED
  TCP    127.0.0.1:49903        activate:49902         ESTABLISHED
  TCP    192.168.1.3:49221      17.110.244.82:https    ESTABLISHED
  TCP    192.168.1.3:49310      db3wns2011007:https    ESTABLISHED
  TCP    192.168.1.3:49313      de-in-f125:5222        ESTABLISHED
  TCP    192.168.1.3:49339      lhr08s07-in-f5:https   ESTABLISHED
  TCP    192.168.1.3:49382      143.127.93.101:http    ESTABLISHED
  TCP    192.168.1.3:49388      a23-4-214-169:https    ESTABLISHED
  TCP    192.168.1.3:49467      DS1815:microsoft-ds    ESTABLISHED
  TCP    192.168.1.3:49493      166.98.7.27:http       ESTABLISHED
  TCP    192.168.1.3:49552      de-in-f188:5228        ESTABLISHED
  TCP    192.168.1.3:49566      herndon-2:https        ESTABLISHED
  TCP    192.168.1.3:49593      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:49601      lhr08s07-in-f10:https  CLOSE_WAIT
  TCP    192.168.1.3:49618      17.167.144.40:https    CLOSE_WAIT
  TCP    192.168.1.3:49619      2.18.13.56:https       CLOSE_WAIT
  TCP    192.168.1.3:49620      17.110.244.50:https    CLOSE_WAIT
  TCP    192.168.1.3:49622      17.110.244.52:https    CLOSE_WAIT
  TCP    192.168.1.3:49626      DS1815:4243            ESTABLISHED
  TCP    192.168.1.3:49629      ec2-174-129-195-83:https  CLOSE_WAIT
  TCP    192.168.1.3:49634      api:https              ESTABLISHED
  TCP    192.168.1.3:49635      lb:https               CLOSE_WAIT
  TCP    192.168.1.3:49646      DS1815:9091            ESTABLISHED
  TCP    192.168.1.3:49656      api:https              ESTABLISHED
  TCP    192.168.1.3:49659      104.20.7.159:https     CLOSE_WAIT
  TCP    192.168.1.3:49713      72.21.215.52:http      CLOSE_WAIT
  TCP    192.168.1.3:49720      104.25.234.34:http     CLOSE_WAIT
  TCP    192.168.1.3:49867      104.25.68.28:https     CLOSE_WAIT
  TCP    192.168.1.3:50519      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:51397      lhr08s07-in-f14:https  ESTABLISHED
  TCP    192.168.1.3:51559      lhr08s05-in-f234:https  ESTABLISHED
  TCP    192.168.1.3:51635      lhr14s23-in-f33:https  TIME_WAIT
  TCP    192.168.1.3:51637      lhr08s07-in-f36:https  TIME_WAIT
  TCP    192.168.1.3:51638      lhr08s07-in-f14:https  TIME_WAIT
  TCP    192.168.1.3:51640      lhr08s07-in-f7:https   TIME_WAIT
  TCP    192.168.1.3:51644      lhr08s07-in-f14:https  TIME_WAIT
  TCP    192.168.1.3:51654      27.122.115.6:https     CLOSE_WAIT
  TCP    192.168.1.3:51657      customer:https         CLOSE_WAIT
  TCP    192.168.1.3:51658      nzbs:https             CLOSE_WAIT
  TCP    192.168.1.3:51659      caam-190-10-14-a167:https  CLOSE_WAIT
  TCP    192.168.1.3:51702      vhost:http             CLOSE_WAIT
  TCP    192.168.1.3:51742      17.110.244.82:https    ESTABLISHED
  TCP    192.168.1.3:51968      vhost:http             CLOSE_WAIT
  TCP    192.168.1.3:51981      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:52070      192.168.1.1:5000       TIME_WAIT
  TCP    192.168.1.3:52071      192.168.1.1:5000       TIME_WAIT
  TCP    192.168.1.3:52083      DS1815:5000            ESTABLISHED
  TCP    192.168.1.3:52094      17.172.238.27:5223     CLOSING
  TCP    192.168.1.3:52095      17.172.239.138:5223    ESTABLISHED
  TCP    192.168.1.3:52096      17.172.238.27:5223     SYN_SENT
  TCP    192.168.1.3:54007      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:55518      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:55620      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:55724      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:56432      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:57271      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:58795      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:59466      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:60779      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:61255      17.110.244.88:https    ESTABLISHED
  TCP    192.168.1.3:61258      17.172.208.81:https    ESTABLISHED
  TCP    192.168.1.3:61276      17.167.138.45:https    ESTABLISHED
  TCP    192.168.1.3:61279      17.167.138.45:https    ESTABLISHED
  TCP    192.168.1.3:61283      17.167.138.45:https    ESTABLISHED
  TCP    192.168.1.3:61286      17.167.138.45:https    ESTABLISHED
  TCP    192.168.1.3:62774      17.110.244.82:https    ESTABLISHED
  TCP    192.168.1.3:63166      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:63617      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:63745      17.248.144.107:https   CLOSE_WAIT
  TCP    [::1]:8080             HAFX:49850             ESTABLISHED
  TCP    [::1]:8080             HAFX:49851             ESTABLISHED
  TCP    [::1]:8080             HAFX:52152             TIME_WAIT
  TCP    [::1]:8080             HAFX:52252             TIME_WAIT
  TCP    [::1]:8080             HAFX:52332             FIN_WAIT_2
  TCP    [::1]:49850            HAFX:8080              ESTABLISHED
  TCP    [::1]:49851            HAFX:8080              ESTABLISHED
  TCP    [::1]:52332            HAFX:8080              CLOSE_WAIT

TORRENT CLIENT ACTIVE

  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:27015        activate:49268         ESTABLISHED
  TCP    127.0.0.1:27015        activate:49272         ESTABLISHED
  TCP    127.0.0.1:27015        activate:49524         ESTABLISHED
  TCP    127.0.0.1:49268        activate:27015         ESTABLISHED
  TCP    127.0.0.1:49272        activate:27015         ESTABLISHED
  TCP    127.0.0.1:49524        activate:27015         ESTABLISHED
  TCP    127.0.0.1:49627        activate:49628         ESTABLISHED
  TCP    127.0.0.1:49628        activate:49627         ESTABLISHED
  TCP    127.0.0.1:49899        activate:49900         ESTABLISHED
  TCP    127.0.0.1:49900        activate:49899         ESTABLISHED
  TCP    127.0.0.1:49902        activate:49903         ESTABLISHED
  TCP    127.0.0.1:49903        activate:49902         ESTABLISHED
  TCP    192.168.1.3:38883      cm-84:59293            ESTABLISHED
  TCP    192.168.1.3:49221      17.110.244.82:https    ESTABLISHED
  TCP    192.168.1.3:49310      db3wns2011007:https    ESTABLISHED
  TCP    192.168.1.3:49313      de-in-f125:5222        ESTABLISHED
  TCP    192.168.1.3:49339      lhr08s07-in-f5:https   ESTABLISHED
  TCP    192.168.1.3:49382      143.127.93.101:http    ESTABLISHED
  TCP    192.168.1.3:49388      a23-4-214-169:https    ESTABLISHED
  TCP    192.168.1.3:49467      DS1815:microsoft-ds    ESTABLISHED
  TCP    192.168.1.3:49493      166.98.7.27:http       ESTABLISHED
  TCP    192.168.1.3:49552      de-in-f188:5228        ESTABLISHED
  TCP    192.168.1.3:49566      herndon-2:https        ESTABLISHED
  TCP    192.168.1.3:49593      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:49601      lhr08s07-in-f10:https  CLOSE_WAIT
  TCP    192.168.1.3:49618      17.167.144.40:https    CLOSE_WAIT
  TCP    192.168.1.3:49619      2.18.13.56:https       CLOSE_WAIT
  TCP    192.168.1.3:49620      17.110.244.50:https    CLOSE_WAIT
  TCP    192.168.1.3:49622      17.110.244.52:https    CLOSE_WAIT
  TCP    192.168.1.3:49626      DS1815:4243            ESTABLISHED
  TCP    192.168.1.3:49629      ec2-174-129-195-83:https  CLOSE_WAIT
  TCP    192.168.1.3:49634      api:https              ESTABLISHED
  TCP    192.168.1.3:49635      lb:https               CLOSE_WAIT
  TCP    192.168.1.3:49646      DS1815:9091            ESTABLISHED
  TCP    192.168.1.3:49656      api:https              ESTABLISHED
  TCP    192.168.1.3:49659      104.20.7.159:https     CLOSE_WAIT
  TCP    192.168.1.3:49713      72.21.215.52:http      CLOSE_WAIT
  TCP    192.168.1.3:49720      104.25.234.34:http     CLOSE_WAIT
  TCP    192.168.1.3:49867      104.25.68.28:https     CLOSE_WAIT
  TCP    192.168.1.3:50519      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:51654      27.122.115.6:https     CLOSE_WAIT
  TCP    192.168.1.3:51657      customer:https         CLOSE_WAIT
  TCP    192.168.1.3:51658      nzbs:https             CLOSE_WAIT
  TCP    192.168.1.3:51659      caam-190-10-14-a167:https  CLOSE_WAIT
  TCP    192.168.1.3:51702      vhost:http             CLOSE_WAIT
  TCP    192.168.1.3:51742      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:51968      vhost:http             CLOSE_WAIT
  TCP    192.168.1.3:51981      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:52122      lhr08s05-in-f234:https  ESTABLISHED
  TCP    192.168.1.3:52190      lhr08s07-in-f14:https  ESTABLISHED
  TCP    192.168.1.3:52353      lhr08s07-in-f14:https  ESTABLISHED
  TCP    192.168.1.3:52506      lhr08s07-in-f35:http   ESTABLISHED
  TCP    192.168.1.3:52512      geoiptool:https        CLOSE_WAIT
  TCP    192.168.1.3:52535      geoiptool:https        CLOSE_WAIT
  TCP    192.168.1.3:52538      94:https               ESTABLISHED
  TCP    192.168.1.3:52542      lhr14s24-in-f10:https  ESTABLISHED
  TCP    192.168.1.3:52544      de-in-f95:https        ESTABLISHED
  TCP    192.168.1.3:52546      lhr08s07-in-f35:https  ESTABLISHED
  TCP    192.168.1.3:52550      lhr14s24-in-f10:https  ESTABLISHED
  TCP    192.168.1.3:52552      lhr14s24-in-f10:https  ESTABLISHED
  TCP    192.168.1.3:52588      ghs-vip-any-c46:https  ESTABLISHED
  TCP    192.168.1.3:52591      de-in-f141:https       ESTABLISHED
  TCP    192.168.1.3:52595      lhr14s27-in-f10:https  ESTABLISHED
  TCP    192.168.1.3:52596      de-in-f141:https       ESTABLISHED
  TCP    192.168.1.3:52614      lhr14s24-in-f78:https  ESTABLISHED
  TCP    192.168.1.3:52616      DS1815:5000            ESTABLISHED
  TCP    192.168.1.3:52635      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52639      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52640      ns39987:34000          TIME_WAIT
  TCP    192.168.1.3:52641      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52647      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52649      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52650      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52653      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52654      ns39987:34000          LAST_ACK
  TCP    192.168.1.3:52655      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52656      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52657      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52658      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52659      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52666      ns39987:34000          CLOSING
  TCP    192.168.1.3:52668      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52671      ns39987:34000          CLOSING
  TCP    192.168.1.3:52672      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52674      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52675      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52676      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52677      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52678      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52682      ns39987:34000          ESTABLISHED
  TCP    192.168.1.3:52684      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52686      sora:34000             ESTABLISHED
  TCP    192.168.1.3:52687      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52689      sora:34000             ESTABLISHED
  TCP    192.168.1.3:52690      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52692      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52695      helios:43000           TIME_WAIT
  TCP    192.168.1.3:52706      helios:43000           TIME_WAIT
  TCP    192.168.1.3:52708      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52710      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52712      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52714      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52719      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52722      192.168.1.1:5000       TIME_WAIT
  TCP    192.168.1.3:52723      192.168.1.1:5000       TIME_WAIT
  TCP    192.168.1.3:52727      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52728      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52735      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52740      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52741      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52742      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52749      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52754      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52755      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52756      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52757      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52758      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52759      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52760      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52761      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52762      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52763      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52764      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52766      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52767      helios:43000           TIME_WAIT
  TCP    192.168.1.3:52771      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52777      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52778      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52781      sora:34000             ESTABLISHED
  TCP    192.168.1.3:52782      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52789      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52790      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52793      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52797      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52800      17.110.244.82:https    ESTABLISHED
  TCP    192.168.1.3:52803      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52804      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52805      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52806      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52807      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52808      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52809      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52810      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52811      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52812      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52813      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52814      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52815      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52816      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52817      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52818      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52819      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52820      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52821      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52822      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52824      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52826      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52828      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52830      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52831      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52832      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52833      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52834      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52835      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52836      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52837      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52840      ns3300615:34000        ESTABLISHED
  TCP    192.168.1.3:52841      ns3300615:34000        ESTABLISHED
  TCP    192.168.1.3:52842      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52843      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52845      17.110.229.13:5223     ESTABLISHED
  TCP    192.168.1.3:52846      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52847      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52848      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52849      ns3300615:34000        TIME_WAIT
  TCP    192.168.1.3:52850      sora:34000             ESTABLISHED
  TCP    192.168.1.3:52852      198.41.202.225:http    TIME_WAIT
  TCP    192.168.1.3:52853      ns39987:34000          SYN_SENT
  TCP    192.168.1.3:52854      17.110.224.19:5223     ESTABLISHED
  TCP    192.168.1.3:54007      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:55518      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:55620      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:55724      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:56432      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:57271      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:58795      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:59466      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:60779      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:61255      17.110.244.88:https    ESTABLISHED
  TCP    192.168.1.3:61258      17.172.208.81:https    ESTABLISHED
  TCP    192.168.1.3:61276      17.167.138.45:https    ESTABLISHED
  TCP    192.168.1.3:61279      17.167.138.45:https    ESTABLISHED
  TCP    192.168.1.3:61283      17.167.138.45:https    ESTABLISHED
  TCP    192.168.1.3:61286      17.167.138.45:https    ESTABLISHED
  TCP    192.168.1.3:62774      17.110.244.82:https    ESTABLISHED
  TCP    192.168.1.3:63166      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:63617      17.110.244.82:https    CLOSE_WAIT
  TCP    192.168.1.3:63745      17.248.144.107:https   CLOSE_WAIT
  TCP    [::1]:8080             HAFX:49850             ESTABLISHED
  TCP    [::1]:8080             HAFX:49851             ESTABLISHED
  TCP    [::1]:8080             HAFX:54012             TIME_WAIT
  TCP    [::1]:8080             HAFX:55020             TIME_WAIT
  TCP    [::1]:8080             HAFX:55461             FIN_WAIT_2
  TCP    [::1]:49850            HAFX:8080              ESTABLISHED
  TCP    [::1]:49851            HAFX:8080              ESTABLISHED
  TCP    [::1]:55461            HAFX:8080              CLOSE_WAIT

Edited by adfdg344, 02 November 2015 - 05:46 PM.


BC AdBot (Login to Remove)

 


#2 shelf life

shelf life

  • Malware Response Team
  • 2,649 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:@localhost
  • Local time:08:30 AM

Posted 02 November 2015 - 06:15 PM

Just out of curiosity what client are you using? You said you limited the max number of connections out and per torrent in the software? Did you also try to throttle the bandwidth?


How Can I Reduce My Risk to Malware?


#3 adfdg344

adfdg344
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:12:30 PM

Posted 02 November 2015 - 06:26 PM

Just out of curiosity what client are you using? You said you limited the max number of connections out and per torrent in the software? Did you also try to throttle the bandwidth?

 

Hi, the client is deluge. There were already limits set to ~80% bandwidth, I did not try throttling further as nothing is currently downloading, just seeding, but even then most are inactive. Deluge shows around 25 connections and 388 DHT nodes. 

 

I remembered another common event log is event id 1001, a WPNConnectionFailure that has numerous entries when it occurs. 

 

Fault bucket , type 0
Event Name: WPNConnectionFailure
Response: Not available
Cab Id: 0


Problem signature:
P1: Data Fast-Reconnect
P2: 8004acb3
P3: WNP
P4: Unknown
P5: Unknown
P6: Unknown
P7: 1
P8: 242
P9: 
P10: 
Version=1
EventType=WPNConnectionFailure
EventTime=130909469428781858
Consent=1
UploadTime=130909752553863081
ReportFlags=256
ReportIdentifier=44af3b74-816b-11e5-bfcd-6245b4e75b75
Response.type=4
Sig[0].Name=Scenario
Sig[0].Value=Data Fast-Reconnect
Sig[1].Name=Error Result
Sig[1].Value=8004acb1
Sig[2].Name=Error Source
Sig[2].Value=WNP
Sig[3].Name=Protocol
Sig[3].Value=Unknown
Sig[4].Name=Proxy Type
Sig[4].Value=Unknown
Sig[5].Name=Interface Type
Sig[5].Value=Unknown
Sig[6].Name=Platform Role
Sig[6].Value=1
Sig[7].Name=Geo Id
Sig[7].Value=242
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10240.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
FriendlyEventName=Windows Push Notifications Connectivity Quality of Service Event
ConsentKey=WPNConnectionFailure
AppName=wpnprv.dll
AppPath=C:\WINDOWS\wpnprv.dll
ApplicationIdentity=00000000000000000000000000000000


Edited by adfdg344, 02 November 2015 - 06:29 PM.


#4 shelf life

shelf life

  • Malware Response Team
  • 2,649 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:@localhost
  • Local time:08:30 AM

Posted 02 November 2015 - 09:09 PM

I tried running Deluge on a Windows machine before and it just didnt behave as expected. Iam a little leery of cross-platform software anyway.   You have any of its plugins running? Did you recently update it or anything?


How Can I Reduce My Risk to Malware?


#5 adfdg344

adfdg344
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:12:30 PM

Posted 03 November 2015 - 08:06 AM

I tried running Deluge on a Windows machine before and it just didnt behave as expected. Iam a little leery of cross-platform software anyway.   You have any of its plugins running? Did you recently update it or anything?

 

Still running the same version for a while, so nothing new on that side. But I will try disabling the webui plugin and see if that helps.



#6 adfdg344

adfdg344
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:12:30 PM

Posted 03 November 2015 - 12:44 PM

OK so it seems like a tracker is the cause, they are having issues on their side, and me having a lot of torrents for said tracker results in something happening and overwhelming the modem.  I've stopped all related torrents until they sort their issues out, will update later to see if there were any modem reboots with just the other torrents and trackers enabled.



#7 shelf life

shelf life

  • Malware Response Team
  • 2,649 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:@localhost
  • Local time:08:30 AM

Posted 03 November 2015 - 05:51 PM

Ok, not on your end after all. I guess thats good. Surely the tracker will get it sorted out eventually.


How Can I Reduce My Risk to Malware?


#8 adfdg344

adfdg344
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:12:30 PM

Posted 03 November 2015 - 06:17 PM

Ok, not on your end after all. I guess thats good. Surely the tracker will get it sorted out eventually.

 

All was going well after pausing the related torrents, but the reboots still happened. I then switched modems to an old one my ISP provided and its been stable with all torrents running for hours now. Now its looking like it was a modem issue after all, because this old one is working perfectly. 

 

Well thanks for your help shelf life, this is sorted for me now.



#9 wjlesaulnier

wjlesaulnier

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bowling green, KY
  • Local time:07:30 AM

Posted 21 November 2015 - 03:07 PM

I've had problems with Deluge in the past, switched to Qbittorrent and no problems at all now.



#10 sAyer

sAyer

  • Members
  • 52 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North Carolina
  • Local time:07:30 AM

Posted 22 November 2015 - 01:43 AM

I've had problems with Deluge in the past, switched to Qbittorrent and no problems at all now.

 

Qbittorrent is my client of choice. If most users of other clients tried it I think they would not look back. Updated often and open source.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users