Horacio - Thanks for the input and I learned something - Unfortunately flushing dns did not solve the problem. Rebooted the modem and router - again no change.
Can you access the forums or any other Einstein pages from that host?
If that doesnt work, use the ping command (from the command prompt) to the einstein.phys.uwm.edu domain to see if what it says.
If the ping command is not able to resolve the IP address then try it with this IP 129.89.61.70.
If the IP address is resolved but it fails getting answers then try to use the tracert command to the same domain to see where the conection stops...
If you dont know how to use ping and tracert commands just open a command prompt session and type the command followed by a space and then the domain like ping einstein.phys.uwm.edu or the IP address ping 129.89.61.70
Of course all this should be made on the host that doesnt work, but it may help to run the same in one of the other hosts to see if there is something different. Post the outputs if they doesn't make sense to you, you can do a right click on the command propmp window to open the menu that will allow you to select and copy all the text displayed to be pasted here... you can edit the output of tracert to delette your own IPs from you network if you are unconfortable showing it openly...
Nothing of this will fix the issue, this is just to gather more info about what is happenning so please share with us the results so we can try to find a way to fix it.
EDIT: other guess...
Is that host using a proxy server for BOINC? if yes, its the same as the others? (If you are not sure look in the event log after restarting BOINC, you will see a message saying that you are using a proxy if you are, IIRC it says nothing if not or in the best case it says explicitly that you are not using a proxy)
Sorry took so long to get back - been out of town. Did the Ping test and could not copy while this is what it reported:
Pinging Einstein.phys.uwm.edu [129.89.61.70] with 32 bytes of data:
Reply from 129.89.61.70: bytes=32 Time=29ms TTL=54
Reply from 129.89.61.70: bytes=32 Time=22ms TTL=54
Reply from 129.89.61.70: bytes=32 Time=24ms TTL=54
Reply from 129.89.61.70: bytes=32 Time=21ms TTL=54
Ping statistics for 129.89.61.70:
Packets: Sent = 4, Received = 4, Lost = 0 (0 % loss),
Approximate round trip time in milli-seconds:
Minimun = 21ms, Maximum = 29ms, average = 24ms
The event log notes: Not using a proxy.
Balance of Event log looks ok Starting BOINC ... version 7.0.28 for Windows_x86_64, etc.
Only thing of note - Started upload ...
Temporarily failed upload ... : transient HTTP error
Backing off 5 Hr ...
Started Upload (next wu)
Project communication failed: attempting access to reference site
The 2 things noted were 1) HTTP error & Project communication failed: attempting access to reference site
Thanks again Horacio for the education - never knew how to perform the Ping Test.
As shown by the ping the TCP/IP network communication is working and the DNS is also working, so the only thing that seems to be failling is the http protocol but this makes no sense if you are able to contact with other projects...
Unless the http protocol is failling only when it tries to talk with Einstein (which is as weird as be deaf only when trying to hear a certain person...) So the last question is: are you able to browse this forum or any other Einstein's page from that host?
If yes, then im finally out of ideas, and if it were my host I'll be thinking in a full reinstall of the OS... if not then there is still some hope as Im sure it has to be some way to fix a "defective" http protocol without reinstalling the whole OS...
Other than that, the only thing we have not talked in this thread is if you have checked for viruses, malware, adware, etc. and also if there is something that may have changed in that host (like the upgrade or install of anything else that is not suppossed to be related)...
Yes can navigate at Einstein through all the functions - Your Computer, Your account, etc. Your thoughts confirm mine - Start from scratch - lay down the Operating System, reload the software and see what happens.
About every 18 months I reload the operating system and reload the software because the system becomes so slow from others down loading unwanted tracking software and other none desirable entities. It is about that time.
Thanks for your help - I'll post what happens after the reinstall.
I also share your thoughts - weird - have no idea the cause of my problem - again thanks for your help and education.
Balance of Event log looks ok Starting BOINC ... version 7.0.28 for Windows_x86_64, etc.
Only thing of note - Started upload ...
Temporarily failed upload ... : transient HTTP error
Backing off 5 Hr ...
Started Upload (next wu)
Project communication failed: attempting access to reference site
The 2 things noted were 1) HTTP error & Project communication failed: attempting access to reference site
Please have a look at this Seti thread and post in the fuller event log results.
From my reading and i may be wrong here -
Do you download E@H tasks then complete them - but can not upload them?
If yes - I think i would look closely at any anti-virus / firewall software and see if they are logging errors.
It has been resolved. Modified the config file as identified in the thread mentioned and the problem was resolved. Now, can get back to number crunching.
Thanks AgentB and to all others that helped. Your efforts and contributions were very much appreciated.
Now, the weird thing here is this: Setting cc_config.xml to let BOINC work with HTTP 1.0 instead of the normal HTTP 1.1, means that something at your ISP changed. Which means that the other machines on the same network should have the same problem.
Well, that is, if you're not running something like Apache on this one machine only. ;-)
Now, the weird thing here is this: Setting cc_config.xml to let BOINC work with HTTP 1.0 instead of the normal HTTP 1.1, means that something at your ISP changed.
Well i´d say something is interfering with http 1.1 and the usual suspects are client firewalls and content filters...maybe a network connectivity issue. Need to view the logs to take it further.
Horacio - Thanks for the
)
Horacio - Thanks for the input and I learned something - Unfortunately flushing dns did not solve the problem. Rebooted the modem and router - again no change.
Thanks for the suggestions.
chuck
Patrick - The computer's host
)
Patrick - The computer's host file is as shown in your message. Nothing else.
Thanks for your input.
This is really
)
This is really weird...
Can you access the forums or any other Einstein pages from that host?
If that doesnt work, use the ping command (from the command prompt) to the einstein.phys.uwm.edu domain to see if what it says.
If the ping command is not able to resolve the IP address then try it with this IP 129.89.61.70.
If the IP address is resolved but it fails getting answers then try to use the tracert command to the same domain to see where the conection stops...
If you dont know how to use ping and tracert commands just open a command prompt session and type the command followed by a space and then the domain like ping einstein.phys.uwm.edu or the IP address ping 129.89.61.70
Of course all this should be made on the host that doesnt work, but it may help to run the same in one of the other hosts to see if there is something different. Post the outputs if they doesn't make sense to you, you can do a right click on the command propmp window to open the menu that will allow you to select and copy all the text displayed to be pasted here... you can edit the output of tracert to delette your own IPs from you network if you are unconfortable showing it openly...
Nothing of this will fix the issue, this is just to gather more info about what is happenning so please share with us the results so we can try to find a way to fix it.
EDIT: other guess...
Is that host using a proxy server for BOINC? if yes, its the same as the others? (If you are not sure look in the event log after restarting BOINC, you will see a message saying that you are using a proxy if you are, IIRC it says nothing if not or in the best case it says explicitly that you are not using a proxy)
Sorry took so long to get
)
Sorry took so long to get back - been out of town. Did the Ping test and could not copy while this is what it reported:
Pinging Einstein.phys.uwm.edu [129.89.61.70] with 32 bytes of data:
Reply from 129.89.61.70: bytes=32 Time=29ms TTL=54
Reply from 129.89.61.70: bytes=32 Time=22ms TTL=54
Reply from 129.89.61.70: bytes=32 Time=24ms TTL=54
Reply from 129.89.61.70: bytes=32 Time=21ms TTL=54
Ping statistics for 129.89.61.70:
Packets: Sent = 4, Received = 4, Lost = 0 (0 % loss),
Approximate round trip time in milli-seconds:
Minimun = 21ms, Maximum = 29ms, average = 24ms
The event log notes: Not using a proxy.
Balance of Event log looks ok Starting BOINC ... version 7.0.28 for Windows_x86_64, etc.
Only thing of note - Started upload ...
Temporarily failed upload ... : transient HTTP error
Backing off 5 Hr ...
Started Upload (next wu)
Project communication failed: attempting access to reference site
The 2 things noted were 1) HTTP error & Project communication failed: attempting access to reference site
Thanks again Horacio for the education - never knew how to perform the Ping Test.
chuck
Well...Im almost out of
)
Well...Im almost out of ideas...
As shown by the ping the TCP/IP network communication is working and the DNS is also working, so the only thing that seems to be failling is the http protocol but this makes no sense if you are able to contact with other projects...
Unless the http protocol is failling only when it tries to talk with Einstein (which is as weird as be deaf only when trying to hear a certain person...) So the last question is: are you able to browse this forum or any other Einstein's page from that host?
If yes, then im finally out of ideas, and if it were my host I'll be thinking in a full reinstall of the OS... if not then there is still some hope as Im sure it has to be some way to fix a "defective" http protocol without reinstalling the whole OS...
Other than that, the only thing we have not talked in this thread is if you have checked for viruses, malware, adware, etc. and also if there is something that may have changed in that host (like the upgrade or install of anything else that is not suppossed to be related)...
Hiracio, Yes can navigate
)
Hiracio,
Yes can navigate at Einstein through all the functions - Your Computer, Your account, etc. Your thoughts confirm mine - Start from scratch - lay down the Operating System, reload the software and see what happens.
About every 18 months I reload the operating system and reload the software because the system becomes so slow from others down loading unwanted tracking software and other none desirable entities. It is about that time.
Thanks for your help - I'll post what happens after the reinstall.
I also share your thoughts - weird - have no idea the cause of my problem - again thanks for your help and education.
chuck
RE: The event log notes:
)
Please have a look at this Seti thread and post in the fuller event log results.
From my reading and i may be wrong here -
Do you download E@H tasks then complete them - but can not upload them?
If yes - I think i would look closely at any anti-virus / firewall software and see if they are logging errors.
AgentB, It has been
)
AgentB,
It has been resolved. Modified the config file as identified in the thread mentioned and the problem was resolved. Now, can get back to number crunching.
Thanks AgentB and to all others that helped. Your efforts and contributions were very much appreciated.
chuck
Now, the weird thing here is
)
Now, the weird thing here is this: Setting cc_config.xml to let BOINC work with HTTP 1.0 instead of the normal HTTP 1.1, means that something at your ISP changed. Which means that the other machines on the same network should have the same problem.
Well, that is, if you're not running something like Apache on this one machine only. ;-)
RE: Now, the weird thing
)
Well i´d say something is interfering with http 1.1 and the usual suspects are client firewalls and content filters...maybe a network connectivity issue. Need to view the logs to take it further.