Keep losing internet connection

Hello Computer Geniuses!

I don't know jack about computers. Nada. Zip.

My internet connection will stay up for an hour, then go down. Stay up for 5 min, then go down. etc. etc.

I regularly run both Adaware and Avira so I don't think it's malware or anything like that.

I tried doing a trace using the tracert command. It works fine while I'm connected but won't do anything when I'm not. Maybe it's not supposed to?

I've pinged my router ip address and my wan ip address. (don't know what either of those are but I pinged them!) Both work fine when I'm connected. When I'm not connected I noticed packet loss when pinging the WAN IP. For all I know that's normal. I'm on my 3rd router in less than 2 years and I'm really hoping I don't need to buy another one.

I also checked my event log. Problem is, there's nothing there that says "Here I am - I'm the problem!" which is what I really need since I have no idea what all that gobbledegook in my event log means. *sigh*

I am up trying to study for a test and I really just want to go to bed now (since it's 3 am and I have to get up for work in 3 hours) rather than messing with this ##*(*(!!! computer! :cry

I hope someone out there can help me (in plain English - lol)!!

 

Hi there, i'm going to explain to you how to flush your DNS Cache !

Clearing Your DNS Cache

Your DNS cache stores the locations (IP addresses) of pages you have recently viewed. If the location of the page changes before the entry in your DNS cache is updated, you will be unable to access the page.
If you are encountering a high number of HTML 404 error codes, you may need to flush your DNS cache. Once you clear your DNS cache, your computer will query nameservers for the new DNS information you require.
For more information about the HTML 404 error code, please visit the HTML 404 wikipedia article.
The methods detailed below allow you to remove old and inaccurate DNS information that may result in 404 errors.



Windows® XP, 2000, or Vista® Which ever system your using :

1. Open the Start menu.
2. Go to CMD Prompt.
   • If you do not see this, click the start button in Vista, search for "run" in the Search bar.
3. When the Run text box appears, type cmd :
4. Then when cmd box appears type into it ipconfig /flushdns
5. remembering to put the space inbetween ipconfig and the forward slash !
6. Press Enter or Return,then wait till cmd prompts o that the job is done, which should only take seconds, and your cache will be flushed.
7. Hopefully his may help you !!!!!!!

 

Tracert will report back each hop or router your request is sent thought to get to the entered ip address or website. If you don't have a connection then tracert will not get very far, this is to help identify where the problem is.

Packet loss usually means there is a problem.
I would check the network cables between your router and your modem.
I would also turn off your modem, then turn it back on as this can sometimes clear up issues.

Have you tried contacting your ISP about this issue yet?
If the modem is acting up replacing the router may not resolve the issue.

I deal with these logs at work and most of the time they rarely tell you what the issue is. However, I don't believe the issue is with your computer but rather another device so you probably will not see any logs on this issue.
When your connection is not working you may want to open a command prompt (start > run and enter "cmd") and enter 'ipconfig /all' to determine if you have an ip address assigned. You can also use 'ipconfig /renew' if your ip address is being assigned by your router (DHCP).
You can try clearing your dns cache like rustyjack talked about using 'ipconfig /flushdns' but since your getting packet loss when trying to ping your wan ip I don't think that's the issue.

 

Thanks Rustyjack, I tried that. However, I don't think the problem is my computer. My iphone can't connect to the wireless either, which tells me the problem is outside of my pc. Either my router, modem, or something like that.

 

Ok, so checked my cables. Other than loose connections, what would I look for though?
I've turned my router on and off umpteen times. It does always bring it back up.
I've talked to my ISP. They always blame it on my router. Always. I don't know how to check for a problem with the modem or with something else on their end. And they either don't know how or won't. I think the problem is on their end. Mainly because I went through this about 2-3 months ago, did NOT get a new router, yet the problem magically resolved itself. Worked fine for a few months and now here we are again. They tell me they can come out and look at the equipment, with the addendum that if it turns out to be my router, I'll get charged for the visit. Kind of a win-win for them since I'd have to believe whatever they tell me, even if it's not true. If the problem was my router, wouldn't it just stay down?

thanks for your help!

 

You just looking for cables that are either not connected are perhaps just loose enough not to make a solid connection. Just make sure everything is connected where they don't look loose.

As a test you could connect your pc directly to the modem removing your router from the equation. Make sure your software firewall is turned on. If you still experiencing the same issues then it's probably not your router.

After you change the cables make sure you run this command from the command prompt 'ipconfig /renew' this will request a new ip address from your modem because the one you had was from your router.

If you know the ip of your modem (can be obtained by performing an 'ipconfig /all' and looking for the default gateway while directly connected to the modem) you can typically enter it in a web browser to access it's web based configuration, however it may require a username and password. If you can identify your modem this page might help.

http://www.pcwintech.com/default-router-modem-passwords

Once you login just look for anything that talks about the modem's status, if you cannot connect to it or it states that the modem's status is offline/down when it's not working it may indicate the modem/ISP as the issue.