Annoying PC problem......

[nismodrifter]

I've had this happening for a while now but in the last few days it seems to have gotten worse:

Turn on pc, browse internet/do whatever......and then randomly the internet stops working, status in bottom left corner of IE is "Detecting Proxy Settings", get pissed off, restart computer, all works fine again for some random amount of time (5min to a few hours...) and then internet stops working again....

I had a feeling it was some kind of spyware or some other BS causing the problem so I run virus scan, spybot and ad-aware every night, yet again when I turned on my PC today my internet cut out after like 20 mins

any ideas as to what could be causing this problem? gets REALLY annoying to have to restart PC everytime this happens.....

[rage2]

www.lavasoftusa.com

Download Ad-Aware 6.

Run Ad-Aware 6.

Run Update, download, finish.

Run Scan, smartscan.

That should clean up pretty much all of your spyware.

[nismodrifter]

ahh shit, I totally forgot to update ad-aware recently....thx for the tip :) I scanned again and it found 25 new things :D

I'll post here again if this shit still happens again

[Ben]

w00t

[Ben]

This didn't solve the similar issue that I am having nismodrifter. My internet connection seems to die off. Currently I cannot view many picture files. Beyond shows up fine but hotlinked pictures dont show up, even after eliminating any sort of firewall or router.

[nismodrifter]

yeh I think the spyware has SOMETHING to do with this problem....however, I had this problem occur to me like 5 minutes after I formatted my hd....the only websites I had visited were beyond and maybe like microsoft update and then internet cut out which is odd unless rage2 and kenny are secretly installing spyware on our PC's now and selling our info to other people :D

also, I've had cases where the only thing that stops working is Internet explorer....IRC and MSN work fine but IE cuts out...

[Ben]

Originally posted by nismodrifter


also, I've had cases where the only thing that stops working is Internet explorer....IRC and MSN work fine but IE cuts out...

Thats my problem!!!!!!!!!!!!

[cappachihngo]

hmm ya i had that problem before 2.. u checked ur cables??? cuz my prob was a loose cable... but then a loose cable would kill msn 2... try running netscape 7.1 and see wut happens maybe its just internet explorer

[PsI]

Linux!!!;)

[nismodrifter]

Originally posted by cappachihngo
hmm ya i had that problem before 2.. u checked ur cables??? cuz my prob was a loose cable... but then a loose cable would kill msn 2... try running netscape 7.1 and see wut happens maybe its just internet explorer

definately not cables as sometimes IRC/MSN works sometimes......

[Davan]

Go into your internet options, connections tab, lan settings, and turn OFF the automatically detect settings.


But that doesn't really explain why it works intermittently....
:dunno:

[Khyron]

Who's your provider? At Cadvision, we had a cache flow thing that cached web pages - and we didn't ask your permission to run it. I know for a fact Telus is testing the same tech. Dunno about Shaw.

Remove the google bar, and any other IE plugins, as well as turning off the "automatically discover" thing mentioned above. Shaw uses a proxy but I think it's transparent to the end user.

Khyron

[nismodrifter]

REALLY gettin pissed off here, same shit happened to me last night

I had the problem once, restarted, used internet for 2 mins and then it cut out. I tryed getting onto beyond and at first it wouldn't work at all....so I refreshed...no workie....then refreshed again after like a minute of waiting and then it SLOWWWWWWWWWWWLY loaded up, so I let it load completely just to see what would happen, and then I hit the forums button....nothing happens, Internet is definately not working at this point so I restarted my pc...and all was well after that....

and I had just run spybot and ad-aware like 2 mins before this happened so it can't be something to do with spyware......

Shaw is my ISP and I turned off the automatically detect settings shit...

[EacydeLude]

I had a similar problem, I called shaw and they said that I had "packet loss" due to who know what? I then remembered that i had a cable splitter down in the basement. I replaced that and it worked a lot better. Its worth a try!

[cappachihngo]

hmm never had a prob wit shaw yet

[Davan]

You might need to get shaw to test your line, and perhaps install a filter or repeater.

[nismodrifter]

alright, its been happening a SHIT load today....pc is virus free and spyware free according to spybot and ad-aware....

I have however found that hitting the reset button on the cable modem fixes the problem....does that give any more clues as to wtf is going on?

[Khyron]

Ok try ping -T www.nexus-point.net (my machine is not on shaw which is what you want). Microsoft and other big sites block ping.

You should get no loss/dropped packets.

Like this:



Reply from 207.34.93.245: bytes=32 time=16ms TTL=253
Reply from 207.34.93.245: bytes=32 time<10ms TTL=253
Reply from 207.34.93.245: bytes=32 time<10ms TTL=253
Reply from 207.34.93.245: bytes=32 time=15ms TTL=253
Reply from 207.34.93.245: bytes=32 time<10ms TTL=253
Reply from 207.34.93.245: bytes=32 time=15ms TTL=253
Reply from 207.34.93.245: bytes=32 time<10ms TTL=253
Reply from 207.34.93.245: bytes=32 time=15ms TTL=253
Reply from 207.34.93.245: bytes=32 time=15ms TTL=253
Reply from 207.34.93.245: bytes=32 time=15ms TTL=253
Reply from 207.34.93.245: bytes=32 time<10ms TTL=253
Reply from 207.34.93.245: bytes=32 time=15ms TTL=253
Reply from 207.34.93.245: bytes=32 time=15ms TTL=253
Reply from 207.34.93.245: bytes=32 time<10ms TTL=253
Reply from 207.34.93.245: bytes=32 time=15ms TTL=253
Reply from 207.34.93.245: bytes=32 time<10ms TTL=253
Reply from 207.34.93.245: bytes=32 time=15ms TTL=253


