Page 1 of 1

Having problems connecting to 171.67.108.45(204) [SOLVED]

Posted: Fri Mar 25, 2016 8:01 pm
by wilding2004

Code: Select all

*********************** Log Started 2016-03-25T19:49:36Z ***********************
19:49:36:************************* Folding@home Client *************************
19:49:36:      Website: http://folding.stanford.edu/
19:49:36:    Copyright: (c) 2009-2014 Stanford University
19:49:36:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
19:49:36:         Args: --open-web-control
19:49:36:       Config: C:/Users/dave/AppData/Roaming/FAHClient/config.xml
19:49:36:******************************** Build ********************************
19:49:36:      Version: 7.4.4
19:49:36:         Date: Mar 4 2014
19:49:36:         Time: 20:26:54
19:49:36:      SVN Rev: 4130
19:49:36:       Branch: fah/trunk/client
19:49:36:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
19:49:36:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
19:49:36:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
19:49:36:     Platform: win32 XP
19:49:36:         Bits: 32
19:49:36:         Mode: Release
19:49:36:******************************* System ********************************
19:49:36:          CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
19:49:36:       CPU ID: GenuineIntel Family 6 Model 15 Stepping 11
19:49:36:         CPUs: 4
19:49:36:       Memory: 4.00GiB
19:49:36:  Free Memory: 788.97MiB
19:49:36:      Threads: WINDOWS_THREADS
19:49:36:   OS Version: 6.2
19:49:36:  Has Battery: false
19:49:36:   On Battery: false
19:49:36:   UTC Offset: 0
19:49:36:          PID: 13748
19:49:36:          CWD: C:/Users/dave/AppData/Roaming/FAHClient
19:49:36:           OS: Windows 10 Pro
19:49:36:      OS Arch: AMD64
19:49:36:         GPUs: 1
19:49:36:        GPU 0: ATI:5 Hawaii [Radeon R9 200 Series]
19:49:36:         CUDA: Not detected
19:49:36:Win32 Service: false
19:49:36:***********************************************************************
19:49:36:<config>
19:49:36:  <!-- Folding Slot Configuration -->
19:49:36:  <client-type v='advanced'/>
19:49:36:
19:49:36:  <!-- Network -->
19:49:36:  <proxy v=':8080'/>
19:49:36:
19:49:36:  <!-- Slot Control -->
19:49:36:  <power v='full'/>
19:49:36:
19:49:36:  <!-- User Information -->
19:49:36:  <passkey v='********************************'/>
19:49:36:  <team v='224497'/>
19:49:36:  <user v='wilding2004_ALL_1GP8RDK3c7qrHrXXeh3kdL4Gg3oFXkcw4C'/>
19:49:36:
19:49:36:  <!-- Work Unit Control -->
19:49:36:  <next-unit-percentage v='100'/>
19:49:36:
19:49:36:  <!-- Folding Slots -->
19:49:36:  <slot id='1' type='GPU'/>
19:49:36:  <slot id='0' type='CPU'>
19:49:36:    <cpus v='4'/>
19:49:36:    <paused v='true'/>
19:49:36:  </slot>
19:49:36:</config>
19:49:36:Trying to access database...
19:49:37:Successfully acquired database lock
19:49:37:FS01:Set client configured
19:49:37:Enabled folding slot 01: READY gpu:0:Hawaii [Radeon R9 200 Series]
19:49:37:Enabled folding slot 00: PAUSED cpu:4 (by user)
19:49:38:WU00:FS01:Connecting to 171.67.108.45:80
19:50:00:WARNING:WU00:FS01:Failed to get ID from '171.67.108.45:80': Failed to connect to 171.67.108.45: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.
19:50:00:WU00:FS01:Connecting to 171.67.108.204:80
19:50:21:WARNING:WU00: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.
19:50:21:ERROR:WU00:FS01:Exception: Could not get an assignment ID
19:50:21:WU00:FS01:Connecting to 171.67.108.45:80
19:50:42:WARNING:WU00:FS01:Failed to get ID from '171.67.108.45:80': Failed to connect to 171.67.108.45: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.
19:50:42:WU00:FS01:Connecting to 171.67.108.204:80
19:51:03:WARNING:WU00:FS01:Failed to get ID from '171.67.108.204:80': Failed to connect to 171.67.108.204:80:
Can't find this server listed on the server status page. Or is that page only for work servers and not assignment servers?

Re: Having problems connecting to 171.67.108.45(204)

Posted: Fri Mar 25, 2016 8:06 pm
by 7im
Failed to get ID error typically means that a firewall or antivirus software is blocking your access. Make sure they are configured with folding at home as an exception.

Re: Having problems connecting to 171.67.108.45(204)

Posted: Fri Mar 25, 2016 8:15 pm
by wilding2004
Yeah, f@h is allowed through. I did check again though, as since I've moved to Win10, firewall exceptions seem to change by themselves.

Re: Having problems connecting to 171.67.108.45(204)

Posted: Fri Mar 25, 2016 9:13 pm
by bruce
if http://171.67.108.45 and http://171.67.108.204/ open in your browser, as they do in mine, it's certainly a local problem associated with your security software.

Re: Having problems connecting to 171.67.108.45(204)

Posted: Fri Mar 25, 2016 10:11 pm
by wilding2004
"The connection has timed out
The server at 171.67.108.45 is taking too long to respond."

That's what I get when I try to open in a browser. I'll keep messing around until it works. I haven't changed any security settings - but that doesn't mean that they haven't changed

Re: Having problems connecting to 171.67.108.45(204)

Posted: Sat Mar 26, 2016 12:11 am
by wilding2004
Ok, with both AV and firewall disabled, I still get the same error message.

Re: Having problems connecting to 171.67.108.45(204)

Posted: Sat Mar 26, 2016 4:19 am
by bruce
C:\Users\bruce>tracert 171.67.108.45

Tracing route to VSP11.stanford.edu [171.67.108.45]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 11 ms 10 ms netblock-xxx-xxx-xxx-1.dslextreme.com
3 11 ms 10 ms 10 ms lax1_cr1_gig_10_0_120.dslextreme.com [66.218.48.145]
4 733 ms 69 ms 61 ms hurricane-electric.as6939.any2ix.coresite.com [206.72.210.122]
5 21 ms 20 ms 23 ms 100ge8-2.core1.pao1.he.net [184.105.81.237]
6 19 ms 18 ms 18 ms stanford-university.10gigabitethernet1-4.core1.pao1.he.net [216.218.209.118]
7 24 ms 21 ms 21 ms west-rtr-vlan8.SUNet [171.64.255.193]
8 19 ms 19 ms 18 ms VSP11.stanford.edu [171.67.108.45]

Trace complete.

Re: Having problems connecting to 171.67.108.45(204) [SOLVED

Posted: Sat Mar 26, 2016 5:28 pm
by wilding2004
Turns out it was a very helpful Windows update. So helpful, it broke some networking voodoo - and then tried to blame it on missing registry entries. After hours of fiddling, the cure was to reboot windows with the router turned off.