I finally took the time today to systematically trouble shoot the one
machine that has been refusing to run BOINC.  Actually it would
install BOINC and had installed seti several times as well. It would
then download the headers for the WUs and then attempt to download the
WUs.  It would start the downloads, but each and every one would fail,
nor could it send finished WUs.

As the other machines are working and they are *nearly* identical in
configuration I figured it had to be something *relatively* simple.

I do run multiple layers of security with a lot of IPs and IP ranges
blocked in addition to a number of other security methods.

I had tried turning off the fire wall, and several other items, but
BOINC had been having problems and trying to fix one thing when
something else may be a contributing factor can rapidly become a
losing battle.  It can become a down hill battle with the user adding
to the problem.

The problem did turn out to be a combination of items from several
sources, both hardware and soft ware.  Once I recognize the main
culprit it stood out like a sore thumb.  How it ended up being changed
I don't know, but the system refused to let that computer connect to
an http source but that had been camouflaged behind several other
items.  

At any rate it downloaded a week's worth of WUs and is happily
crunching away.

Thanks to all those who had offered suggestions and help.

Roger Halstead (K8RI & ARRL life member)
(N833R, S# CD-2 Worlds oldest Debonair)
www.rogerhalstead.com