Page 1 of 1

Connecting to assign3.stanford.edu

Posted: Thu Jul 09, 2015 11:23 am
by jinjonBoo
Hey guys.

I'm behind a proxy/DNS at work, and i can't download the Work Units, the log says
11:15:04:ERROR:WU00:FS00:Exception: Could not get IP address for assign3.stanford.edu: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.

Is there any way to download a Work Unit manually?

Yes, i've already set up the proxy on FAH client 7.7.4, i can't ping assign3.stanford.edu, i can however open it on http//assign3.stanford.edu on IE

Thanks in advance

Re: Connecting to assign3.stanford.edu

Posted: Thu Jul 09, 2015 1:31 pm
by Joe_H
Welcome to the folding support forum.

First, the terms of use for the folding client do require that you have permission to use work computers for folding. This may at some businesses extend to also having permission to use your own system such as a laptop on the work network. Just mentioning this as while we appreciate contributions from persons at work, we also don't want them getting into trouble for what some some businesses consider unauthorized use.

That said, you may need to talk with your corporate IT people as they would have the local knowledge of the proxy settings required. There may also be firewall issues. The folding client uses http connections over ports 80 and/or 8080 to connect and many firewalls or anti-malware software are by default set to only allow that type of connection from known "browsers" such as IE, Firefox, etc. If this is the case, then the FAHClient process needs to be given the same ability to connect and download or upload data over the network.

Re: Connecting to assign3.stanford.edu

Posted: Thu Jul 09, 2015 6:02 pm
by bruce
jinjonBoo wrote:I can't ping assign3.stanford.edu, i can however open it on http//assign3.stanford.edu on IE
Being able to ping is not a requirement -- and some server admins configure their servers to ignore pings.

The FAHClient uses the same http protocol and the same ports that your browser uses (provided you've set up your proxy server correctly and) provided your security settings allow connections on ports 8080 or 80.

Re: Connecting to assign3.stanford.edu

Posted: Tue Aug 25, 2015 10:26 pm
by MP3Mike
I am getting an error that assign3.stanford.edu does not resolve to an IP address. I have tried via two different Internet connections/Name Servers, so I think the problem is on the Stanford side right now...

Re: Connecting to assign3.stanford.edu

Posted: Tue Aug 25, 2015 11:07 pm
by 7im

Re: Connecting to assign3.stanford.edu

Posted: Tue Aug 25, 2015 11:14 pm
by DemonfangArun
23:12:41:WARNING:WU01:FS00:Exception: Could not get IP address for assign3.stanford.edu: No such host is known.
23:12:41:ERROR:WU01:FS00:Exception: Could not get an assignment

can confirm same here, unable to connect to assign3.stanford.edu

Re: Connecting to assign3.stanford.edu

Posted: Tue Aug 25, 2015 11:37 pm
by cxh
Thanks for reporting! We're currently on the case! We'll keep you all posted once a fix is made.

Re: Connecting to assign3.stanford.edu

Posted: Tue Aug 25, 2015 11:44 pm
by cxh
Seems like this issue has been corrected, but will take an hour or so to propagate throughout the system. See here for more details: viewtopic.php?f=24&t=28029

Re: Connecting to assign3.stanford.edu

Posted: Wed Aug 26, 2015 5:26 am
by sco01
jcoffland » Wed Aug 26, 2015 3:17 am
assign3.stanford.edu and fah.stanford.edu are both back up.
NO
5:23:49:WARNING:WU00:FS01:Exception: Could not get IP address for assign3.stanford.edu: Этот хост неизвестен.
05:23:49:ERROR:WU00:FS01:Exception: Could not get an assignment
05:23:49:WARNING:WU00:FS01:Exception: Could not get IP address for assign3.stanford.edu: Этот хост неизвестен.
05:23:49:ERROR:WU00:FS01:Exception: Could not get an assignment

on two computers, client I rebooted

Re: Connecting to assign3.stanford.edu

Posted: Wed Aug 26, 2015 5:34 am
by Joe_H
Yes, assign3 and 4 are up, but you may need to have your system update its DNS lookup tables. I can reach both without problems now, the change took a couple hours to propagate to my system.