Reply from 10.15.208.2: Destination host unreachable

That means your ISP has their local routers programmed not to allow PING requests in their network and to the Internet. ISP's like EarthLink have started blocking these types of commands to reduce traffic and block Worms and Trojans from spreading.

It can also mean your ISP has connections to other networks that are down and not working. Those types of problems are usually fixed very quickly.

Try the TRACERT command, but it is not likely that it will work either.

However, you know that your ISP's DNS server is resolving the URL correctly.
Your system should be able to connect to the server and upload results. As you can read and post to this message board, the Internet path from you to the servers is working.

The error messages you are getting are all generated by the BOINC Manager and are not messages received from the servers. The BOINC Manager is not able to connect to the server for some reason.

If you have a software FireWall, go into its setup and look for any Berkeley URL's or IP addresses and see if they are being blocked. They should have permission to connect to those sites. The setiboinc.ssl.berkeley.edu resolves to two different IP addresses 128.32.18.173 and 128.32.18.174 and it is possible your firewall is blocking one of those IP addresses for some reason. The URL resolving to its alternate IP address might be causing your firewall to block the response, as it has been "trained" to expect the other one.

[Edit Add]
What software Firewall are you using?

If you disable the firewall, can BOINC connect?

Where was boincview showing this?

You want a windows user to type in a command shell? :<

Actually, on anything this side of 98 (I think), even environment variables don't need to be typed in the command shell. That said ...

