dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1799
share rss forum feed

Alexwdstmdsl

join:2013-01-01

I am Lagging ALOTTT!!!

Hi,

I paid for a 12mb speed and 766 kbps. I dont know but the last few days I have been constantly buffering. No, I dont use bittorrent, I only have 3 devices connected to the internet: computer, iphone and roku box. I did read another persons post and the windstream support guy said it could be a virus, well, I will tell you something awesome before you tell me its a virus. I have avast antivirus, enod32 antivirus, and comodo firewall. I run combofix and anti-malewarebyte before going to sleep every night. I dont think by running all these applications I would have missed a virus somewhere. I have these same applications running on business computer and I have windstream, I suffer no lags on a 3mb download, I feel like normal customers arent being treated the way they should be. DSL customer shouldnt be feeling lags, it just makes me sad that I moved from charter cable internet hell to another episode of hell in windstream. I dont have any other internet service options in Dalton, GA except these 2 providers. I am not sure who to contact next.

I wanna post my logs from my router and hopping someone can help me:

System Log

Date/Time Facility Severity Message
Feb 7 14:30:00 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=65.208.142.89 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=25294 DF PROTO=TCP SPT=1455 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 14:39:47 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=24.185.115.161 DST=98.18.160.81 LEN=60 TOS=0x00 PREC=0x00 TTL=50 ID=58049 DF PROTO=TCP SPT=51548 DPT=23 WINDOW=5840 RES=0x00 SYN URGP=0
Feb 7 14:49:53 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=46.55.142.27 DST=98.18.160.81 LEN=64 TOS=0x00 PREC=0x00 TTL=110 ID=42761 DF PROTO=TCP SPT=3193 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 14:53:49 syslog info -- MARK --
Feb 7 14:54:23 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=75.169.95.234 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=14813 DF PROTO=TCP SPT=54805 DPT=46597 WINDOW=8192 RES=0x00 SYN URGP=0
Feb 7 15:06:32 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=78.97.33.179 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=109 ID=44089 DF PROTO=TCP SPT=4313 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 15:23:04 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=187.174.137.136 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=3556 DF PROTO=TCP SPT=1991 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 15:23:07 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=187.174.137.136 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=3885 DF PROTO=TCP SPT=1991 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 15:44:39 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=186.67.35.171 DST=98.18.160.81 LEN=60 TOS=0x00 PREC=0x00 TTL=51 ID=23653 DF PROTO=TCP SPT=48588 DPT=8080 WINDOW=5840 RES=0x00 SYN URGP=0
Feb 7 15:53:48 syslog info -- MARK --
Feb 7 16:10:05 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=27.78.202.191 DST=98.18.160.81 LEN=52 TOS=0x00 PREC=0x00 TTL=110 ID=54160 DF PROTO=TCP SPT=4368 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 16:10:07 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=27.78.202.191 DST=98.18.160.81 LEN=52 TOS=0x00 PREC=0x00 TTL=110 ID=54210 DF PROTO=TCP SPT=4368 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 16:10:47 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=69.114.254.24 DST=98.18.160.81 LEN=64 TOS=0x00 PREC=0x00 TTL=50 ID=51322 DF PROTO=TCP SPT=51500 DPT=46597 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 16:30:35 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=176.227.212.162 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=50089 DF PROTO=TCP SPT=62468 DPT=445 WINDOW=8192 RES=0x00 SYN URGP=0
Feb 7 16:30:38 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=176.227.212.162 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=50191 DF PROTO=TCP SPT=62468 DPT=445 WINDOW=8192 RES=0x00 SYN URGP=0
Feb 7 16:33:48 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=187.121.117.46 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x20 TTL=111 ID=31633 DF PROTO=TCP SPT=2391 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 16:53:48 syslog info -- MARK --
Feb 7 16:58:13 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=198.23.143.72 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=32766 DF PROTO=TCP SPT=2567 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 16:58:16 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=198.23.143.72 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=607 DF PROTO=TCP SPT=2567 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 17:05:31 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=1.215.253.106 DST=98.18.160.81 LEN=40 TOS=0x00 PREC=0x00 TTL=100 ID=256 PROTO=TCP SPT=6000 DPT=1433 WINDOW=16384 RES=0x00 SYN URGP=0
Feb 7 17:11:58 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=177.218.87.153 DST=98.18.160.81 LEN=64 TOS=0x00 PREC=0x00 TTL=113 ID=41491 DF PROTO=TCP SPT=1047 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 17:22:54 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=14.63.226.14 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=106 ID=28487 PROTO=TCP SPT=46970 DPT=22 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 17:32:14 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=200.26.172.42 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=62146 DF PROTO=TCP SPT=1044 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 17:51:51 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=24.172.236.173 DST=98.18.160.81 LEN=44 TOS=0x00 PREC=0x00 TTL=28 ID=36901 PROTO=TCP SPT=15212 DPT=3389 WINDOW=4096 RES=0x00 SYN URGP=0
Feb 7 17:51:51 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=24.172.236.173 DST=98.18.160.81 LEN=44 TOS=0x00 PREC=0x00 TTL=33 ID=7295 PROTO=TCP SPT=19931 DPT=3389 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 7 17:53:49 syslog info -- MARK --
Feb 7 18:02:03 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=156.17.88.191 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=103 ID=59544 PROTO=TCP SPT=56361 DPT=3389 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 18:11:55 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=49.204.143.166 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=64477 DF PROTO=TCP SPT=2187 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 18:23:22 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=88.191.148.121 DST=98.18.160.81 LEN=48 TOS=0x04 PREC=0x00 TTL=107 ID=42317 PROTO=TCP SPT=21082 DPT=5910 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 18:51:26 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=58.59.135.198 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=107 ID=16968 DF PROTO=TCP SPT=1545 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 18:51:29 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=58.59.135.198 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=107 ID=17085 DF PROTO=TCP SPT=1545 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 18:53:48 syslog info -- MARK --
Feb 7 18:56:00 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=78.140.198.140 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=60970 DF PROTO=TCP SPT=4573 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 19:10:17 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=50.70.10.153 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=115 ID=21442 DF PROTO=TCP SPT=1409 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0
Feb 7 19:18:22 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=58.221.60.148 DST=98.18.160.81 LEN=64 TOS=0x00 PREC=0x00 TTL=112 ID=65535 DF PROTO=TCP SPT=4445 DPT=135 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 19:23:11 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=190.221.235.93 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=25432 DF PROTO=TCP SPT=2618 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 19:35:00 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=208.50.115.2 DST=98.18.160.81 LEN=64 TOS=0x00 PREC=0x00 TTL=114 ID=46697 DF PROTO=TCP SPT=32811 DPT=31724 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 19:43:57 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=59.149.108.232 DST=98.18.160.81 LEN=60 TOS=0x00 PREC=0x00 TTL=53 ID=30964 DF PROTO=TCP SPT=34118 DPT=23 WINDOW=5840 RES=0x00 SYN URGP=0
Feb 7 19:53:49 syslog info -- MARK --
Feb 7 20:11:30 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=198.20.70.114 DST=98.18.160.81 LEN=40 TOS=0x00 PREC=0x00 TTL=112 ID=1 PROTO=TCP SPT=32370 DPT=1023 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 7 20:25:40 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=89.39.6.62 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=112 ID=25222 DF PROTO=TCP SPT=2292 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 20:25:43 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=89.39.6.62 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=112 ID=25882 DF PROTO=TCP SPT=2292 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 20:30:56 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=61.191.235.81 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=238 ID=10911 DF PROTO=TCP SPT=48441 DPT=1433 WINDOW=16384 RES=0x00 SYN URGP=0
Feb 7 20:48:06 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=98.174.81.246 DST=98.18.160.81 LEN=60 TOS=0x00 PREC=0x00 TTL=47 ID=40324 DF PROTO=TCP SPT=41699 DPT=23 WINDOW=5840 RES=0x00 SYN URGP=0
Feb 7 20:53:49 syslog info -- MARK --
Feb 7 20:56:53 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=50.70.10.153 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=115 ID=10292 DF PROTO=TCP SPT=3324 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0
Feb 7 20:58:07 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=112.104.195.129 DST=98.18.160.81 LEN=52 TOS=0x00 PREC=0x00 TTL=42 ID=43740 DF PROTO=TCP SPT=3750 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 21:24:24 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=190.61.151.234 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=27839 DF PROTO=TCP SPT=3238 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 21:24:28 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=190.61.151.234 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=27958 DF PROTO=TCP SPT=3238 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 21:26:24 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=92.52.156.233 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=112 ID=12780 DF PROTO=TCP SPT=3700 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 21:35:11 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=69.114.254.24 DST=98.18.160.81 LEN=64 TOS=0x00 PREC=0x00 TTL=50 ID=32955 DF PROTO=TCP SPT=64210 DPT=46597 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 21:46:13 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=186.92.251.145 DST=98.18.160.81 LEN=52 TOS=0x00 PREC=0x00 TTL=49 ID=41303 DF PROTO=TCP SPT=3016 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 21:52:18 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=75.169.95.234 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=116 ID=23282 DF PROTO=TCP SPT=56960 DPT=46597 WINDOW=8192 RES=0x00 SYN URGP=0
Feb 7 21:53:48 syslog info -- MARK --
Feb 7 22:16:16 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=74.242.192.35 DST=98.18.160.81 LEN=52 TOS=0x00 PREC=0x00 TTL=51 ID=22039 DF PROTO=TCP SPT=20770 DPT=445 WINDOW=60352 RES=0x00 SYN URGP=0
Feb 7 22:16:20 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=74.242.192.35 DST=98.18.160.81 LEN=52 TOS=0x00 PREC=0x00 TTL=51 ID=22773 DF PROTO=TCP SPT=20770 DPT=445 WINDOW=60352 RES=0x00 SYN URGP=0
Feb 7 22:22:13 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=203.136.93.114 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=103 ID=53565 DF PROTO=TCP SPT=3893 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 22:34:36 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=69.175.126.170 DST=98.18.160.81 LEN=44 TOS=0x00 PREC=0x00 TTL=38 ID=53205 PROTO=TCP SPT=44949 DPT=443 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 7 22:43:20 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=194.150.254.6 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=41439 DF PROTO=TCP SPT=1696 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 22:53:48 syslog info -- MARK --
Feb 7 23:05:40 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=23.24.38.148 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=26922 DF PROTO=TCP SPT=65051 DPT=46597 WINDOW=8192 RES=0x00 SYN URGP=0
Feb 7 23:05:43 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=23.24.38.148 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=26984 DF PROTO=TCP SPT=65051 DPT=46597 WINDOW=8192 RES=0x00 SYN URGP=0
Feb 7 23:19:57 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=141.212.121.46 DST=98.18.160.81 LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=0 PROTO=TCP SPT=43715 DPT=443 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 23:24:57 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=121.22.64.147 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=239 ID=32594 DF PROTO=TCP SPT=49294 DPT=1433 WINDOW=16384 RES=0x00 SYN URGP=0
Feb 7 23:34:34 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=77.77.220.147 DST=98.18.160.81 LEN=60 TOS=0x00 PREC=0x00 TTL=50 ID=50142 DF PROTO=TCP SPT=2126 DPT=23 WINDOW=5760 RES=0x00 SYN URGP=0
Feb 7 23:42:19 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=64.56.64.18 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=36052 DF PROTO=TCP SPT=1700 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 7 23:53:48 syslog info -- MARK --
Feb 7 23:55:04 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=67.211.197.42 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=109 ID=23442 PROTO=TCP SPT=8752 DPT=22 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 8 00:05:25 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=188.191.240.224 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=114 ID=16001 DF PROTO=TCP SPT=3814 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 8 00:26:38 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=109.199.51.169 DST=98.18.160.81 LEN=64 TOS=0x00 PREC=0x00 TTL=108 ID=1554 DF PROTO=TCP SPT=1468 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 8 00:29:57 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=114.97.212.115 DST=98.18.160.81 LEN=52 TOS=0x00 PREC=0x00 TTL=113 ID=26810 DF PROTO=TCP SPT=36540 DPT=443 WINDOW=8192 RES=0x00 SYN URGP=0
Feb 8 00:32:48 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=95.245.24.217 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=112 ID=47929 DF PROTO=TCP SPT=3862 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0
Feb 8 00:45:19 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=121.145.120.75 DST=98.18.160.81 LEN=40 TOS=0x00 PREC=0x00 TTL=97 ID=256 PROTO=TCP SPT=6000 DPT=3389 WINDOW=16384 RES=0x00 SYN URGP=0
Feb 8 00:52:22 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=202.80.122.85 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=111 ID=29527 DF PROTO=TCP SPT=4269 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 8 00:53:49 syslog info -- MARK --
Feb 8 01:08:20 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=59.127.221.220 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=107 ID=15856 DF PROTO=TCP SPT=3992 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
Feb 8 01:15:10 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=190.74.181.69 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0xA0 TTL=111 ID=6766 DF PROTO=TCP SPT=4823 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0
Feb 8 01:25:52 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=85.119.217.48 DST=98.18.160.81 LEN=48 TOS=0x00 PREC=0x00 TTL=115 ID=26733 DF PROTO=TCP SPT=1297 DPT=445 WINDOW=64240 RES=0x00 SYN URGP=0
Feb 8 01:32:46 user alert kernel: Intrusion -> IN=ppp0 OUT= MAC= SRC=178.18.17.11 DST=98.18.160.81 LEN=44 TOS=0x00 PREC=0x00 TTL=117 ID=62009 DF PROTO=TCP SPT=28417 DPT=6515 WINDOW=8192 RES=0x00 SYN URGP=0
Feb 8 01:36:17 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Feb 8 01:36:17 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:2".^M
Feb 8 01:36:18 user info kernel: device br0 entered promiscuous mode
Feb 8 01:36:20 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M
Feb 8 01:36:20 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANConnectionDevice:2".^M
Feb 8 01:36:23 daemon debug syslog: Destroying device "urn:dslforum-org:device:WANDevice:1".^M


