I just added the DNS entries to my windows computer (which I have never worried about before since it has 1.5+ days cache) and noticed "Notepad must be run as Administrator"

Maybe that is why the file is being modified, wrong rights?

I'm wondering how all my computers keep getting the SETI servers hosts entries commented out. They can't connect in that state. Unless I notice the building uploads or the messages that no work can be retrieved because of pending uploads, I wouldn't have known to go check the hosts file again. I don't know whether it is Windows doing the deed of some antivirus program. I have Kaspersky on the Win7 machines and using Defender on the Win10 machine. Two different AV programs makes it unlikely that they both are doing the same thing. Unless Windows directs them to do that.

Seems strange that DNS is OK to the web pages but not the upload server ... Don't think this would be a client issue.

HP-Z400b
117812			08/02/17 9:07:08 PM	Project communication failed: attempting access to reference site	
117813	SETI@home	08/02/17 9:07:08 PM	Temp failed upload 16ap08ae.32309.4571.13.40.61_0_r1507416175_0: can't resolve hostname	
117814	SETI@home	08/02/17 9:07:08 PM	Backing off 00:02:34 on upload of 16ap08ae.32309.4571.13.40.61_0_r1507416175_0	
117815			08/02/17 9:07:09 PM	Internet access OK - project servers may be temporarily down.	

---

Thank you TBar I modified my host file in Windows Vista ultimate now I am connecting with no problem but I'm curious do I need to delete the modification on made to my host file after things return to normal? Thanks again

---

Thank you TBar I modified my host file in Windows Vista ultimate now I am connecting with no problem but I'm curious do I need to delete the modification I made to my host file after things return to normal? Thanks again



OOPS sorry for the double posting

---

I just added the DNS entries to my windows computer (which I have never worried about before since it has 1.5+ days cache) and noticed "Notepad must be run as Administrator"

Maybe that is why the file is being modified, wrong rights?

I can edit the Hosts file with Notepad with no issues on the Win7 machines. I discovered I can't with the Win10 machine which just updated to the Creators Edition. Still learning the differences between that and Anniversary Edition. I had to use PowerShell and Administrator permissions to edit and Save the hosts file on the Win 10 machine. Soon as I fixed the hosts entries for the SETI servers, my backlog of uploads cleared and I started getting tasks again.

What commented out my previous entries in the first place though?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

After a quick Search it seems bitdefender is one culprit.

After a quick Search it seems bitdefender is one culprit.

I'll have to do a Search on Kaspersky. Took a look at the Permissions on both the Win10 and Win7 systems. Only System has Write privileges. Had entries for Applications on the Win10 system which weren't there for the Win7 systems. But they didn't have Write privileges. So the mystery is still unsolved.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Glad for this thread. Got home to find my main cruncher out of GPU work, uploads all sitting there doing nothing.
Un-commented the entries in my Hosts file, and now I can upload & get work again.
As to why it was the main machine that had issues, and the slow one was still able to upload, no idea. Just the natural perversity of things.

Ah, just had a look at my old system's Hosts file- never got around to commenting out the addresses 12 months ago.

---

Grant
Darwin NT

I can't upload or see my stats!

Very soon now we will be out of Arecibo tasks. Is that all there is? Only BLCs from here on? At least they run fairly well with the CUDA Special App, especially the BLC02 types ;-)

Not too worried about the lack of Arecibo work. Plenty of GBT WUs to keep things chugging along.

---

Grant
Darwin NT

Hmm.
Threads are loading OK, but posting is rather problematic.

---

Grant
Darwin NT

Glad for this thread. Got home to find my main cruncher out of GPU work, uploads all sitting there doing nothing.
Un-commented the entries in my Hosts file, and now I can upload & get work again.
As to why it was the main machine that had issues, and the slow one was still able to upload, no idea. Just the natural perversity of things.

Ah, just had a look at my old system's Hosts file- never got around to commenting out the addresses 12 months ago.

So what are you entering in your hosts file that is getting commented out, if I may ask? Can you copy the relevants here?
Not sure why this would be in hosts rather than relying on DNS. What am I missing? Thanks

---

So what are you entering in your hosts file that is getting commented out, if I may ask? Can you copy the relevants here?

In the Hosts file I've got the server addresses there, so the system doesn't have to use a DNS to find what the address is to make contact.

Normally when BOINC contacts the servers it has to find the address using the DNS. It gives it the correct address for the relevant server so it can make contact. Having the address in the Hosts file it's able to make contact directly- no need to find out what the address is.
Of course with this method if the address changes, you loose the connection. Using the DNS, if the address changes it doesn't matter, the server finds out (eventually) what the new address is and passes it along when you next make a request to contact the server.

208.68.240.118 setiboincdata.ssl.berkeley.edu # upload server Oct 2016
208.68.240.119 boinc2.ssl.berkeley.edu # download server Oct 2016
208.68.240.126 setiboinc.ssl.berkeley.edu # scheduler Oct 2016

---

Grant
Darwin NT

As to why it was the main machine that had issues...

See the front page news.

So what are you entering in your hosts file that is getting commented out, if I may ask? Can you copy the relevants here?

In the Hosts file I've got the server addresses there, so the system doesn't have to use a DNS to find what the address is to make contact.
...

Thanks

---

As to why it was the main machine that had issues...

See the front page news.

Ref to my original post.
I knew that there were issues and why.
However one machine had issues, the other didn't.
One was using the DNS, the other still had the addresses there from a previous time.

---

Grant
Darwin NT

Ref to my original post.

At the time of your original post, the front page news hadn't appeared, so I doubt that you knew why the machine using public DNS was having problems.

Those "Results received in last hour" numbers look bad.
So....someone sees Smoke on some distant mountain, flips the breaker to the DNS Server, and then scurries off to their Safe space?
The last time this happened someone posted the DNS numbers and all was well, it's still fine here.
https://support.rackspace.com/how-to/modify-your-hosts-file/

208.68.240.118 setiboincdata.ssl.berkeley.edu
208.68.240.119 boinc2.ssl.berkeley.edu
208.68.240.126 setiboinc.ssl.berkeley.edu

Works for me.

Dunno how I missed this the first time through, but thanks to Grant. Sigh. Totally missed the context on that one ...
Now of course, once they get the DNS server working again and change their server addresses some months down the road, I'll be scratching my ... head ... wondering why I can't connect.
And considering my hosts file is ~600k (almost the limit) to filter out all the crapware sites ....

---

208.68.240.118 setiboincdata.ssl.berkeley.edu # upload server Oct 2016
208.68.240.119 boinc2.ssl.berkeley.edu # download server Oct 2016
208.68.240.126 setiboinc.ssl.berkeley.edu # scheduler Oct 2016

Tnx for this...worked for me too. Lovely to get rid of all those uploads in progress and finally DL some new tasks. I got 128 in one fell swoop...perfect :-) Though my Webroot AV had a thing or two to say about it, haha...

...Grete...

---

Humans may rule the world...but bacteria run it...

I was able to open the file -- but where do I make these changes in the file!