I hate my intarwebs

[pavel_lishin]

My internet connection goes out sporadically. But it doesn't just boot me offline - it just pretends that it's a freshman fratboy and starts chugging data like crazy, and then pukes them all up five minutes later. For about five minutes, I'll have zero connectivity - then suddenly, everything floods in all at once. AIM won't boot me off, nor will

Comments

[eazyt]

here's what you do

1. start up cmd, type in ipconfig, and get your default gateway ip. if it's anything thats not 192.168.x.x or 10.x.x.x or 172.16.x.x (i think), skip to step 2. now type ping -t ... leave this running, you should get regular ping times of <10ms.. if you get anything different, the problem is between you and your router... if you just get "request timed out" over and over, yet are still on the inet, check your router, chances are it was coded by dumbfucks who set "dont respond to pings from the LAN" on by default

2. if your default gateway reported by ipconfig is a real IP address (not in the ranges listed above) then use that IP for this, otherwise, go into your router config and get your gateway IP... then open up another cmd box and do ping -t ... you should be getting a consistant ping of 10-30ms, if you get request timed out all the time, something is blocking pings... if you get request timed out every so often, you're having packet loss, call comcast and tell them you can't get on the internet (don't say

[pavel_lishin]

It's cool, I need talking down to, I know next-to-nothing about networking.

No problem getting to the router, but I'm getting anywhere from 200-400ms pings to the actual gateway. I'm going to assume my roommate is downloading Anime porn.

Is it a good idea to just leave the ping running the whole time?

[eazyt]

if you're getting 200-400ms pings to the gateway, unplug the wire from the back of the router (that goes to the cable modem) and plug it directly into your computer

then do in cmd: ipconfig /release
then: ipconfig /renew

now ping the gateway you see in ipconfig, and if it still has that high of a ping, it's time to call comcast and tell them UR INTARNET ISNT WORKING (they don't understand anything else)

[insolent_pool]

start -> run -> ipconfig (then press enter)
Bunch of crap is then shown.
Paste 'gateway' and your ip.

[alexhays]

just smoke a bowl every 15 mins

[swankspike]

now here's a smart man.

[alexhays]

wanna meet da wizzard

[with_my_pistola]

You win.

[xed_geek]

Patience. This is the universe telling you to calm down.
Or maybe your provider sucks big rocks.

[pavel_lishin]

Fuck the universe, it's not the boss of me!

[xed_geek]

Shhhhhh. It may hear you!

[russkiypenguin]

I had that issue through several generations of wireless routers. I finally bought a decent one for about 2x what I paid for the first two pieces of shit. Now I don't have any issues. Oh wait, I do if I use bitlord.

Basically, it seems like if I use a sharing client that tries to bypass firewalls it would tear the firewalls a new asshole. That's for the new one. I stopped using bitlord and now I have reliable connectivity and I can share a shit-ton.

Perhaps another person in the dorm is doing the same thing to the switch in your building?

[pavel_lishin]

Not dorms; apartments. And it's our own dedicated Cable line, I'm only sharing it with my flatmate.

[russkiypenguin]

I'd buy a new router and see how it does. If it sucks, return it immediately then bitch out your provider. If they don't respond, leave.

The pocketbook is the only thing these bastards understand anymore.

[pavel_lishin]

I don't think it's the router. First, we've had it for awhile, so I don't think it would just now start acting up. Second, uh, based on what eazyt said.

[absinthine]

yeah, I have no clue what any of you are talking about.

[pavel_lishin]

You're in good company.