cant load webpages after computer is left on [moved from Windows]

[dragonember]

I tend to leave my computer on at night so i can listen to music, receive IM's convert stuff, burn large projects, etc etc etc. However, whenever I leave this computer on all night, when I get up in the morning I cant load webpages, download updates for any programs, BUT all of my IM screen names are still on and I can send and receive messages. AND if I start tor, and make firefox go through tor, then I can load webpages, but as soon as I turn tor off, firefox again cant load the page. Rebooting the computer fixes the problem and I assume disabling the ethernet connection in control panel then re-enabling it would have the same effect, but why is this happening?

[justpassingby]

Some problem with the DNS server maybe ? When you fail to connect to the internet with firefox do the following :

Go to start => run and type cmd

type : ping www.google.com
and tell us the result

type : ping 64.233.183.99
and tell us the result

If pinging the ip address works but not pinging the domain name then contact your ISP and ask them what their DNS server is. Then go to control panel => network connections. Right-click your network adapter and click properties. Select TCP/IP internet protocol and click properties. Enter the DNS server ip under "use the following DNS server".

In the dos command prompt (run => cmd), type ipconfig /all. What are the lease obtained and lease expires dates ? If it's only 24 hours or less it may be your problem. Typing ipconfig /renew should renew the lease without needing to restart the computer or disabling the ethernet connection (it will actually restart the internet connection but the interruption should be very short). Setting the DNS server manually could solve the problem.

[dragonember]

My assumption: if it was that the lease was expired is that my IM screen names would be kicked offline as well. i can send and receive files and IM's, just cant update any programs or load web pages (unless I use a proxy to load the pages) Im only able to post this because Im going through tor. when I tell firefox to access the internet directly it cant find the pages.

"ping request could not find host google.com Please check the name and try again."

however, pinging the IP worked properly, so it must be a DNS issue.

Lease was obtained the 21st and expires the 23

I get on the internet through my schools connection. I live in the dorms at a state university so I have no idea what ISP they use.

My suitemate said this happens to him too, but i don't recall this happening when I leave my laptop on all night then try to use it. If i remember correctly everything loaded fine. Of course I always run linux on my laptop (ubuntu 6.06). I wonder if it has something to do with windows and timeout issues with DNS servers.

[justpassingby]

You can probably still surf the net without tor if you enter the ip address of the website in the url instead of the full name. Try http://72.52.136.82/ for techsupportforum for instance.

There's no problem asking the school's network admin which ISP they use.

Here's more information about DNS errors :

DNS lookup fails. Most of the instances of Fx failing to load a webpage that can't be attributed to a misconfigured firewall are probably due to a failure by the ISP's DNS nameservers to resolve the hostname that one wishes to access. This could be caused by actual failure or misconfiguration or overloading of your ISP's DNS nameserver. When such a failure is intermittent, overloading of the server is a likely cause. Many broadband providers have experienced such intermittent failures lately. Examples are OptimumOnline, Verizon, Comcast, RCN, Roadrunner. Perhaps too many people have been signing up for broadband lately, and ISP's are running out of DNS server capacity.

Sometimes, you will experience long load times if your DNS cache becomes corrupted or the address of your ISPs DNS server changes. It's always worth it to run: Start>Run> ipconfig /flushdns


1) In Fx's URL field (the space into which you type a hostname) type http://www.google.com and hit <Enter>. If Fx can't load the Google homepage , then there is a problem. Now, clear the URL field, type http://64.233.167.147 and hit <Enter>. If Fx can load the Google homepage now, then the problem is failure of DNS lookup. If you have trouble getting through to Google but you can consistently reach it using the IP address, the problem is probably the DNS. DNS service may be intermittent. With an intermittent problem, it takes repeated tests to be sure. The DNS nameservers are there to convert the easy to remember hostname "www.google.com" to the IP address "64.233.167.147" that is actually used by the servers and routers on the Internet. If the nameserver is dead or nonresponsive, "www.google.com" will get you nowhere but "64.233.167.147" will bypass the nameserver and get you to Google more directly. You can also enter the command "nslookup www.google.com" on the command line, and see whether nslookup tells you that the request timed out ("cannot find server"). "Checking DNS issues "

2. Call your ISP tech support and ask them whether any of the DNS nameservers that your machine automatically connects to through DHCP are experiencing problems (overloading or failure because of Internet attacks) and if so what they are planning to do about it. If you can't get satisfaction from them, discard their DNS nameservers and go to step 3.

3. Rather than using your ISP's DNS nameservers, use stable, reliable and non-congested alternative nameservers such as public nameservers or those of a major university nearby. A list of public nameservers can be found here: http://www.broadbandreports.com/faq/7472 . Choose two from the list that are nearby. If you use a router add the DNS servers there.

4. Treewalk :"You need TreeWalk DNS if: (ONLY Works for Windows)
1. Accurately (resolving) Web Sites is a problem
2. You wish to capture or debug DNS routing Data
3. You want to custom configure DNS settings and Servers
4. You'd like faster repeat visits to Sites (cached lookups)
5. Your Internet Service Provider's (ISP) DNS Server is slow or offline
6. You have problems with your wireless or satellite Internet connection"
Download it here: http://ntcanuck.com/

5. You can also add the IP address of sites you visit frequently to your HOSTS file. (This will also help speed up updates such as your Antivirus.)
If you do not know the IP address try http://www.samspade.org


Here is a way to show that the problem is due to DNS and not just FF.
1. Find your host file in c:\windows or
c:\windows\system32\drivers\etc depending on your version
2. add a line for one of your favourite sites, like
140.211.166.9 forums.mozillazine.org
3. Save the hosts file and restart FF.
4. Go to that site. If you can now get there on the first try, you know that DNS is at fault.

Source : http://forums.mozillazine.org/viewtopic.php?t=258042