jtesh69

join:2010-08-27

2 edits

Well not having time at the moment to go through the log, but from the description you are running two Ant-viruses on the same machine. This in fact does not provide you protection but hinders it. While Malware-bytes does do a decent job at finding what its definition set it to find it still misses quite a few virus that are out in the wild.
Now moving on to Combo fix, while it is a decent tool to help in malware and virus removal it is not meant to be run on machines with no issues. Doing this can result in removal of files that are not truly malicious and cause connection and programs to not function correctly. Combo fix will not detect or remove many root kit and boot kits out there, such as Phar and TDSS families to name a few. Also combo fix was taken down for the past week due to the update on the 28/29th of January was in fact infested by a virus and would have infected any machine with the Sality family viruses.


Alexwdstmdsl

join:2013-01-01

Dont worry about combofix virus part, mine is new built computer so I havent put a comfix during time the virus event was going on so I know its clean version that I got from their site after they put a clean version up.

Running two antivirus would hinder it some way but my computer is fast enough run multiple applications though its built mainly for gaming. If your worried that combofix has missed something then I will post the results for TDSS and see if it catches something.

But why is my computer lagging this bad? Why is it the past couple of days? That's what I wanna know.

Alex


Alexwdstmdsl

join:2013-01-01

19:54:07.0337 4448 TDSS rootkit removing tool 2.8.15.0 Oct 31 2012 21:47:35
19:54:07.0821 4448 ============================================================
19:54:07.0821 4448 Current date / time: 2013/02/08 19:54:07.0821
19:54:07.0821 4448 SystemInfo:
19:54:07.0821 4448
19:54:07.0821 4448 OS Version: 6.1.7601 ServicePack: 1.0
19:54:07.0821 4448 Product type: Workstation
19:54:07.0821 4448 ComputerName: FEZ-PC
19:54:07.0821 4448 UserName: Fez
19:54:07.0821 4448 Windows directory: C:\Windows
19:54:07.0821 4448 System windows directory: C:\Windows
19:54:07.0821 4448 Running under WOW64
19:54:07.0821 4448 Processor architecture: Intel x64
19:54:07.0821 4448 Number of processors: 4
19:54:07.0821 4448 Page size: 0x1000
19:54:07.0821 4448 Boot type: Normal boot
19:54:07.0821 4448 ============================================================
19:54:08.0569 4448 Drive \Device\Harddisk0\DR0 - Size: 0x7470C06000 (465.76 Gb), SectorSize: 0x200, Cylinders: 0xED81, SectorsPerTrack: 0x3F, TracksPerCylinder: 0xFF, Type 'K0', Flags 0x00000040
19:54:08.0601 4448 ============================================================
19:54:08.0601 4448 \Device\Harddisk0\DR0:
19:54:08.0601 4448 MBR partitions:
19:54:08.0601 4448 \Device\Harddisk0\DR0\Partition1: MBR, Type 0x7, StartLBA 0x800, BlocksNum 0x32000
19:54:08.0601 4448 \Device\Harddisk0\DR0\Partition2: MBR, Type 0x7, StartLBA 0x32800, BlocksNum 0x3A353000
19:54:08.0601 4448 ============================================================
19:54:08.0694 4448 C: \Device\Harddisk0\DR0\Partition2
19:54:08.0694 4448 ============================================================
19:54:08.0694 4448 Initialize success
19:54:08.0694 4448 ============================================================
19:54:19.0209 4584 ============================================================
19:54:19.0209 4584 Scan started
19:54:19.0209 4584 Mode: Manual; SigCheck; TDLFS;
19:54:19.0209 4584 ============================================================
19:54:19.0458 4584 ================ Scan system memory ========================
19:54:19.0474 4584 System memory - ok
19:54:19.0474 4584 ================ Scan services =============================

