Jump to content
Posted 05 January 2011 - 12:21 AM
Posted 06 January 2011 - 05:19 PM
Posted 06 January 2011 - 06:22 PM
Posted 06 January 2011 - 09:03 PM
Edited by mommafrick, 06 January 2011 - 09:04 PM.
Posted 07 January 2011 - 01:00 PM
It should have worked on wireless, but it's probably not related to your problem. I just tell people to go ahead and do that so it's a "fresh start" when they go to troubleshoot things.
The first one flushed the DNS Resolver Cache successfully, but Release and Renew said, No operation can be performed on Local Area Connection while it has its media disconnected. I wish that I knew more about this stuff. I'm connected to the internet wirelessly - is this why they didn't work?
Posted 08 January 2011 - 01:56 AM
Posted 08 January 2011 - 05:10 PM
Posted 09 January 2011 - 02:28 PM
Posted 09 January 2011 - 09:37 PM
The only reason I could see right now is a problem with your modem/router or a local PC firewall. It not even getting the router IP (192.168.1.1) eliminates your ISP and PopCap's servers.
It is now working with Internet Explorer. I did another flushdns, shut down computer, unplugged modem and router, waited, then started them again. So it worked, but it doesn't help me in the future if I don't really understand what happened. What does unplugging modem and router do to them? And what may have been messed up to make that work? (If there are many reasons, what do you think the top two are?)
1 4 ms 4 ms 4 ms dslrouter [192.168.1.1]That indicates the connection is making it to your router, and then the server/router it connects to past there is
2 34 ms 38 ms 34 ms L100.LSANCA-DSL-08.verizon-gni.net [220.127.116.11]This is most likely a local DSL center within a few miles or so of you. This is most likely what everyone that's on Verizon in your area connects to before actually accessing the "full" internet. More things come into play - but just keeping it simple.
All traceroutes should start out the same way. The first few hops are normally the same. Although they can be different and still work correctly, if the second hop for a working and unworking site are different, then that points to the problem being with your internet provider and not the website itself. Although all "request timed outs" are not bad, they can be used to tell were the connection is being dropped "down the line". So if it shows verizon as the last hop before dropping out, then you can assume the problem is with Verizon. Although that's not always the case, it is about 80% of the time. Because it wasn't even getting to your modem, then that shows it was a problem with your modem/router or the IP given (although I was able to rule that out when you posted the first traceroute due to receiving the correct IP).
I looked at google now and it looks similar, of course. My old tracert for popcap didn't even have the DSL modem number in the first line. Does that mean the wireless router didn't even make it to the modem? And why would it for some, but not others?
As noted before the first hops are the same, however because the servers are located at different places, different routes are taken. It's like going to a local store or going to one 200 miles away. You start out the same by leaving your house and going down the road and you may even make a few more turns the same, however before too long you will go in different directions. Were Google ends, hop 11, is the server Google.com is hosted on for you. The first "request timed out" in the PopCap traceroute, is were we can assume the PopCap server is. Although it may be 1 or 2 more past that.
Now, I'm looking closer, and I was wrong about it all being information from popcap, right? It talks to verizon, then are the LAX1, LAX7, LAX15 looking for a network out? Lines 7 to 13 of popcap are things that don't even show up in the google list, and the popcap seems to quit before my computer was ready for it, but the google list just ends. Hmmm...
Edited by NpaMA, 09 January 2011 - 09:45 PM.
0 members, 0 guests, 0 anonymous users