Folding Forum

Posted: **Fri Jun 26, 2015 2:26 am**

For a while I have been unable to connect to the FAH service to get work units for the GPU but recently I have lost connection to other work units as well. looking at the logs I see connection attempts to 171.67.108.200 and .204 with both failing. pings to both addresses fail also. tracert to .200 shows i make into Stanford's network but then get blocked. tracert and ping from a hotspot both succeed. I believe either my IP or my subnet is being blocked and humbly request an admin or moderator please investigate.

my WAN information:
Service Provider AT&T Uverse
IP Address 108.208.203.68
Subnet Mask 255.255.252.0
Default Gateway 108.208.200.1

tracert results:

Code: Select all

tracert 171.67.108.200

Tracing route to vsp10v-vz00.stanford.edu [171.67.108.200]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    21 ms    22 ms    21 ms  108-208-200-2.lightspeed.irvnca.sbcglobal.net [108.208.200.2]
  3    21 ms    23 ms    21 ms  75.20.1.0
  4    23 ms    23 ms    23 ms  12.83.38.145
  5    26 ms    26 ms    24 ms  ggr2.la2ca.ip.att.net [12.122.128.97]
  6    22 ms    25 ms    23 ms  las-bb1-link.telia.net [80.239.193.213]
  7    35 ms    36 ms    35 ms  palo-b1-link.telia.net [80.91.252.232]
  8    41 ms    48 ms    48 ms  hurricane-ic-308019-palo-b1.c.telia.net [80.239.167.174]
  9     *       35 ms    57 ms  stanford-university.10gigabitethernet1-4.core1.pao1.he.net [216.218.209.118]
 10    36 ms    36 ms    36 ms  rtf-rtr-po8-8.SUNet [171.64.255.194]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Log file failure:

Code: Select all

*********************** Log Started 2015-06-26T02:12:37Z ***********************
02:12:37:************************* Folding@home Client *************************
02:12:37:      Website: http://folding.stanford.edu/
02:12:37:    Copyright: (c) 2009-2014 Stanford University
02:12:37:       Author: Joseph Coffland <[email protected]>
02:12:37:         Args: --open-web-control
02:12:37:       Config: C:/Users/jbodenhoefer/AppData/Roaming/FAHClient/config.xml
02:12:37:******************************** Build ********************************
02:12:37:      Version: 7.4.4
02:12:37:         Date: Mar 4 2014
02:12:37:         Time: 20:26:54
02:12:37:      SVN Rev: 4130
02:12:37:       Branch: fah/trunk/client
02:12:37:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
02:12:37:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
02:12:37:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
02:12:37:     Platform: win32 XP
02:12:37:         Bits: 32
02:12:37:         Mode: Release
02:12:37:******************************* System ********************************
02:12:37:          CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
02:12:37:       CPU ID: GenuineIntel Family 6 Model 42 Stepping 7
02:12:37:         CPUs: 4
02:12:37:       Memory: 7.97GiB
02:12:37:  Free Memory: 4.35GiB
02:12:37:      Threads: WINDOWS_THREADS
02:12:37:   OS Version: 6.1
02:12:37:  Has Battery: false
02:12:37:   On Battery: false
02:12:37:   UTC Offset: -7
02:12:37:          PID: 9104
02:12:37:          CWD: C:/Users/jbodenhoefer/AppData/Roaming/FAHClient
02:12:37:           OS: Windows 7 Professional
02:12:37:      OS Arch: AMD64
02:12:37:         GPUs: 1
02:12:37:        GPU 0: NVIDIA:2 GF114 [GeForce GTX 560 Ti]
02:12:37:         CUDA: 2.1
02:12:37:  CUDA Driver: 7050
02:12:37:Win32 Service: false
02:12:37:***********************************************************************
02:12:37:<config>
02:12:37:  <!-- Slot Control -->
02:12:37:  <power v='FULL'/>
02:12:37:
02:12:37:  <!-- User Information -->
02:12:37:  <passkey v='********************************'/>
02:12:37:  <team v='143016'/>
02:12:37:  <user v='Fresh_Cookies'/>
02:12:37:
02:12:37:  <!-- Folding Slots -->
02:12:37:  <slot id='0' type='CPU'/>
02:12:37:  <slot id='1' type='GPU'/>
02:12:37:</config>
02:12:37:Connecting to assign-GPU.stanford.edu:80
02:12:58:WARNING:Attempting to update GPUs.txt from assign-GPU.stanford.edu:80: Failed to connect to assign-GPU.stanford.edu:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
02:12:58:Connecting to assign-GPU2.stanford.edu:80
02:13:19:WARNING:Attempting to update GPUs.txt from assign-GPU2.stanford.edu:80: Failed to connect to assign-GPU2.stanford.edu:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
02:13:19:Trying to access database...
02:13:19:Successfully acquired database lock
02:13:19:Enabled folding slot 00: READY cpu:3
02:13:19:Enabled folding slot 01: READY gpu:0:GF114 [GeForce GTX 560 Ti]
02:13:19:WU00:FS00:Connecting to 171.67.108.200:8080
02:13:19:WU01:FS01:Connecting to 171.67.108.200:8080
02:13:23:15:127.0.0.1:New Web connection
02:13:41:WARNING:WU00:FS00:Failed to get ID from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
02:13:41:WARNING:WU01:FS01:Failed to get ID from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
02:13:41:WU00:FS00:Connecting to 171.67.108.204:80
02:13:41:WU01:FS01:Connecting to 171.67.108.204:80
02:14:01:WARNING:WU01:FS01:Failed to get ID from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
02:14:01:ERROR:WU01:FS01:Exception: Could not get an assignment ID
02:14:02:WARNING:WU00:FS00:Failed to get ID from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
02:14:02:ERROR:WU00:FS00:Exception: Could not get an assignment ID

