every 4-5 minutes internet will keep dcing.

just new router / modem 2 days ago and it's worked perfectly

its clear as day outside

they last for~3 mins or less

happen every 4-5

Need more information.
Could be isp, malware,virus.

I have lots of trouble with my isp. It drops like you sAY. But I know why mine does it.

Try pinging your isp. Or running a tracert to Jsp or google or yahoo.

IN CMD if your using a windows based os. Type this in with out the quotes.

C:\WINDOWS> "tracert yahoo.com"

C:\WINDOWS> " ping d2jsp.org"


http://help.expedient.com/general/ping_traceroute.shtml for more information.

This post was edited by thunderga on Jul 3 2011 06:45pm

how do i ping my isp?

i doubt i have any viruses i keep my shit clean / scanned every day.

See above edit for part of it. Access your router to veiw your isp adresss. It will be your Primary DNS numbers. That will be a IP address as well.

This post was edited by thunderga on Jul 3 2011 06:48pm

saying 1 * * * request timed out

your not connect to the net at all by what you posted. I would restart router/pc/radio/modem what ever you have. Then retry.

Here is my tracert to jsp.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Chris>tracert d2jsp.org

Tracing route to d2jsp.org [208.110.65.133]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1 this is to my isp radio tower
2 30 ms 18 ms 39 ms 174.78.240.1 my isp to the rest of the net.
3 146 ms 54 ms 29 ms COX-70-169-216-169-static.coxinet.net [70.169.21
6.169]
4 23 ms 16 ms 24 ms mtc3dsrj01-ge701.0.rd.ok.cox.net [68.12.14.43]
5 31 ms 34 ms 24 ms 68.1.2.119
6 47 ms 51 ms 46 ms 10gigabitethernet4-4.core1.chi1.he.net [184.105.
213.118]
7 58 ms 56 ms 61 ms 10gigabitethernet1-1.core1.mci1.he.net [72.52.92
.2]
8 59 ms 59 ms 46 ms 10gigabitethernet1-1.core1.mci2.he.net [184.105.
213.2]
9 50 ms 59 ms 59 ms wholesale-internet-inc.10gigabitethernet1-3.core
1.mci2.he.net [216.66.78.90]
10 59 ms 49 ms 54 ms 69.30.209.7
11 59 ms 49 ms 56 ms web.d2jsp.org [208.110.65.133]

Trace complete.

Here's a few steps that I could suggest doing - as a traceroute is good to do, it doesn't solve problems, only shows your routing to a specific network.

If you're DCing every 2-3 minutes, you could try doing some of the following steps;

1) Directly connect to your modem - might need to give the modem a restart so it'll update with a new ghost mac address and give you a IP address
2) Once you've connected directly to the modem, Go to Start -> Run -> type in cmd -> type in: ping 4.2.2.1 /t - this'll ping a military DNS server
3) Look for occasional drops - if you're getting "Request timed out", you're having bad hops/internet is completely disconnecting for that instance

If you don't receive any drops in MS, go ahead and re-hook up your router (I'm assuming you're directly connected to the router via ethernet and not wireless) and issue another ping to 4.2.2.1 (with /t so it'll continue), and monitor it for a while - if you're receiving loss/drops, it pinpoints issues down to your router.

As another step, I'd recommend using a different computer as well to see if it's having the same problem - this is due to a possible nic card and or wireless device on the computer you're currently connected to might be bad and or outdated - it has a potential to drop connection.

If you're wireless, I'd recommend directly connecting to the router and or modem to give these tests as a wireless connection isn't usually extremely stable.

Personally, I just had this issue with one of the PC's on my network; The computer would go online and it'd disconnect rapidly at different times then it'd come back online eventually - it was a setting in my router I forgot to change, which was called "WPS" - I had to disable it since it was interfering with my WPA2 security password.


These are just a couple steps to going about in troubleshooting your network, sometimes a traceroute will work if you're appointing it towards your ISP and they're wanting it to forward to a system administrator which usually doesn't happen if other users isn't have the same problem - don't fix what isn't broke.

Traceroute's will show if a router/network is having issues and it'll start itself out ( * * * ), it won't respond to the echo response or it'll have a high latency/route you elsewhere. This doesn't imply to all networks, some networks have Echo Replies turned off by default or for security reasons so you'll get the *'s regardless but the network could still be online.

As you'll see on a traceroute of mine directly from my router (ssh), I get a request timed out at the very start due to my isp's local server has echo replies disabled



As you'll see it's rather long due to going through 3 local networks and dns servers/routers - eventually to d2jsp's server.

Not to be picky, however - thunderga: 1 <1 ms <1 ms <1 ms 192.168.1.1 this is to my isp radio tower - 192.168.1.1 is your local router, not modem; That's the router at your house - from reviewing your network, you don't have a very good ms to your local node at all, it's rather bad in my opinion. I'd further look into that and determine where your local node is -- usually you'll have a 1-8ms+ to a local node, you're having 18-39 range, yikes.

Here's a example ping tests to 4.2.2.1 which is public military DNS servers



As you'll see, my network is decently stable, I could post a huge output but it'll be generally the same since I've monitored it many times before. Don't mind the root@knight, it's linux.


Get back to me with some more information as to if you're wireless, updated nic card/wireless drivers, connected to a different pc and attempted those steps, etc. Eventually - if all else fails and you're having serious connection issues and it's not a local network problem, you'll need to get into contact with your ISP and they'll be able to check your modem SNR/signals and determine if you're having a outage frequently.