Version: 7.3.6:No address associated with hostname

[suprleg]

I recently took custody of two blades and since restarting them, in their new home, I'm getting the following error message while attempting to get new work.:
[91m10:10:31:ERROR:WU01:FS00:Exception: Could not get an assignment[0m
[93m10:10:31:WARNING:WU01:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Could not get IP address for assign4.stanford.edu: No address associated with hostname[0m

Any ideas would be appreciated.

Thanks

[P5-133XL]

DNS isn't available. Do you have an internet connection on the blades?

[suprleg]

Thanks for the response, yes net connectivity is fine. The blades went from a [static IP, proxy server, and hostname] to new DNS servers and DHCP. Ubuntu 12.04.4 LTS.

[P5-133XL]

The error is directly related to the lack of DNS. It can't take the url assign4.stanford.edu and convert it to an IP address which is a function of DNS.

[suprleg]

In speaking with the blades original owner I've edited .bashrc and removed some proxy lines, but it hasen't helped. Can you think of any other possible file locations that fah might still be attempting to draw from?

[P5-133XL]

No, File. It is attempting to go to the DNS server configured for the internet connection and getting no response...

[P5-133XL]

If you are using a proxy server to access the internet, then that would need to be configured withing the folding program using the advanced control.

[P5-133XL]

Also, you may have a firewall actively preventing folding from accessing the internet which could also cause this problem.

[suprleg]

Still having DNS problems with assignx.stanford.edu, what am I missing"?
Other machines on the LAN have no problems resolving Standord's server addresses.
Thanks

Snippet of log:

* 05:25:39:WU00:FS00:Connecting to assign3.stanford.edu:8080
05:25:59:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Could not get IP address for assign3.stanford.edu: No address associated with hostname
05:25:59:WU00:FS00:Connecting to assign4.stanford.edu:80
05:26:18:WARNING:WU00:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Could not get IP address for assign4.stanford.edu: No address associated with hostname
05:26:18:ERROR:WU00:FS00:Exception: Could not get an assignment

* 05:45:28:WU01:FS00:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
05:45:30:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
05:45:30:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:6370 run:25 clone:133 gen:5 core:0xa4

* 05:45:30:WU01:FS00:Uploading 1.22MiB to 155.247.166.219
05:45:30:WU01:FS00:Connecting to 155.247.166.219
:8080
05:45:32:WU01:FS00:Upload complete

* 10:46:42:WU00:FS00:Connecting to assign3.stanford.edu:8080
10:46:52:WU00:FS00:News: Welcome to Folding@Home
10:46:52:WU00:FS00:Assigned to work server 171.64.65.124
10:46:52:WU00:FS00:Requesting new work unit for slot 00: READY cpu:1 from 171.64.65.124
10:46:52:WU00:FS00:Connecting to 171.64.65.124:8080
10:46:53:WU00:FS00:Downloading 863.96KiB
10:46:53:WU00:FS00:Download complete
************************
PING 171.64.65.124
--- 171.64.65.124 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5010ms

nslookup 171.64.65.124
;; connection timed out; no servers could be reached
************************
ping 155.247.166.219
--- 155.247.166.219 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8001ms

nslookup 155.247.166.219
Server: 127.0.0.1
Address: 127.0.0.1#53

Non-authoritative answer:
219.166.247.155.in-addr.arpa name = vav3.ocis.temple.edu.
***********************

[suprleg]

Hmm..now I seem to be having difficulties with all my Windows and Ubuntu clients..
The Windows clients are searching endlessly:
13:20:31:Server access denied for 192.168.1.31:38666
13:20:36:Server access denied for 192.168.1.31:38668
13:20:41:Server access denied for 192.168.1.31:38670
13:20:46:Server access denied for 192.168.1.31:38672
13:20:51:Server access denied for 192.168.1.31:38674
13:20:56:Server access denied for 192.168.1.31:38676
13:21:01:Server access denied for 192.168.1.31:38678
13:21:06:Server access denied for 192.168.1.31:38680
13:21:11:Server access denied for 192.168.1.31:38682
13:21:16:Server access denied for 192.168.1.31:38684
13:21:21:Server access denied for 192.168.1.31:38686
13:21:26:Server access denied for 192.168.1.31:38688
13:21:31:Server access denied for 192.168.1.31:38690
13:21:36:Server access denied for 192.168.1.31:38692
13:21:41:Server access denied for 192.168.1.31:38694
13:21:46:Server access denied for 192.168.1.31:38696
13:21:51:Server access denied for 192.168.1.31:38698
.
.
.
13:32:27:Server access denied for 192.168.1.31:38962
13:32:32:Server access denied for 192.168.1.31:38964
13:32:37:Server access denied for 192.168.1.31:38966
******************************** Date: 05/06/14 ********************************
13:32:42:Server access denied for 192.168.1.31:38968
13:32:47:Server access denied for 192.168.1.31:38970
13:32:52:Server access denied for 192.168.1.31:38972
13:32:57:Server access denied for 192.168.1.31:38974
13:33:02:Server access denied for 192.168.1.31:38976
13:33:07:Server access denied for 192.168.1.31:38978

[log from Windows client at 192.168.1.102]

*********************

192.168.1.31 is the IP of the newly added Ubuntu 12.04 LTS blades

[PantherX]

Hmm..now I seem to be having difficulties with all my Windows and Ubuntu clients..
The Windows clients are searching endlessly:...
[log from Windows client at 192.168.1.102]

*********************

192.168.1.31 is the IP of the newly added Ubuntu 12.04 LTS blades

Can you please see if the section Advanced Control Issues (Remote) in this post (viewtopic.php?p=261089&f=24#p261089) solves your issue or not.

[ChristianVirtual]

It really looks like some trouble with your basic network setup.
Have a look into the files like
/etc/hosts
/etc/resolve.conf

And have a look here:
man resolvconf

Also make sure the DNS server is forwarding those requests it can't solve itself, e.g. To google on 8.8.8.8

What do you get when try the following

nslookup assign4.stanford.edu

[bruce]

The repeated message "Server access denied for 192.168.1.31:38978" is a separate problem from your DNS problem. PantherX has already identified that it's a report of difficulties in enabling remote access between FAHControl on 192.168.1.102 and FAHClient on 192.168.1.31. Check the remote access settings, and the identy settings. Are you using a password (and if so, do they match in Connection and in Remote Access)? Are both machines using the same passkey?

[P5-133XL]

Do note, that when you make remote access changes to folding v7, both the host and the client folding applications need to be restarted for it to work. Just making the changes in the configs is not enough.

[suprleg]

It really looks like some trouble with your basic network setup.
Have a look into the files like
/etc/hosts
/etc/resolve.conf

And have a look here:
man resolvconf

Also make sure the DNS server is forwarding those requests it can't solve itself, e.g. To google on 8.8.8.8

What do you get when try the following

nslookup assign4.stanford.edu

~$ nslookup assign4.stanford.edu
Server: 127.0.0.1
Address: 127.0.0.1#53

Non-authoritative answer:
assign4.stanford.edu canonical name = vspg6-vz7.stanford.edu.
Name: vspg6-vz7.stanford.edu
Address: 171.64.65.121