Posts by Greg

1) Message boards : BOINC Manager : Status Indicator (Message 3573) Posted 21 Mar 2006 by Greg Post: Truthfully I never expected the idea to fly more than a few feet. I just thought it might be something to place in the back of a developers mind for future reference. This is not idiot proofing it is making it easier to see if you are running and insure that your computer worksa to the max. Maybe one day but not now. Thanks for the reply.
2) Message boards : BOINC Manager : Status Indicator (Message 3553) Posted 19 Mar 2006 by Greg Post: It sure would be nice if there was some kind of status indicator, rumming, suspended etc. Something like what MSN messenger has. Just something small so we can see easily if we are running or suspended. I usually suspend when going on the net because the nbet works so much faster without BOINC running but sometimes, often, I forget to restart BONIC.What do you guys think??? :)
3) Message boards : BOINC client : Resolving Computer Hostname (Message 3166) Posted 19 Feb 2006 by Greg Post: Thanks to all who helped. The local host problem resolved it's self somehow. All I know for sure is I kept trying to get it started and one day it started. I have talked to some others and they seem to think there is nothing I could do just wait for the routing to get straight. Thanks again.
4) Message boards : BOINC client : Resolving Computer Hostname (Message 2796) Posted 27 Jan 2006 by Greg Post: Unresolved host names are usually an ISP's DNS server problem. Sometimes they can be caused by your router if you use one. Power it off along with the systems and then powering it up, followed by the systems should fix that problem, unless the router is defective. But then you would have problems with other sites, such as posting on this one. You could have a Firewall program that has BOINC.exe and/or BOINC Manager blocked from accessing the Internet. It can also happen if you are using or going through a Proxy server that has problems. BOINC does not work from behind company firewalls that block programs from direct communication to peer servers on the Internet. It does not use the old HTTP web page method used by Seti@home classic. Some companies have proxy servers that allow programs like this to work and go around their firewall. It is also possible that Spyware programs have altered your DSN settings and are routing your DNS requests to some tracking company's systems which act as your DNS server. It might not know about the changed IP address of BOINC. Open a DOS/Command window and ping the servers. PING 128.32.18.173 PING setiboinc.ssl.berkeley.edu The first should ping OK. The second should have its URL resolved to 128.32.18.173 or 128.32.18.174 by your ISP's DNS server. If that does not happen correctly, it is not BOINC's problem. I tried the PING and all I get is timed out. I disabeled NORTON and still get timed out. Did a full system scan today and found nothing. I do not have any proxy servers. I am working from a single machine in my home. The only router involved is my high speed connection that is still running for all other items without problem. I am stumped.
5) Message boards : BOINC client : Resolving Computer Hostname (Message 2795) Posted 27 Jan 2006 by Greg Post: Unresolved host names are usually an ISP's DNS server problem. Sometimes they can be caused by your router if you use one. Power it off along with the systems and then powering it up, followed by the systems should fix that problem, unless the router is defective. But then you would have problems with other sites, such as posting on this one. You could have a Firewall program that has BOINC.exe and/or BOINC Manager blocked from accessing the Internet. It can also happen if you are using or going through a Proxy server that has problems. BOINC does not work from behind company firewalls that block programs from direct communication to peer servers on the Internet. It does not use the old HTTP web page method used by Seti@home classic. Some companies have proxy servers that allow programs like this to work and go around their firewall. It is also possible that Spyware programs have altered your DSN settings and are routing your DNS requests to some tracking company's systems which act as your DNS server. It might not know about the changed IP address of BOINC. Open a DOS/Command window and ping the servers. PING 128.32.18.173 PING setiboinc.ssl.berkeley.edu The first should ping OK. The second should have its URL resolved to 128.32.18.173 or 128.32.18.174 by your ISP's DNS server. If that does not happen correctly, it is not BOINC's problem.
6) Message boards : BOINC client : Resolving Computer Hostname (Message 2787) Posted 27 Jan 2006 by Greg Post: I have been with SETI and then BOINC for some time but it now appears that I have to quit. I don't want to quit but I keep getting unresolved hostname errors and all my attempts to cure this have failed. I have reset DNS, I have reloaded and restarted BOINC and have ask everyone I know but I still can not solve this problem. I make one last request to anyone out there for any help they can provide. Greg
7) Message boards : BOINC client : Resolving Computer Hostname (Message 2760) Posted 25 Jan 2006 by Greg Post: This may work If you get a message that states; cannot resolve host name, do the following; Reboot or wait an hour or two to see if your ISP gets the DNS back to normal or flush the DNS by doing the following, Start->Run, type cmd {enter} type ipconfig /flushdns {enter} wait for the broadcast (15 - 45 minutes) try again. The DNS were reset last Friday long before this started. Rebooting doesn't help either. Any other suggestions would be appreciated.
8) Message boards : BOINC client : Resolving Computer Hostname (Message 2750) Posted 25 Jan 2006 by Greg Post: Since early Sunday morning both SETI and EINSTEIN have been putting out measages that it can not resolve the computer hostaname. I have no idea what is happening but I am loosing good time in the waiting state. Can anybody help me "resolve" this problem. Cheers.

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.