Page 1 of 2
The connected host didn't answer
Posted: Wed Nov 25, 2015 4:40 am
by coccola
I don't know what's wrong, I reset my routers and switch but it didn't solve the problem. Everything else is working properly (websites, torrents etc). Tried restarting the F@h client numerous times but it didn't help either.
Any help is welcome!
Code: Select all
*********************** Log Started 2015-11-25T04:32:58Z ***********************
04:32:58:************************* Folding@home Client *************************
04:32:58: Website: http://folding.stanford.edu/
04:32:58: Copyright: (c) 2009-2014 Stanford University
04:32:58: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
04:32:58: Args: --open-web-control
04:32:58: Config: C:/Users/Carlos/AppData/Roaming/FAHClient/config.xml
04:32:58:******************************** Build ********************************
04:32:58: Version: 7.4.4
04:32:58: Date: Mar 4 2014
04:32:58: Time: 20:26:54
04:32:58: SVN Rev: 4130
04:32:58: Branch: fah/trunk/client
04:32:58: Compiler: Intel(R) C++ MSVC 1500 mode 1200
04:32:58: Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
04:32:58: /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
04:32:58: Platform: win32 XP
04:32:58: Bits: 32
04:32:58: Mode: Release
04:32:58:******************************* System ********************************
04:32:58: CPU: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
04:32:58: CPU ID: GenuineIntel Family 6 Model 26 Stepping 5
04:32:58: CPUs: 8
04:32:58: Memory: 5.99GiB
04:32:58: Free Memory: 2.59GiB
04:32:58: Threads: WINDOWS_THREADS
04:32:58: OS Version: 6.1
04:32:58: Has Battery: false
04:32:58: On Battery: false
04:32:58: UTC Offset: -2
04:32:58: PID: 7772
04:32:58: CWD: C:/Users/Carlos/AppData/Roaming/FAHClient
04:32:58: OS: Windows 7 Ultimate
04:32:58: OS Arch: AMD64
04:32:58: GPUs: 1
04:32:58: GPU 0: UNSUPPORTED: RV770 [Radeon HD 4850]
04:32:58: CUDA: Not detected
04:32:58:Win32 Service: false
04:32:58:***********************************************************************
04:32:58:<config>
04:32:58: <!-- Network -->
04:32:58: <proxy v=':8080'/>
04:32:58:
04:32:58: <!-- Slot Control -->
04:32:58: <power v='full'/>
04:32:58:
04:32:58: <!-- User Information -->
04:32:58: <passkey v='********************************'/>
04:32:58: <team v='86565'/>
04:32:58: <user v='coccola'/>
04:32:58:
04:32:58: <!-- Folding Slots -->
04:32:58: <slot id='0' type='CPU'>
04:32:58: <next-unit-percentage v='100'/>
04:32:58: </slot>
04:32:58:</config>
04:32:58:Trying to access database...
04:32:58:Successfully acquired database lock
04:32:58:Enabled folding slot 00: READY cpu:8
04:32:59:WU00:FS00:Connecting to 171.67.108.45:8080
04:33:05:20:127.0.0.1:New Web connection
04:33:20:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Failed to connect to 171.67.108.45:8080: Uma tentativa de conex?o falhou porque o componente conectado n?o respondeu
04:33:20:WARNING:WU00:FS00:corretamente ap?s um per?odo de tempo ou a conex?o estabelecida falhou
04:33:20:WARNING:WU00:FS00:porque o host conectado n?o respondeu.
04:33:20:WU00:FS00:Connecting to 171.67.108.204:80
04:33:41:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: Uma tentativa de conex?o falhou porque o componente conectado n?o respondeu
04:33:41:WARNING:WU00:FS00:corretamente ap?s um per?odo de tempo ou a conex?o estabelecida falhou
04:33:41:WARNING:WU00:FS00:porque o host conectado n?o respondeu.
04:33:41:ERROR:WU00:FS00:Exception: Could not get an assignment
04:33:41:WU00:FS00:Connecting to 171.67.108.45:8080
04:34:02:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Failed to connect to 171.67.108.45:8080: Uma tentativa de conex?o falhou porque o componente conectado n?o respondeu
04:34:02:WARNING:WU00:FS00:corretamente ap?s um per?odo de tempo ou a conex?o estabelecida falhou
04:34:02:WARNING:WU00:FS00:porque o host conectado n?o respondeu.
04:34:02:WU00:FS00:Connecting to 171.67.108.204:80
04:34:23:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: Uma tentativa de conex?o falhou porque o componente conectado n?o respondeu
04:34:23:WARNING:WU00:FS00:corretamente ap?s um per?odo de tempo ou a conex?o estabelecida falhou
04:34:23:WARNING:WU00:FS00:porque o host conectado n?o respondeu.
04:34:23:ERROR:WU00:FS00:Exception: Could not get an assignment
04:34:41:WU00:FS00:Connecting to 171.67.108.45:8080
04:35:03:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Failed to connect to 171.67.108.45:8080: Uma tentativa de conex?o falhou porque o componente conectado n?o respondeu
04:35:03:WARNING:WU00:FS00:corretamente ap?s um per?odo de tempo ou a conex?o estabelecida falhou
04:35:03:WARNING:WU00:FS00:porque o host conectado n?o respondeu.
04:35:03:WU00:FS00:Connecting to 171.67.108.204:80
04:35:24:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: Uma tentativa de conex?o falhou porque o componente conectado n?o respondeu
04:35:24:WARNING:WU00:FS00:corretamente ap?s um per?odo de tempo ou a conex?o estabelecida falhou
04:35:24:WARNING:WU00:FS00:porque o host conectado n?o respondeu.
04:35:24:ERROR:WU00:FS00:Exception: Could not get an assignment
04:36:19:WU00:FS00:Connecting to 171.67.108.45:8080
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 10:35 am
by toTOW
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 12:37 pm
by coccola
Nope, I get a connection timeout on both.
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 2:49 pm
by coccola
Any idea of what's going on?
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 3:06 pm
by Ricky
Perhaps you have a firewall set on your machine. If so, maybe you can set an exception for both of these IP addresses. Just a guess on my part.
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 3:35 pm
by coccola
I disabled Windows' firewall and restarted the F@h client. Exactly the same problem happens.
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 3:42 pm
by coccola
I'll translate the error message, maybe more people can help me this way:
04:33:20:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Failed to connect to 171.67.108.45:8080: Uma tentativa de conex?o falhou porque o componente conectado n?o respondeu
04:33:20:WARNING:WU00:FS00:corretamente ap?s um per?odo de tempo ou a conex?o estabelecida falhou
04:33:20:WARNING:WU00:FS00:porque o host conectado n?o respondeu.
Full error message:
Uma tentativa de conex?o falhou porque o componente conectado n?o respondeu corretamente ap?s um per?odo de tempo ou a conex?o estabelecida falhou porque o host conectado n?o respondeu.
Translation:
A connection attempt failed because the connected component didn't answer correctly after a period of time or the established connection failed because the connected host didn't answer.
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 4:03 pm
by toTOW
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 5:00 pm
by bruce
From here, I can open all four of the assign* addresses and both IPs in the second post. (The "complementary test" reports a problem with the security certificate which I can bypass to get a connection.)
The Stanford end of the connection seems to be working (for me?) so maybe it was fixed and maybe it's on your end.
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 6:20 pm
by coccola
The first 4 links time out for me.
The complementary test works, but I have to add an exception on Firefox.
I'm getting desperate, I'm getting this problem for many hours...
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 8:30 pm
by bruce
Try tracert 171.67.108.204 (windows) or traceroute 171.67.108.204 (linux)
(hops 1 & 2 edited)
Tracing route to vsp10v-vz04.stanford.edu [171.67.108.204]
over a maximum of 30 hops:
3 25 ms 10 ms 11 ms lax1_cr1_3_0_306.dslextreme.com [66.51.202.17]
4 10 ms 95 ms 84 ms any2ix.coresite.com [206.72.210.122]
5 19 ms 19 ms 20 ms 10ge9-5.core1.sjc2.he.net [184.105.213.6]
6 19 ms 24 ms 23 ms 10ge3-3.core1.pao1.he.net [72.52.92.69]
7 19 ms 20 ms 19 ms stanford-university.10gigabitethernet1-4.core1.pao1.he.net [216.218.209.118]
8 84 ms 90 ms 89 ms rtf-rtr-po8-8.SUNet [171.64.255.194]
9 125 ms 104 ms 90 ms vsp10.stanford.edu [171.67.108.18]
10 19 ms 19 ms 19 ms vsp10v-vz04.stanford.edu [171.67.108.204]
Trace complete.
Re: The connected host didn't answer
Posted: Wed Nov 25, 2015 8:45 pm
by coccola
Thank you for your reply!
Here is the result:
Code: Select all
C:\>tracert 171.67.108.204
Rastreando a rota para vsp10v-vz04.stanford.edu [171.67.108.204]
com no máximo 30 saltos:
1 <1 ms <1 ms <1 ms 192.168.10.2
2 <1 ms <1 ms 1 ms mymodem [192.168.1.1]
3 * * * Esgotado o tempo limite do pedido.
4 3 ms 2 ms 2 ms 187-100-37-105.dsl.telesp.net.br [187.100.37.105]
5 28 ms 3 ms 8 ms 187-100-78-145.dsl.telesp.net.br [187.100.78.145]
6 3 ms 3 ms 3 ms 187-100-35-245.dsl.telesp.net.br [187.100.35.245]
7 10 ms 9 ms 9 ms et1-0-0-100-grtsanem3.net.telefonicaglobalsolutions.com [213.140.39.185]
8 113 ms 115 ms 115 ms hu1-2-0-0-grtmiabr6.net.telefonicaglobalsolutions.com [5.53.3.143]
9 141 ms 140 ms 141 ms xe4-0-1-0-grtdaleq4.net.telefonicaglobalsolutions.com [94.142.119.33]
10 141 ms 142 ms 175 ms 213.140.53.254
11 181 ms 181 ms 189 ms 10ge9-1.core3.fmt2.he.net [72.52.92.153]
12 187 ms 182 ms 191 ms 10ge10-5.core1.pao1.he.net [184.105.222.90]
13 * * * Esgotado o tempo limite do pedido.
14 182 ms 181 ms 180 ms rtf-rtr-po8-8.SUNet [171.64.255.194]
15 * * * Esgotado o tempo limite do pedido.
16 * * * Esgotado o tempo limite do pedido.
17 * * * Esgotado o tempo limite do pedido.
18 * * * Esgotado o tempo limite do pedido.
19 * * * Esgotado o tempo limite do pedido.
20 * * * Esgotado o tempo limite do pedido.
21 * * * Esgotado o tempo limite do pedido.
22 * * * Esgotado o tempo limite do pedido.
23 * * * Esgotado o tempo limite do pedido.
24 * * * Esgotado o tempo limite do pedido.
25 * * * Esgotado o tempo limite do pedido.
26 * * * Esgotado o tempo limite do pedido.
27 * * * Esgotado o tempo limite do pedido.
28 * * * Esgotado o tempo limite do pedido.
29 * * * Esgotado o tempo limite do pedido.
30 * * * Esgotado o tempo limite do pedido.
Rastreamento concluído.
C:\>
Translation:
Esgotado o tempo limite do pedido. = The request timed out.
Re: The connected host didn't answer
Posted: Thu Nov 26, 2015 12:43 am
by _r2w_ben
Is there any difference between tracert -4 171.67.108.204 and tracert -6 171.67.108.204?
Re: The connected host didn't answer
Posted: Thu Nov 26, 2015 1:03 am
by coccola
-6 results in a error message stating that it's not possible to resolve the name of the target system.
-4 results the same as before, except for the hop #13:
Code: Select all
C:\>tracert -4 171.67.108.204
Rastreando a rota para vsp10v-vz04.stanford.edu [171.67.108.204]
com no máximo 30 saltos:
1 <1 ms <1 ms <1 ms 192.168.10.2
2 <1 ms <1 ms <1 ms mymodem [192.168.1.1]
3 * * * Esgotado o tempo limite do pedido.
4 3 ms 3 ms 2 ms 187-100-37-105.dsl.telesp.net.br [187.100.37.105]
5 4 ms 2 ms 1 ms 187-100-78-145.dsl.telesp.net.br [187.100.78.145]
6 3 ms 3 ms 3 ms 187-100-35-245.dsl.telesp.net.br [187.100.35.245]
7 10 ms 10 ms 10 ms et1-0-0-100-grtsanem3.net.telefonicaglobalsolutions.com [213.140.39.185]
8 116 ms 115 ms 116 ms hu1-2-0-0-grtmiabr6.net.telefonicaglobalsolutions.com [5.53.3.143]
9 141 ms 141 ms 141 ms xe4-0-1-0-grtdaleq4.net.telefonicaglobalsolutions.com [94.142.119.33]
10 160 ms 147 ms 149 ms 213.140.53.254
11 184 ms 181 ms 180 ms 10ge9-1.core3.fmt2.he.net [72.52.92.153]
12 182 ms 193 ms 182 ms 10ge10-5.core1.pao1.he.net [184.105.222.90]
13 182 ms 181 ms 180 ms stanford-university.10gigabitethernet1-4.core1.pao1.he.net [216.218.209.118]
14 188 ms 181 ms 181 ms rtf-rtr-po8-8.SUNet [171.64.255.194]
15 * * * Esgotado o tempo limite do pedido.
16 * * * Esgotado o tempo limite do pedido.
17 * * * Esgotado o tempo limite do pedido.
18 * * * Esgotado o tempo limite do pedido.
19 * * * Esgotado o tempo limite do pedido.
20 * * * Esgotado o tempo limite do pedido.
21 * * * Esgotado o tempo limite do pedido.
22 * * * Esgotado o tempo limite do pedido.
23 * * * Esgotado o tempo limite do pedido.
24 * * * Esgotado o tempo limite do pedido.
25 * * * Esgotado o tempo limite do pedido.
26 * * * Esgotado o tempo limite do pedido.
27 * * * Esgotado o tempo limite do pedido.
28 * * * Esgotado o tempo limite do pedido.
29 * * * Esgotado o tempo limite do pedido.
30 * * * Esgotado o tempo limite do pedido.
Rastreamento concluído.
C:\>
Re: The connected host didn't answer
Posted: Thu Nov 26, 2015 3:32 am
by _r2w_ben
This reminds me of this
thread where someone was unable to access the .edu TLD. The 15th and 16th hops in your trace route would end in standford.edu.
Have you power-cycled your modem, router, and flushed DNS?