================ Scan global ===============================
19:54:42.0172 4584 [ BA0CD8C393E8C9F83354106093832C7B ] C:\Windows\system32\basesrv.dll
19:54:42.0203 4584 [ 9E479C2B605C25DA4971ABA36250FAEF ] C:\Windows\system32\winsrv.dll
19:54:42.0219 4584 [ 9E479C2B605C25DA4971ABA36250FAEF ] C:\Windows\system32\winsrv.dll
19:54:42.0250 4584 [ D6160F9D869BA3AF0B787F971DB56368 ] C:\Windows\system32\sxssrv.dll
19:54:42.0265 4584 [ 24ACB7E5BE595468E3B9AA488B9B4FCB ] C:\Windows\system32\services.exe
19:54:42.0265 4584 [Global] - ok
19:54:42.0265 4584 ================ Scan MBR ==================================
19:54:42.0281 4584 [ A36C5E4F47E84449FF07ED3517B43A31 ] \Device\Harddisk0\DR0
19:54:42.0546 4584 \Device\Harddisk0\DR0 - ok
19:54:42.0562 4584 ================ Scan VBR ==================================
19:54:42.0562 4584 [ 19B9F38CD18FED8174B14BDA7B6D848E ] \Device\Harddisk0\DR0\Partition1
19:54:42.0562 4584 \Device\Harddisk0\DR0\Partition1 - ok
19:54:42.0593 4584 [ 1DFB6B0CBBBC58005D40401F24730C6D ] \Device\Harddisk0\DR0\Partition2
19:54:42.0593 4584 \Device\Harddisk0\DR0\Partition2 - ok
19:54:42.0593 4584 ============================================================
19:54:42.0593 4584 Scan finished
19:54:42.0593 4584 ============================================================
19:54:42.0593 4676 Detected object count: 0
19:54:42.0593 4676 Actual detected object count: 0

