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.

---

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.

---

BOINC Wiki

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.

---

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

---

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.

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.

---

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.

---

If you go to the wiki site there is a download there that will do some basic diagnostics of your link. Here's the address Here Its half way down under automated test for microsoft windows.

If you run that and send me the results file I will see if I can help you. Send them to john_brown_gordon at ntlworld.com
Regards
Ian

---

Having same connectivity problem here. Ran the batch file mentioned. For some reason it runs the gateway test against 0.1.0.1 instead of my actual gateway ip, which is correctly recorded in the b.btf file. Would this be a problem with Boinc or the app? I can't find any reference to 0.1.0.1 in the Boinc directory or in a registry search.

If you go to the wiki site there is a download there that will do some basic diagnostics of your link. Here's the address Here Its half way down under automated test for microsoft windows.

If you run that and send me the results file I will see if I can help you. Send them to john_brown_gordon at ntlworld.com
Regards
Ian

Having same connectivity problem here. Ran the batch file mentioned. For some reason it runs the gateway test against 0.1.0.1 instead of my actual gateway ip, which is correctly recorded in the b.btf file. Would this be a problem with Boinc or the app? I can't find any reference to 0.1.0.1 in the Boinc directory or in a registry search.

If you go to the wiki site there is a download there that will do some basic diagnostics of your link. Here's the address Here Its half way down under automated test for microsoft windows.

If you run that and send me the results file I will see if I can help you. Send them to john_brown_gordon at ntlworld.com
Regards
Ian

What Windows OS are you? 2000? MS changed the output for Win 2000. The script works on 98, ME, XP , 2003 - all tested OK. Known to fail on 2000.

---

Just so its tidy I had a trace from Greg. He was having problems resovling a host name. The trace indocated he has a pretty poor or slow route between him and the Seti servers. Ping times of 700 ms were not uncommon on 4/5 hops of his route.
Example:
7 599 ms 583 ms 618 ms chi-ix.he.net [206.223.119.37]

8 706 ms 736 ms 713 ms pos1-0.gsr12012.sjc.he.net [64.62.227.53]

9 731 ms 758 ms 740 ms pos8-0.gsr12416.sjc2.he.net [64.62.133.18]

10 743 ms 713 ms 731 ms pos3-0.gsr12416.pao.he.net [216.218.230.221]

My guess is he was timing out connection wise before he even got to seti. I suggested he use a proxy as the route was beyond his or seti's control.

I would just add that hostnames were being resolved for him which is waht this thread is about.

---

Having same connectivity problem here. Ran the batch file mentioned. For some reason it runs the gateway test against 0.1.0.1 instead of my actual gateway ip, which is correctly recorded in the b.btf file. Would this be a problem with Boinc or the app? I can't find any reference to 0.1.0.1 in the Boinc directory or in a registry search.

If you go to the wiki site there is a download there that will do some basic diagnostics of your link. Here's the address Here Its half way down under automated test for microsoft windows.

If you run that and send me the results file I will see if I can help you. Send them to john_brown_gordon at ntlworld.com
Regards
Ian

What Windows OS are you? 2000? MS changed the output for Win 2000. The script works on 98, ME, XP , 2003 - all tested OK. Known to fail on 2000.

Yes, running 2000. Thanks.

---

i ran ipconfig/all here are the results but i still cant get boinc manager to communicate with boinc client can anyone tell me why
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\\Documents and Settings\\Darrin Langlois>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

C:\\Documents and Settings\\Darrin Langlois>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

C:\\Documents and Settings\\Darrin Langlois>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : livingroom
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-50-8D-7D-21-29

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : D-Link AirPlus DWL-G520 Wireless PCI
Adapter(rev.B)
Physical Address. . . . . . . . . : 00-13-46-60-23-F9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Tuesday, February 14, 2006 10:55:13
AM
Lease Expires . . . . . . . . . . : Tuesday, February 21, 2006 10:55:13
AM

C:\\Documents and Settings\\Darrin Langlois>ent

---

All the Media States say Media disconneccted.

---

@darrin

Are you running client and manager in that same PC?
You must make sure the boinc client is running and then try and connect using boinc manager. Let me know you have done this and then we can look further.

---

Try these

Do you have BOINC starting at boot? If so delete it from windows startup and reboot, that works for some people...

OK, the disconnected issue means that the BOINC manager is not able to talk to the BOINC daemon. Whether or not you are uploading/downloading/crunching at this point must be determined with the task list (I do not remember how to bring this up for 95/98/me).
The usual reason for this problem is that the BOINC manager is starting and trying to talk before the BOINC daemon is ready to listen. The usual fix is to wait a minute or two and see if connecting to "" or "localhost" or "127.0.0.1" works.
If the above fails, then there is a possibility that the BOINC daemon is not starting. If that is the case, then staring it manually may help. If it is installed as a service, run "net start BOINC" from a command line. If it is installed as single or multi user, cd to the install directory, and run BOINC.exe. If it is now running, you are the victim of a bug that has hopefully been fixed in 5.1.
If it is still not working, you have a problem with one of the XML files, and you will probably have to delete the directory and start over. (I have seen this problem much less with 5.1).
You might also go to the BOINC folder and look for this file "gui rpc auth.cfg" open with word pad and change the password to one you like make sure you enter a return at the end and then save and reboot computer then try the local host entry in select computer popup..... Check your firewall.
When all screens in Boinc Manager are blank, check that Boinc.exe is running. In Windows NT/2k/XP, rightclick on the Windows taskbar and choose Task Manager. Go to the processes tab and check if Boinc.exe is running. Check how many versions of Boincmgr.exe there are running.
If more than 2 of the latter, close them all down and restart one.
If Boinc.exe isn't running, please try a reboot of the computer first.
Close down BOINC.
Navigate to your Boinc directory.
Find the file called gui_rpc_auth.cfg, open it up with a word processor and delete password, then put a blank space followed by a carriage return, save file.
Then restart BOINC.
That will most probably fix it.

---

BOINC Wiki

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.

---