There is a TZ environment variable, which generally takes the form of TZ=EST5EDT (depending on where you're located, of course). It's not a default variable, though - it has to be added manually. Also, there's no "export TZ" functionality, so it's up to the applications that want it to use it. BOINCMGR seems to ignore it, even if set.

For whatever it's worth...

Actually this whole subject is one of the major problems I have with BOINC, it tries to "delay" things happening, when from basic Queuing Theory that is not what you want to do in the name of efficiency. You want to get as much through the pipe as fast as you can. It is not the objective of Queuing Theory and computers to play fair and waste time on the chance that someone else might need to use it. This "fair use" actually wastes bandwidth and time. There is no provision in Queuing Theory for being fair!
.....snip snip.......
After writing this, I am starting to wonder if they have taken Queuing Theory out of Computer Science and System Design courses, or worse, turned it into a "Feel Good about it" course.

Being predominantly a penguin hugger (Linux) I don't know if something like this would work in Windows, and I don't have any Windows machines here at the moment to try it. In Linux you can start a new shell and set the timezone that's used just in that instance, and doesn't effect the rest of the system....

export TZ="utc" ; boincmgr

... for example. Don't know if something similar could be implemented in the wonderful world of Windows or not.

I had the exact messages you put up. I do not have dial up. All I got was I have a sorry router. I had a Bellsouth Westell modem. Can't change. US Robotics 8514 serving 5 computers. I thought US Robotics was pretty good. The computers can download workunits but not return them properly. I got so many workunits trying to return that my internet connection was pretty much cutoff. I couldn't connect to anything on internet. If my equipment is so bad then would some people send me their equipment so I can continue to contribute. I had to stop the network connections within my home network.

If what I say is so bad why was it mentioned as problem in dev mail list by those who hate me so.

I just allowed BOINC to work and my network stopped responding. It was not acting like it should of. The only messages I get are scheduler messages of http 500 server error. Your ignorance is showing.

Ya know, why is it that there are people, who have a whole hell of a lot more computers attached, running through a network, crunching happily, reporting work, not bitching about this??? You say u have 5 computers, yet you have hardly over 12k credit, and BOINC stopped your network access? I'm no network person, nor do I care to be, but when I can see several others running BOINC just fine on 10 computers or more, on a network, with no problems, I think your full of crap. Your best solution, as many have pointed out, but your too dense to listen, is to get a new router, and fix the problem on YOUR end.

Reading your posts gives me more than a headache, I need a beer now.

Jeremy

....

....

....
You are too happy to support substandard program.

I see NOTHING "substandard" about BOINC....

All I have been doing is install connect and let it run.

YEP! That's right, install it, start it and let it run. Who knows better how BOINC is to run than the devs? You know? As Tony mentioned in a previous post, we have gone over this in at least 2 other threads. You attitude that "I'm right and everyone of you are wrong" is not going to get you any sympathy, let alone help.
---rest cut----

I have a defined set of things I would like. They are based on the fact that the scheduler says things that are wrong. The answer given indicates it's too hard to do what is right. John can admit that the computer is overcommitted isn't correct most of the time. The biggest issue is the 2 times correct rate rule. You probably never had heard from me if that one rule wasn't instituted. It's annoying that I can't controll what goes into cache. I wanted to volunteer time to a few projects. I can't stand something is accepted as normal that states something that is obviously wrong.

The defined set of things that you would like is worthless crap. The scheduler is correct but you are too stupid to understand it, or too pig-headed to listen to what 100 people have been telling you, for weeks. Nobody cares if you can or can't control what goes into cache, or if you want to volunteer or if you just go away (actually, most of us would prefer you just go away). The things that are accepted as normal are only "obviously wrong" to your deranged, mentally ill little mind. Everyone else here understands this but YOU! If you are the ONLY person on the planet who believes something, then here's a hint - YOU'RE PROBABLY WRONG! Your constant verbal flatulance on these boards is accomplishing nothing.

The scheduler DOES have problems; they are minor ones; they are being worked on; they are NOT the ones you are inventing out of thin air. EDF is not an "error", and "overcommitted" isn't either. BOINC does not do "DOS attacks" on your private network with the broken router. But maybe that will be the factor that finally gets you to uninstall it and go back to running something you can actually understand, like Solitaire.

Have a nice day.

I like normal mode and error mode.
but that is not what this thread is for. Do you know how I can make it so only one computer caches work units for other computers and then that one computer returns the results.

You don't. This functionality has been discussed by the project staff, and some initial brainstorming was done, but they have other pressing matters that demand their immediate attention. It may get added at some indefinite time in the future, it may not. A lot depends on whether or not a.) a proposed design can be agreed on (by the project staff) that addresses the security concerns that prompted the initial design decision that each computer must communicate with the project(s) server(s) on their own to fetch and return work, b.) someone experienced with the BOINC code has the time, ability, and desire to code it up, and c) the code meets the approval of the staff for inclusion in the BOINC code-base. BOINC will not do this now, nor is it likely to do so for quite some time (if ever). If lack of this function hampers your participation in BOINC projects, I am sorry. There is nothing that almost everyone that posts here can do about it. The few posters that *can* are tied up working on other things at this time. Perhaps you could make more productive use of your time participating in another project (d-net comes to mind, with its 'personal proxy').

I guess the other question is why Boinc is not working correctly when trying to upload all the results at once. It goes only two deep the first two upload and go past 100% and then the next one starts while the other ones are still going.

I've never seen it work on more than 2 at a time, and after extended outages, I usually have a bunch to go back. And, believe me, I watch this closely.

The '>100%' issue on uploads is a known bug. It is being worked on.

From another post of yours:

An apology would be nice. Maybe a little help would be even nicer.

People have tried to help you. You, simply, just choose not to heed what they tell you. You just keep on whineing about whatever it is that bothers you today. For instance, take this thread. You described your problem when you started this thread (though you WERE more than a little trollish with your thread title (BOINC officially DOS'd my network)). As people chimed in, you rejected all their suggestions. You even admitted your router is sub-standard

The router doesn't switch lines too well. So if one computer is doing something it affects the other computers eventually.

So, somehow, in your tortured logic, you maintain that your difficulties are still 'all BOINC's fault', even though you have crappy equipment?

Nah, you are a troll. And you will get bugger-all of an apology from me.

I like normal mode and error mode.

Yes, we're well aware of that.

The goal is to never report work late. You'd be more unhappy if your results were routinely discarded because they were late.

Simple suggestion: set "connect every 'x' days" to one.

Please answer relevant question and not continue off topic. People at boinc don't like the truth. If the truth offends somebody let's call it something else.

So How do you cause only one computer to communicate with main servers and not cause DOS?

You've been complaining about Earliest-Deadline-First mode. I quoted your statement on that topic. Setting the connect interval to 1 day avoids EDF.

So let's just pick any old algorithm and who cares if what it says is correct or not. It is bad style to not be able to work in a standard operating mode. Everything that Boinc is supposed to aid is broken because everyone has to be held to a little rule you made up for dial up. There should be a cache setting. There should be a connect rate. WHEN MY COMPUTER IS NOT OVERCOMMITTED IT SHOULDN'T SAY SO. I WANT THREE DAYS OR WHATEVER I SET WORTH OF WORK ON COMPUTER ANd ONLY THAT AMOUNT. I DON'T WANT A RANDOM SET OF WORK UNITS AT ANY GIVEN TIME. I SHOULD KNOW OR PREDICT WHAT THE SCHEDULER IS GOING TO DO FOR ANY DATE IN FUTURE.

Do you have anything helpful to tell John or is ranting and raving all you know?