`````````````````````````````````````````````````````
`````````````````````````````````````````````````````
`````````````````````````````````````````````````````

I just ran TDSS and above was my result, still nothing.

jtesh69

join:2010-08-27
reply to Alexwdstmdsl

Running multiple Antivirus programs is moe than likely your issue. The reason being is Antivirus programs clash with each other, a bit like two guys fighting over one chick.
AV programs work at a low level whereas other programs run at high level. It is ok to have multiple instances of, lets say, web browsers as they just connect to the net then close down completely when you are finished surfing and they operate on the higher level.
So what actually happens is when you have two programs working at low level is they trip over each other causing program crashes and system lockups.

Most antivirus programs operate in two modes:
Scan Mode: the program examines the memory and files on your hard disk for traces of malware. This involves examining the contents each file for traces that ‘look like’ viruses.
Monitor Mode: usually called or referred to as ‘real time monitoring’, the program runs constantly scanning files as they are downloaded to your machine, notifying you if the file you just received contains something that appears to be a virus.
It’s ok to scan with a different antivirus program than your normal resident scanner as all that happens is the program will scan, report it findings then it will close down. Online scanners are good for second opinions. But if you install a second AV program it will (or should) inform you that another antivirus program has been detected and to uninstall it, if you choose to ignore this warning it will then install its own ‘real time monitors’ and that is when the problems will start – lockups, poor performance and crashes.

You will need to decide which antivirus program to keep and which one to uninstall.


jtesh69

join:2010-08-27
reply to Alexwdstmdsl

Now in regards to Comodo, while having a firewall is ideal you may be running multiple. Most modems and routers have them built in . So turning the un needed ones of may help improve performance. Avast if the paid version also contains a firewall. Avast tends to run programs it is not familiar with in a sand boxed mode which can hinder performance of programs, it also does this with web browsers.


Alexwdstmdsl

join:2013-01-01

You keep mentioning stuff to do with virus or poor performance.

Forget all that. My computer is awesome and is running super normal.

Why the hell is my windstream 12mb/s speed lagging? Why is I get less than 0.12 speed for upload and download? why is it buffering? Why is it that I get something like a yellow msg in a triangle that says cannot connect or internet isnt working?


jtesh69

join:2010-08-27
reply to Alexwdstmdsl

Wow sadly you come here complaining on performance. These issues can be caused by many things which each needs to be gone through. Your description and the admittance of running multiple AV and that all can have an impact on everything from machine performance and connectivity as explained. I am a professional PC and network repair tech of 17 years and run a business , have my CCNA, A+, Network+, Linux+, Server Plus etc. So to try and find your issues we have to fix all the things that can be causing problems. As far as your computer being Awesome, everyone thinks their computer is. Currently I run An Intel Core I-7 extreme 3970X, 64GB Ram, 320GB SSD raid, Dual 690 GTXs, so how awesome your machine is has no effect on me. That lil yellow triangle is contained on your pc and is usually shown when there is a connectivity issue(which is a windows feature), in which multiple AV's can cause, multiple firewalls can cause, and/or there can be a network issue that all these can be adding to create a much worse issue than there originally was. So coming here and attacking because you the help given isn't what you wish to hear is really poor showing. With anything in computer repair and network repair you have to remove all the simple issues first before moving on since they can actually add up or add to the other issues creating a very complex issue. Keep up the poor attitude and unwillingness to address each issue and I doubt many will help you.


malianx

join:2012-11-24
Clarendon, TX
Reviews:
·Windstream

Or it could be that he's using windstream DSL, which doesn't work for really MOST of their customers. I doubt anything he does, or anything you say to try to 'help' him will get anywhere.

My 12mbit, $80 connection:


Only computer on the network, booted into safemode + networking, zero applications running other than the browser.

Expand your moderator at work

jtesh69

join:2010-08-27
reply to Alexwdstmdsl

Re: I am Lagging ALOTTT!!!

Wow such animosity for someone who is unwilling to correct issues that can actually lend itself to the issue. Anti virus programs employ real time scanning if they are worth anything meaning they will scan any content including webpages and any media files as they are opened and ran. That can create lag in itself on viewing or downloading files put simply. Number 2 for no viruses half the ips in your log originate in Hong Kong, Bulgaria, Romania, Vietnam, etc. So either that log was when you had a Bit torrent client open or there is some other program possibly creating this traffic. Funny you should say you scanned with 3 Antiviruses and they found nothing since yesterday I just removed a severe infection off a computer that had 3 bootkits, 5 rootkits, 14 injection style viruses, of which TDSSkiller found 1 rootkit , Kaspersky rescue disk found 2 rootkits and the rest I actually had to manually go into the MBR and partitioning to find and remove. Which shows even those tools are not infallible.
Now as far as not knowing what it is like, I have had poor connection issues for almost 5 years with Windstream. I also have logs of the speed test(multiple sites), Line Quality test, copies of the field techs notes on the connection. Like tonight I have to use my phone to check E-mail.

Now I can agree with Malianx on that there may be a connection issue here caused by equipment possibly.Also that there may not be much a user can do, other than notifying Windstream. The main issue is that without fixing other issues which could be exacerbating the problem, all attempts at trying to troubleshoot is made more difficult, leading to a diagnosis or an attempted fix which can either fail or degrade performance further.


DavidFromKY4

join:2007-12-30
reply to jtesh69

I was sad to not see you using a Titan. Was reading through your specs and I could just feel it coming and it never did.


jtesh69

join:2010-08-27
reply to Alexwdstmdsl

I could put a Titans in the machine but it was built before they released it. Performance wise it currently performs about the same as having Titans in SLI . Only real benefit for me with the Titan would be heat generation and power use, which heat for me is a non issue really with my water cooling set up. Only thing that hits any performance is the online performance due to Windstream not wanting to upgrade their equipment. Here is one the benchmarks of the Titan and 6 series performance at stock clocks in SLI. »www.tomshardware.com/reviews/gef···2-9.html


Craig1993

join:2013-03-03
Denton, NC
reply to Alexwdstmdsl

Im running at 3mpbs as of now, but later in the day I start disconnecting and my connection ends up at a measly .5megs or slower. this is fucking awful they are gonna lose so much business if they dont fix this crap!!



Napsterbater
Meh
Premium,MVM
join:2002-12-28
Milledgeville, GA
Reviews:
·Windstream

said by Craig1993:

Im running at 3mpbs as of now, but later in the day I start disconnecting and my connection ends up at a measly .5megs or slower. this is fucking awful they are gonna lose so much business if they dont fix this crap!!

Welcome to Windstream. Take the time and read the forums, your definitely not the first to have this problem.
--
ASUS M4A79T Deluxe | AMD Phenom II x3 720 BE AM3 w/4 Cores @ 3.41Ghz(OC) | 4Gb DDR3 Memory @ 1600mhz | Sapphire ATI HD4870 1GB 800mhz/1000mhz(OC) | 2x500GB HDD's Raid 0 | Windows 7 Ultimate x64 Build 7600 (RTM) | Windstream DSL 12m (14.9m Sync)/766k


Windstream
Premium,VIP
join:2009-03-31
Twinsburg, OH
kudos:38
reply to Alexwdstmdsl

Alex-
Send me a PM with the phone number to your account. If it is an issue with the service in your area I will tell you, no holds barred. Otherwise I will do my best to help you resolve the situation.

Aaron
Specialist II
--
We're here to help! wci.broadbandhelp@windstream.com



TKHellz

@windstream.net
reply to Alexwdstmdsl

Windstream doesnt care, I've been living with internet spikes of 1000 ms every day all day, And dl speeds of 50 kb/s its so aggravating how they dont care about their customers. Its soooooo bad.