Network/browser issues
Posted: 21. Mar 2010, 19:03
Hi, I've searched the forums, but didn't find my answer. I'm sure I'm not the only one who had this problem, so I'd be glad for any helpful link... However, many topics which seemed to solve a similar problem didn't help me at all.
Description:
1) Websites sometimes don't load in Firefox on Linux Mint and Sabayon Linux
-> It seems not to matter which site
-> Just checked on Mint, IPv6 is disabled in Firefox, don't know if that matters
2) Websites very often don't load in Google Chrome (everywhere) and Firefox (several Ubuntu installations)
-> Here it's heavily dependent on which site it is. for instance, Google's pages work well.
- I'm on a Windows 7 host now. On Windows XP and Windos Vista, I didn't have these problems
- I've tried several ways to stop this behavior... Disabling ipv6 in Firefox and Chrome, editing resolv.conf, etc.
- Everything works well on the host and on a different computer in the network (the Vista machine), so I don't think it's my network.
My guess is that it is something about ipv6, but disabling in Firefox doesn't solve it.
Another guess was DNS, but the same site is still affected more than once in a row. Reloading often helps.
Description:
1) Websites sometimes don't load in Firefox on Linux Mint and Sabayon Linux
-> It seems not to matter which site
-> Just checked on Mint, IPv6 is disabled in Firefox, don't know if that matters
2) Websites very often don't load in Google Chrome (everywhere) and Firefox (several Ubuntu installations)
-> Here it's heavily dependent on which site it is. for instance, Google's pages work well.
- I'm on a Windows 7 host now. On Windows XP and Windos Vista, I didn't have these problems
- I've tried several ways to stop this behavior... Disabling ipv6 in Firefox and Chrome, editing resolv.conf, etc.
- Everything works well on the host and on a different computer in the network (the Vista machine), so I don't think it's my network.
My guess is that it is something about ipv6, but disabling in Firefox doesn't solve it.
Another guess was DNS, but the same site is still affected more than once in a row. Reloading often helps.