Thank you for any help you can provide.

Mod edit: Please enclose long listings such as your log file in Code tags, they are available from the Full Editor option for posting

Posted: **Fri Jun 26, 2015 2:53 am**

Can you open 171.67.108.200 in your web browser? If yes then it is likely something local like your security software thats blocking the fahclient from connecting.

Posted: **Fri Jun 26, 2015 4:03 am**

My hop 7 and 8 look like alternate routes through stanford's network to your hops 9 and 10.

My guess is that whatever was wrong an hour earlier has been fixed. I'm having no troubles getting through with my browser.

...
3 44 ms 44 ms 46 ms lax1_cr1_3_0_306.dslextreme.com [66.51.202.17]
4 546 ms 78 ms 107 ms any2ix.coresite.com [206.72.210.122]
5 72 ms 69 ms 73 ms 10ge9-5.core1.sjc2.he.net [184.105.213.6]
6 78 ms 89 ms 79 ms 10ge5-2.core1.pao1.he.net [72.52.92.69]
7 * 37 ms 46 ms stanford-university.10gigabitethernet1-4.core1.pao1.he.net [216.218.209.118]
8 46 ms 36 ms 36 ms rtf-rtr-vlan8.SUNet [171.64.255.194]
9 38 ms 37 ms 36 ms vsp10.stanford.edu [171.67.108.18]
10 36 ms 36 ms 37 ms vsp10v-vz00.stanford.edu [171.67.108.200]

Trace complete.

Posted: **Fri Jun 26, 2015 4:46 am**

Rel25917 - I cannot open it in the browser and any computer on my LAN cannot reach the final IP. ping attempts directly from the modem also fail so the problem is not in the PC but rather within my WAN route.

bruce - I can get a similar trace route when i use a hot spot (stanford hops are identical) and i can reach the final destination. thank you for checking your route also.

Posted: **Fri Jun 26, 2015 5:13 am**

I've heard some pretty [insert adjective here] stories about uverse.

Posted: **Fri Jun 26, 2015 1:44 pm**

bruce wrote:I've heard some pretty [insert adjective here] stories about uverse.

Eh, it's not horrendous or anything of the sort. Props to them for at least trying.

But jokes aside, the hops stop at the VSPs, or the last two hops: vsp10.stanford.edu [171.67.108.18] and vsp10v-vz00.stanford.edu [171.67.108.200]. Other than that, it is fine, it is simply a problem connecting to Stanford's servers, which is wondering why if our IP/subnet had been blocked: it's not a problem with any of our equipment at home (router + modem) and we managed to get pretty high up into their tech support and it couldn't be fixed within the ISP's systems. On top of that, the trace hops show it getting all the way from our home network to the ISP's networks and then into Stanford... and then stopping. It says on the FAQ, and I quote:

Stanford's Official FAQ for Folding@Home wrote: If one accesses the stats too often (eg one is running a bot or automatic script), our web server detects this and bans the IP

It then says to make a forum post to inquire about this. We can still access the stats page, but the fact remains that we still cannot access the Assignment Servers.

Posted: **Fri Jun 26, 2015 5:28 pm**

taking a look now, I am able to reach 171.67.108.200 from various places via ping/traceroute , so I will check to see why you cant reach the AS

Thanks,

Mark

Posted: **Fri Jun 26, 2015 5:44 pm**

I've been able to upload/download WU from this server all day, so definitely something on your end. Any windows updates or firewall changes ?

Posted: **Fri Jun 26, 2015 7:45 pm**

Nathan_P wrote:I've been able to upload/download WU from this server all day, so definitely something on your end. Any windows updates or firewall changes ?

Sorry, but you didn't upload or download anything to/from 171.67.108.200. It's an ASSIGNMENT server, not a WORK server. It doesn't have any WORK to be issued nor does it accept results. It is called an ASSIGNMENT server because it ASSIGNs you to an appropriate WORK server that has WUs that will run on your configuration.

Many people do not understand this distinction. Look at your log carefully and you'll see you contacted the Assignment Server first but the WU was downloaded from and uploaded to a different server(s).

That two-step process is necessary in order to avoid cases like "You're asking for a Linux WU and all my WUs only run on Windows" or cases like "This work server doesn't have any WUs right now but others might"

--------------------

The fact that different ISPs enter the Stanford network from different routes and must subsequently be routed through their internal network has been noted and as of last night, at least one of those internal routes was broken has also been noted.

Posted: **Fri Jun 26, 2015 8:02 pm**

our sysadmins and I have looked at this and all tests (traceroutes/pings) to the AS were successful. So there must be something blocking it on the client/ISP side- If it helps, traceroutes to both 108.208.200.1 and 108.208.203.68 end at 12.122.85.37 (gar5.lsrca.ip.att.net).

Thanks,

Mark

Posted: **Fri Jun 26, 2015 11:41 pm**

thank you for looking into this. on the FAQ (dated 12/27/2013) there is mention of an automated system that can ban an IP if it has to much activity come from it. this is in reference to the web service but I was wondering if it is also true for the AS. if the answer is no then I will just have to try again when i move eventually.

Posted: **Sat Jun 27, 2015 12:53 am**

AS cannot ban based on IP address that I know of.

I have seen another AS ban method, but your posted log doesn't show that kind of exclusion.

Folding Forum

unable to connect to 171.67.108.200

unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200

Re: unable to connect to 171.67.108.200