Ping statistics for 207.34.93.245:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 16ms, Average = 8ms
Control-C

C:\Documents and Settings\khyron>

You should have 0% loss - but run it for around 100 packets to get a good average. One of my fiber links was dropping 30% and it was still unnoticable.

If you are dropping, tracert to the same address and see where the fucked link is. Post it up if it looks weird, or anything is over 250 miliseconds.

Then you phone Shaw, you say you are getting 20% packet loss, it's occuring at the gateway blah blah blah and they send a guy out right away. If you find the problem for them, they will act very fast to fix it.

Khyron

[nismodrifter]

alright, I did that and am getting constant results (ttl=248) but the times vary from like 20ms to 168ms, does that matter?

[Khyron]

168 is 168 miliseconds. So it's a little bad but not fucked. Ie in counterstrike or something your ping would be 168. 250ish is dialup but that can be just backbone problems. The key is the loss. Do that command again, and leave it up for 100 or so packets, then hit CTRL-C to stop it. It will have a summary like mine above.

Khyron

[nismodrifter]

Ping statistics for 209.115.249.51:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 146ms, Average = 48ms
Control-C
^C

[Khyron]

Here is my pings to google - note the time is 63 miliseconds.


C:\Documents and Settings\khyron>ping -t www.google.com

Pinging www.google.akadns.net [216.239.41.104] with 32 bytes of data:

Reply from 216.239.41.104: bytes=32 time=47ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239
Reply from 216.239.41.104: bytes=32 time=47ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239
Reply from 216.239.41.104: bytes=32 time=63ms TTL=239

Ping statistics for 216.239.41.104:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 63ms, Average = 60ms
Control-C
^C
C:\Documents and Settings\khyron>

Now here is to Central US:



C:\Documents and Settings\khyron>ping -t www.medievia.com

Pinging www.medievia.com [206.245.175.229] with 32 bytes of data:

Reply from 206.245.175.229: bytes=32 time=78ms TTL=112
Reply from 206.245.175.229: bytes=32 time=78ms TTL=112
Reply from 206.245.175.229: bytes=32 time=78ms TTL=112
Reply from 206.245.175.229: bytes=32 time=63ms TTL=112
Reply from 206.245.175.229: bytes=32 time=78ms TTL=112
Reply from 206.245.175.229: bytes=32 time=63ms TTL=112
Reply from 206.245.175.229: bytes=32 time=78ms TTL=112
Reply from 206.245.175.229: bytes=32 time=125ms TTL=112

Ping statistics for 206.245.175.229:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 125ms, Average = 80ms
Control-C
^C
C:\Documents and Settings\khyron>


So lets suppose I think 78ms and 125ms is too bad for my taste - it's actually fine. Remember you are limited by maximum speed signal can travel which is why going to east coast is worse than seattle.



C:\Documents and Settings\khyron>tracert www.medievia.com

Tracing route to www.medievia.com [206.245.175.229]
over a maximum of 30 hops:

1 16 ms 16 ms <10 ms dsl-kln-gateway-205.233.15.nucleus.com [209.115.166.65]
2 16 ms <10 ms 16 ms telus-gw-cgy.nucleus.com [207.34.94.1]
3 <10 ms 15 ms 16 ms clgrab31dr01.bb.telus.com [154.11.101.53]
4 16 ms 15 ms <10 ms clgrab21gr01.bb.telus.com [205.233.111.77]
5 47 ms 31 ms 47 ms clgrab21br01.bb.telus.com [154.11.10.218]
6 47 ms 47 ms 31 ms wnpgmb38br00.bb.telus.com [154.11.10.158]
7 63 ms 47 ms 46 ms chcnil23gr00.bb.telus.com [154.11.11.177]
8 31 ms 47 ms 47 ms chcgildtgr00.bb.telus.com [154.11.11.18]
9 31 ms 47 ms 47 ms williams.chcgildtgr00.bb.telus.com [154.11.3.178]
10 47 ms 47 ms 47 ms chcgil1wcx2-oc48.wcg.net [64.200.103.117]
11 47 ms 47 ms 46 ms brvwil1wcx3-pos9-0-1-a0.wcg.net [64.200.103.194]
12 78 ms 63 ms 62 ms nycmny2wcx3-pos5-0.wcg.net [64.200.210.110]
13 78 ms 62 ms 63 ms phlapa1wce2-atm3-0.wcg.net [64.200.240.198]
14 63 ms 78 ms 62 ms phlapa1wce2-fastnet-pos.wcg.net [65.77.115.54]
15 79 ms 62 ms 78 ms core02-phlpa.fast.net [206.245.170.2]
16 78 ms 63 ms 93 ms 209.92.248.198
17 79 ms 62 ms 94 ms LISTSERV [206.245.175.229]

Trace complete.

C:\Documents and Settings\khyron>


You can see that my network, and the local Telus stuff is perfect - 15 MS is about as good as it gets once you go internet.

From step 11 to 12 is the lag (not really but pretend it jumped to 250 or something). That's out of our control, so you say "Fucking internet is fucking fucked" and come back later. If the lag jumped immediately to 150+ on the first hop it's your shit or it's the cable modem->shaw. You have to eyeball the names and guess who owns the hops.

And that is your Ramzi hacker tip of the day.

Khyron