...
So it looks like no problems on either .13 or .18 from this side of the pond...
...

.13 has been responding to pings the whole way through, but was handing out zero length files (last night anyway).

Curiously, I don't see a lot of Windows 7 users commenting here... could that mean the Lazy DNS cache issue is addressed in that OS ?

Nope, I had the lazy DNS issue back when it was .13 working and not .18.

I just changed the hosts file on both the Mac and the Win 7 Quad and am back crunching on them.

I have .13 commented out on both machines until they clear up the problem.

---

Sutaru - I did as you suggested, but did not reboot - I just stopped BOINC, edited my HOSTS file, and restarted BOINC, and all my pending d/l came through!
Thanks for the idea....

And, after all this settles down, I will remove or comment out the added lines to avoid any future problems with reassigned IP addresses for BOINC, per some of the other comments...

Thanks to all for your help.

---

Nope, I had the lazy DNS issue back when it was .13 working and not .18.

I just changed the hosts file on both the Mac and the Win 7 Quad and am back crunching on them.

I have .13 commented out on both machines until they clear up the problem.

Macs too ? *sigh*

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

You mean, if BOINC have a 'DL break' of 5 min., I need to close/exit BOINC and start again? Maybe reboot of PC?

I mean you should be patient and let the computers do their jobs.

Putting things in the HOSTS file is permanent. It requires you to monitor your machines, and monitor SETI@Home for any changes.

Not putting things in your HOSTS file means the internet will deal with it without your help.

The exception is the Maximum TTL settings in the Windows Registry. That is to correct a Windows BUG.

---

The exception is the Maximum TTL settings in the Windows Registry. That is to correct a Windows BUG.

I'm sure it's considered a feature...

---

Grant
Darwin NT

I noticed something strange about this problem on my machines. All my machines with Crunch3rs 6.1.0 fixed themselves and are fine. Each of my machines with 6.10.18 needed to be restarted to finish their downloads a couple a few restarts. So the problem seems to be in the newer builds on my machines.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I had turned my i7 off for 3 hours when i had problems with the downloads. wathced a movie with the grand kids. low and behold when i turned it on ,I had work units running. maybe patience is what was called for. I only powerd up to read the forums, wasnt worried if i had anything running.

---

[/quote]

Old James

The exception is the Maximum TTL settings in the Windows Registry. That is to correct a Windows BUG.

I'm sure it's considered a feature...

It's all in how you conjugate the verb.

If it's in your code, it's a bug.

If it's in my code, it's a feature.

:-)

---

Curiously, I don't see a lot of Windows 7 users commenting here... could that mean the Lazy DNS cache issue is addressed in that OS ?

Well, my i7 running Windows 7 64 bit ultimately downloaded 1400 WU's. I say ultimately, since it took nearly 4 hours and more /flushdns's than I can count.

What I saw was that after a /flush, Boinc would d/l WU's for five minutes (I put a stopwatch on it to be certain; it was always 5 minutes, give or take 10 seconds), then roll right back into the error state. I'd have to halt d/l's, stop Boinc, do another flush, and start over again.

But, it DID work.............;)

I have Windows 7 64 bit ultimate also. Had to do a bunch of restarts.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I had one waiting to be downloaded sinve yesterday, turned off the machine last night, switched on the machine this morning and now have 6 having trouble downloading will wait and see what happens next. Tired ipconfig /flushdns got cannot flush the resolver cache, my Isp will not allow it.

---

I found that using the ReSchedule tool for changing GPU>CPU worked for my
Vista rigs.Having to do it a few times though.

Don't know why it works.

Dave

---

@ Ned,

I've been watching this thread, still without access to my main machines, and you've almost convinced me that it's all Windoze' fault - but not quite.

This story sounds like a very good description of the effects that one would expect to see with round-robin DNS and a TTL of 300 seconds:

What I saw was that after a /flush, Boinc would d/l WU's for five minutes (I put a stopwatch on it to be certain; it was always 5 minutes, give or take 10 seconds), then roll right back into the error state. I'd have to halt d/l's, stop Boinc, do another flush, and start over again.

But if that was the end of the story, wouldn't we expect to see that five minutes later, the downloads restart again of their own accord? (maybe only 50% of the time - sometimes it might be 10 minutes, sometimes 15, and so on - but it should have a good chance of restarting in due course). I don't think anybody has posted in this thread to report a spontaneous resumption of downloads after hitting the problem: if anyone has experienced one, please tell us about it.

It sounds the same as the discussion in Panic Mode On (18): there I reported a similar run of downloads followed by failure, but with no resumption after more than an hour. The odds against that are more than 4,000 to 1 if there's a true random re-resolve from DNS every 5 minutes. That's why I think there's a difference between BOINC's initial attempt to download a file (using DNS), and subsequent retries, using ?????

Tried ipconfig /flushdns got cannot flush the resolver cache, my Isp will not allow it.

This has nothing to do with your ISP. You probably have the DNS client service disabled, or stopped. Without a DNS client, you're not caching any DNS entries.

(You'll need administrator functions for this)

Go to Start->Run
Type "services.msc" without the quotes, press Enter
Scroll to DNS Client.
Double click on DNS Client.
Under the Startup type pulldown, put it on "Automatic".
Then click the Start button.
Click Apply.
Click OK.

You will now be able to flush your DNS using the ipconfig /flushdns command.

---

That's why I think there's a difference between BOINC's initial attempt to download a file (using DNS), and subsequent retries, using ?????

I was trying to compose exactly the same comment but Richard got the words so much better. I have amended the registry entries to force the 5 minute switch and can watch it happening in a cmd box by pinging. But I have one download that has been stuck for over an hour ATM and, no matter how many retries I force (or wait for) it remains stuck. It would certainly appear that the IP address (rather than the url) is being cached elsewhere within Boinc.

F.

---

Tried it still cannot ipconfig / flushdns still get DNS cache not being cleared. Just tried it again and it has cleared it however still cannot download wu's

---

I am curious why this only seems to effect my machines with 6.10.18 but none using 6.1.0?

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Haven't been able to download all day.
FLUSHDNS doesn't work.
Reboot doesn't work.
Upload works fine.
Report works fine.

Dust storm has made my nose run a continuous 4 minute mile all day.
Damaged newly-painted wall trying to hang a picture.
Motor mower on the fritz.

I'm telling you, it's a conspiracy!

---

Now report doesn't work.
And I appear to have been bitten by a spider.

Definitely a conspiracy [panic on]

---

Tried ipconfig /flushdns got cannot flush the resolver cache, my Isp will not allow it.

This has nothing to do with your ISP. You probably have the DNS client service disabled, or stopped. Without a DNS client, you're not caching any DNS entries.

(You'll need administrator functions for this)

Go to Start->Run
Type "services.msc" without the quotes, press Enter
Scroll to DNS Client.
Double click on DNS Client.
Under the Startup type pulldown, put it on "Automatic".
Then click the Start button.
Click Apply.
Click OK.

You will now be able to flush your DNS using the ipconfig /flushdns command.

While you are correct in what you say, this is not curing the issue, which is a problem at S@H end.

We shall have to do the usual, and wait for the crew to hit the appropriate pipe with a hammer.

---