Ato_Zee wrote:
>>> So it looks as if *any* internet activity triggers this problem, and
>>> that
>>> it probably has nothing to do with Firefox per se.
>
> When internet connection dies on one machine but not another,
> see if the dead one can ping www.google.com both by
> name and dotted quad IP address.
> 209.85.229.106 (not sure if Google change this
> occasionally, but you get the idea, you can do the ping
> to get the IP address on the good machine)
> Next do an ipconfig /all on both machines and compare
> the results.
> Compare the hosts files.
> And one common problem is too high an MTU sdetting,
> there are free utilities to fix this problem.
I half agree.
Too high an MTU should not cause things to crap out, but it does,
because some upstream router or switch is mangling packet fragmentation
and defragmentation.
So its not a local problem, its a remote problem, that has not a local
FIX, but a local *workaround*.
Fixing a crash on the M25 is clearing away the bodies, car and human,
and cleaning and repairing the road surface. Driving across london, is a
workaround ;-)
> Usually when things go pear shaped I just restore
> the OS in under 5 mins from the original image, plus
> the differential image taken when things worked.
> You just select the differential image of appropriate
> date. It helps if the OS is on its own drive or partition,
> with data, emails, bookmarks, newsgroups etc on another.
I just go :-
#ifconfig eth0 mtu 1400
Takes about 10 seconds.;-)
However its not the only problem that can cause these effects. Sometimes
the routers NAT cache seems to get screwed. Rebooting the router and
the client PC's will fix that for a while.