Sometimes my router can't connect to random pages ( last one was bitwatch.com). Page is 'unreachable' until I restart my router. This wasn't problem, but few days ago I noticed it also blocks mining since deepbit.net was the 'blocked' page. Today same happened. I have routers firewall turned off, but this doesn't help. Do u have any idea what can I do to solve this?
What router? I highly recommend the D-Link DIR-655 or DIR-855 (I use the latter). Use DNS Relay and setup on your router to use a DNS that is not your ISP. Good options are:
Google DNS http://code.google.com/speed/public-dns/
8.8.8.8
8.8.4.4
OpenDns http://www.opendns.com/
208.67.222.222
208.67.220.220
I use Google DNS, but frankly, I wonder about their information gathering these days. OpenDNS is also very good and you do not have to sign up either, but they also may gather data [and you can actually use this data to monitor activity from your network which uses DNS, if you sign up for a free account]. They are both fantastic, but most of the time, I have found Google DNS to perform just a little better .... far better than Comcast most of the time in spite of the fact that they are out of the ISP network. Your router should cache by TTL anyway [or memory limits]. If your router does not have this option, then set it up individually on your mining machine, or setup a DNS of your own on one of your mining rigs [especially if you are running linux ... just install bind and learn how to configure it] and point the rest of your machines at it instead. OpenDNS does have a nice option to use the last known address for a lookup if it fails to find a current one ... thus often keeping you connected when you might otherwise not be.
I am just assuming the issue is DNS related, but it very well could be connectivity related. Perhaps your ISP is not multi-homed, or it is overloaded; a common problem with QWest DSL using MSN for instance ... which is why most of who I know moved to Comcast or Charter depending upon where they live.
I too have seen these communication errors every now and again and they are only a minute or two in duration and it is usually when Tycho was doing maintenance. There were some issues with growth awhile back, but I think Tycho has done a decent job of trying to balance the network [appears to be using a basic DNS load balancer which is why I was suggesting DNS ... your ISP may not be honoring the TTL as it should].