134.139.127.31 Cannot connect to work server
Moderators: Site Moderators, FAHC Science Team
134.139.127.31 Cannot connect to work server
Hi I'm new...
The specific servers listed for two packets have been failing uploading quite a bit.
The first..
Project: 1751 (Run 2, Clone 55, Gen 7), Core: a0
Work server: 134.139.127.31:8080
Collection server: 134.139.127.34
Download date: October 7 08:15:03
Finished date: October 11 05:40:15
Failed uploads: 15
(from log)
17:22:07] + Attempting to send results [October 12 17:22:07 UTC]
[17:22:07] Core required: FahCore_78.exe
[17:22:07] Core found.
[17:22:07] Working on queue slot 09 [October 12 17:22:07 UTC]
[17:22:07] + Working ...
[17:22:08] - Couldn't send HTTP request to server
[17:22:08] + Could not connect to Work Server (results)
[17:22:08] (134.139.127.31:8080)
[17:22:08] + Retrying using alternative port
[17:22:08] - Couldn't send HTTP request to server
[17:22:08] + Could not connect to Work Server (results)
[17:22:08] (134.139.127.31:80)
[17:22:08] - Error: Could not transmit unit 06 (completed October 11) to work server.
Look to up fully active when looking at the server status page, but I cannot bring up that ip on my browser on either. Other WU's are being returned successfully.
Thanks!
jww
The specific servers listed for two packets have been failing uploading quite a bit.
The first..
Project: 1751 (Run 2, Clone 55, Gen 7), Core: a0
Work server: 134.139.127.31:8080
Collection server: 134.139.127.34
Download date: October 7 08:15:03
Finished date: October 11 05:40:15
Failed uploads: 15
(from log)
17:22:07] + Attempting to send results [October 12 17:22:07 UTC]
[17:22:07] Core required: FahCore_78.exe
[17:22:07] Core found.
[17:22:07] Working on queue slot 09 [October 12 17:22:07 UTC]
[17:22:07] + Working ...
[17:22:08] - Couldn't send HTTP request to server
[17:22:08] + Could not connect to Work Server (results)
[17:22:08] (134.139.127.31:8080)
[17:22:08] + Retrying using alternative port
[17:22:08] - Couldn't send HTTP request to server
[17:22:08] + Could not connect to Work Server (results)
[17:22:08] (134.139.127.31:80)
[17:22:08] - Error: Could not transmit unit 06 (completed October 11) to work server.
Look to up fully active when looking at the server status page, but I cannot bring up that ip on my browser on either. Other WU's are being returned successfully.
Thanks!
jww
Last edited by jwwPhotos on Thu Oct 22, 2009 3:23 am, edited 1 time in total.
Re: 134.139.127.31 Cannot connect to work server
Update.. still failing as previously reported.
Last edited by jwwPhotos on Thu Oct 22, 2009 3:23 am, edited 1 time in total.
Re: 134.139.127.31 Cannot connect to work server
Adding verbose log results
Code: Select all
[13:22:13] + Attempting to send results [October 14 13:22:13 UTC]
[13:22:13] - Reading file work/wuresults_06.dat from core
[13:22:13] (Read 6346264 bytes from disk)
[13:22:13] Connecting to http://134.139.127.31:8080/
[13:22:13] - Couldn't send HTTP request to server
[13:22:13] + Could not connect to Work Server (results)
[13:22:13] (134.139.127.31:8080)
[13:22:13] + Retrying using alternative port
[13:22:13] Connecting to http://134.139.127.31:80/
[13:22:13] - Couldn't send HTTP request to server
[13:22:13] + Could not connect to Work Server (results)
[13:22:13] (134.139.127.31:80)
[13:22:13] - Error: Could not transmit unit 06 (completed October 11) to work server.
[13:22:13] - 24 failed uploads of this unit.
[13:22:13] + Attempting to send results [October 14 13:22:13 UTC]
[13:22:13] - Reading file work/wuresults_06.dat from core
[13:22:13] (Read 6346264 bytes from disk)
[13:22:13] Connecting to http://134.139.127.34:8080/
[13:22:13] - Couldn't send HTTP request to server
[13:22:13] + Could not connect to Work Server (results)
[13:22:13] (134.139.127.34:8080)
[13:22:13] + Retrying using alternative port
[13:22:13] Connecting to http://134.139.127.34:80/
[13:22:13] - Couldn't send HTTP request to server
[13:22:13] + Could not connect to Work Server (results)
[13:22:13] (134.139.127.34:80)
[13:22:13] Could not transmit unit 06 to Collection server; keeping in queue.
[13:22:13] Project: 3864 (Run 56, Clone 4, Gen 23)
[13:22:13] + Attempting to send results [October 14 13:22:13 UTC]
[13:22:13] - Reading file work/wuresults_08.dat from core
[13:22:13] (Read 2468469 bytes from disk)
[13:22:13] Connecting to http://128.143.48.226:8080/
[13:22:14] - Couldn't send HTTP request to server
[13:22:14] + Could not connect to Work Server (results)
[13:22:14] (128.143.48.226:8080)
[13:22:14] + Retrying using alternative port
[13:22:14] Connecting to http://128.143.48.226:80/
[13:22:15] - Couldn't send HTTP request to server
[13:22:15] + Could not connect to Work Server (results)
[13:22:15] (128.143.48.226:80)
[13:22:15] - Error: Could not transmit unit 08 (completed October 12) to work server.
[13:22:15] - 16 failed uploads of this unit.
[13:22:15] + Attempting to send results [October 14 13:22:15 UTC]
[13:22:15] - Reading file work/wuresults_08.dat from core
[13:22:15] (Read 2468469 bytes from disk)
[13:22:15] Connecting to http://128.143.48.227:8080/
[13:22:15] - Couldn't send HTTP request to server
[13:22:15] + Could not connect to Work Server (results)
[13:22:15] (128.143.48.227:8080)
[13:22:15] + Retrying using alternative port
[13:22:15] Connecting to http://128.143.48.227:80/
[13:22:15] - Couldn't send HTTP request to server
[13:22:15] + Could not connect to Work Server (results)
[13:22:15] (128.143.48.227:80)
[13:22:15] Could not transmit unit 08 to Collection server; keeping in queue.
[13:22:15] + Sent 0 of 2 completed units to the server
[13:22:15] + Closed connections
Re: 134.139.127.31 Cannot connect to work server
Sorry for the above messy posts.. didn't realize what the code tag option could be used for!!
Still getting failures on this server. Now up to 43 attempts
Still getting failures on this server. Now up to 43 attempts
Code: Select all
[17:53:25] + Attempting to send results [October 17 17:53:25 UTC]
[17:53:25] - Reading file work/wuresults_06.dat from core
[17:53:25] (Read 6346264 bytes from disk)
[17:53:25] Connecting to http://134.139.127.31:8080/
[17:53:25] - Couldn't send HTTP request to server
[17:53:25] + Could not connect to Work Server (results)
[17:53:25] (134.139.127.31:8080)
[17:53:25] + Retrying using alternative port
[17:53:25] Connecting to http://134.139.127.31:80/
[17:53:25] - Couldn't send HTTP request to server
[17:53:25] + Could not connect to Work Server (results)
[17:53:25] (134.139.127.31:80)
[17:53:25] - Error: Could not transmit unit 06 (completed October 11) to work server.
[17:53:25] - 43 failed uploads of this unit.
Last edited by jwwPhotos on Thu Oct 22, 2009 3:24 am, edited 1 time in total.
-
- Posts: 522
- Joined: Mon Dec 03, 2007 4:33 am
- Location: Australia
Re: 134.139.127.31 Cannot connect to work server
I see this server is in the 'Accepting' status and there have been some WUs returned within the past half hour. Can you connect to http://134.139.127.34:80/ and http://134.139.127.34:8080/ via your browser?
Re: 134.139.127.31 Cannot connect to work server
Hmmm... yes I can. I do get an ok. Possibly the next time around it will finally send!
..or do you think I have an issue on my client? I have other packets that have returned, but as you can see my client isn't connecting when it finally attempts. Is there some extra command I should be adding to my client or a way to retry that one queue manually?
Thanks so much for your help!!
..or do you think I have an issue on my client? I have other packets that have returned, but as you can see my client isn't connecting when it finally attempts. Is there some extra command I should be adding to my client or a way to retry that one queue manually?
Thanks so much for your help!!
Last edited by jwwPhotos on Sun Oct 18, 2009 12:58 am, edited 1 time in total.
Re: 134.139.127.31 Cannot connect to work server
If you can upload some units and not others, there is nothing in the client that can be done about it. There's a high probabilty that it's a problem with a specific server and it will be fixed by the Pande Group when possible. The client is specifically designed to take this into account by holding the WU and retrying automatically.
If you wish to study the data on the Server Status page it may tell you more about the problem, but there's nothing that you can do about it except perhaps to test the specific connection as anandhanju suggested.
If you wish to study the data on the Server Status page it may tell you more about the problem, but there's nothing that you can do about it except perhaps to test the specific connection as anandhanju suggested.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: 134.139.127.31 Cannot connect to work server
Hi Bruce,
Thanks so much for your reply. I am still able to get the OK status on both IP's and for fun, stopped and restarted the client which seems to force a retry and still get the cannot connect. The status pages still shows it is accepting and nothing else seems out of place. So I dunno.. So maybe the server is just full or something as someone suggested on another server I reported.
I understand that at least it stays on the the queue and resends. The reason I am mentioning all this is that over the past week or so since I have joined Folding, I now have 5 out of 10 queue slots that are still trying to send. Since that same timeframe only a total of 7 WU's were successfully sent. It just looked like a bad percentage to me!! At any rate, I will keep reporting those IP's!
Thanks again!
Thanks so much for your reply. I am still able to get the OK status on both IP's and for fun, stopped and restarted the client which seems to force a retry and still get the cannot connect. The status pages still shows it is accepting and nothing else seems out of place. So I dunno.. So maybe the server is just full or something as someone suggested on another server I reported.
I understand that at least it stays on the the queue and resends. The reason I am mentioning all this is that over the past week or so since I have joined Folding, I now have 5 out of 10 queue slots that are still trying to send. Since that same timeframe only a total of 7 WU's were successfully sent. It just looked like a bad percentage to me!! At any rate, I will keep reporting those IP's!
Thanks again!
Re: 134.139.127.31 Cannot connect to work server
Yes, that really is a bad percentage.jwwPhotos wrote:The reason I am mentioning all this is that over the past week or so since I have joined Folding, I now have 5 out of 10 queue slots that are still trying to send. Since that same timeframe only a total of 7 WU's were successfully sent. It just looked like a bad percentage to me!! At any rate, I will keep reporting those IP's!
* Which version of the client are you using?
* Have you modified any of the default configuration settings?
* Please describe how your machine is connected to the internet.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: 134.139.127.31 Cannot connect to work server
*I am using Version CPU client 6.23bruce wrote: Yes, that really is a bad percentage.
* Which version of the client are you using?
* Have you modified any of the default configuration settings?
* Please describe how your machine is connected to the internet.
*I added -verbosity 9 when I started seeing issues so I could report here better and just today enabled Do Not Lock Cores since I have a Quad CPU and figured that would boost the performance a bit when I am afk.
*I am connected via a router to a DSL modem.
Further info. I am able to bring up the pages in my browser at least on this WU's IP and have even tried turning off my firewall when restarting the folding client and still get 0 out of 5. I've checked the firewall and the folding client has access.
Thanks again for your help!
Re: 134.139.127.31 Cannot connect to work server
I don't see the 0 out of 5 that you're talking about. The log you posted shows two WUs. One is numbered 06 which failed to upload to servers 134.139.127.31 and 134.139.127.34 and another numbered 08 failed to upload to servers 128.143.48.226 and 128.143.48.227.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: 134.139.127.31 Cannot connect to work server
bruce wrote:I don't see the 0 out of 5 that you're talking about. The log you posted shows two WUs. One is numbered 06 which failed to upload to servers 134.139.127.31 and 134.139.127.34 and another numbered 08 failed to upload to servers 128.143.48.226 and 128.143.48.227.
Sorry for the confusion.. I have them reported under their seperate IP addresses and must have grabbed two on the above. Here is the full portion of the log showing the connectivity issues if it helps...
Code: Select all
# Windows CPU Systray Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Documents and Settings\jww\Application Data\Folding@home-x86
Arguments: -verbosity 9
[01:08:02] - Ask before connecting: No
[01:08:02] - User name: jwwphotos (Team 170070)
[01:08:02] - User ID: 4BE2C385425AC398
[01:08:02] - Machine ID: 1
[01:08:02]
[01:08:02] Loaded queue successfully.
[01:08:02] Initialization complete
[01:08:02]
[01:08:02] - Autosending finished units... [October 18 01:08:02 UTC]
[01:08:02] + Processing work unit
[01:08:02] Trying to send all finished work units
[01:08:02] Project: 6301 (Run 176, Clone 6, Gen 8)
[01:08:02] + Attempting to send results [October 18 01:08:02 UTC]
[01:08:02] Core required: FahCore_78.exe
[01:08:02] Core found.
[01:08:02] - Reading file work/wuresults_00.dat from core
[01:08:02] Working on queue slot 03 [October 18 01:08:02 UTC]
[01:08:02] + Working ...
[01:08:02] - Calling '.\FahCore_78.exe -dir work/ -suffix 03 -nocpulock -checkpoint 15 -verbose -lifeline 6080 -version 623'
[01:08:02] (Read 4722331 bytes from disk)
[01:08:02] Connecting to http://171.64.65.111:8080/
[01:08:02] - Couldn't send HTTP request to server
[01:08:02] + Could not connect to Work Server (results)
[01:08:02] (171.64.65.111:8080)
[01:08:02] + Retrying using alternative port
[01:08:02] Connecting to http://171.64.65.111:80/
[01:08:02] - Couldn't send HTTP request to server
[01:08:02] + Could not connect to Work Server (results)
[01:08:02] (171.64.65.111:80)
[01:08:02] - Error: Could not transmit unit 00 (completed October 15) to work server.
[01:08:02] - 21 failed uploads of this unit.
[01:08:02] + Attempting to send results [October 18 01:08:02 UTC]
[01:08:02] - Reading file work/wuresults_00.dat from core
[01:08:02] (Read 4722331 bytes from disk)
[01:08:02] Connecting to http://171.67.108.17:8080/
[01:08:02]
[01:08:02] *------------------------------*
[01:08:02] Folding@Home Gromacs Core
[01:08:02] Version 1.90 (March 8, 2006)
[01:08:02]
[01:08:02] Preparing to commence simulation
[01:08:02] - Looking at optimizations...
[01:08:02] - Files status OK
[01:08:02] - Couldn't send HTTP request to server
[01:08:02] + Could not connect to Work Server (results)
[01:08:02] (171.67.108.17:8080)
[01:08:02] + Retrying using alternative port
[01:08:02] Connecting to http://171.67.108.17:80/
[01:08:02] - Couldn't send HTTP request to server
[01:08:02] + Could not connect to Work Server (results)
[01:08:02] (171.67.108.17:80)
[01:08:02] Could not transmit unit 00 to Collection server; keeping in queue.
[01:08:02] Project: 6301 (Run 176, Clone 6, Gen 8)
[01:08:02] + Attempting to send results [October 18 01:08:02 UTC]
[01:08:02] - Reading file work/wuresults_01.dat from core
[01:08:02] (Read 4722192 bytes from disk)
[01:08:02] Connecting to http://171.64.65.111:8080/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (171.64.65.111:8080)
[01:08:03] + Retrying using alternative port
[01:08:03] Connecting to http://171.64.65.111:80/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (171.64.65.111:80)
[01:08:03] - Error: Could not transmit unit 01 (completed October 16) to work server.
[01:08:03] - 16 failed uploads of this unit.
[01:08:03] + Attempting to send results [October 18 01:08:03 UTC]
[01:08:03] - Reading file work/wuresults_01.dat from core
[01:08:03] (Read 4722192 bytes from disk)
[01:08:03] Connecting to http://171.67.108.17:8080/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (171.67.108.17:8080)
[01:08:03] + Retrying using alternative port
[01:08:03] Connecting to http://171.67.108.17:80/
[01:08:03] - Expanded 238652 -> 1164961 (decompressed 488.1 percent)
[01:08:03]
[01:08:03] Project: 4460 (Run 952, Clone 0, Gen 40)
[01:08:03]
[01:08:03] Assembly optimizations on if available.
[01:08:03] Entering M.D.
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (171.67.108.17:80)
[01:08:03] Could not transmit unit 01 to Collection server; keeping in queue.
[01:08:03] Project: 3861 (Run 415, Clone 9, Gen 30)
[01:08:03] + Attempting to send results [October 18 01:08:03 UTC]
[01:08:03] - Reading file work/wuresults_02.dat from core
[01:08:03] (Read 1104801 bytes from disk)
[01:08:03] Connecting to http://128.143.48.226:8080/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (128.143.48.226:8080)
[01:08:03] + Retrying using alternative port
[01:08:03] Connecting to http://128.143.48.226:80/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (128.143.48.226:80)
[01:08:03] - Error: Could not transmit unit 02 (completed October 17) to work server.
[01:08:03] - 9 failed uploads of this unit.
[01:08:03] + Attempting to send results [October 18 01:08:03 UTC]
[01:08:03] - Reading file work/wuresults_02.dat from core
[01:08:03] (Read 1104801 bytes from disk)
[01:08:03] Connecting to http://128.143.48.227:8080/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (128.143.48.227:8080)
[01:08:03] + Retrying using alternative port
[01:08:03] Connecting to http://128.143.48.227:80/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (128.143.48.227:80)
[01:08:03] Could not transmit unit 02 to Collection server; keeping in queue.
[01:08:03] Project: 1751 (Run 2, Clone 55, Gen 7)
[01:08:03] + Attempting to send results [October 18 01:08:03 UTC]
[01:08:03] - Reading file work/wuresults_06.dat from core
[01:08:03] (Read 6346264 bytes from disk)
[01:08:03] Connecting to http://134.139.127.31:8080/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (134.139.127.31:8080)
[01:08:03] + Retrying using alternative port
[01:08:03] Connecting to http://134.139.127.31:80/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (134.139.127.31:80)
[01:08:03] - Error: Could not transmit unit 06 (completed October 11) to work server.
[01:08:03] - 47 failed uploads of this unit.
[01:08:03] + Attempting to send results [October 18 01:08:03 UTC]
[01:08:03] - Reading file work/wuresults_06.dat from core
[01:08:03] (Read 6346264 bytes from disk)
[01:08:03] Connecting to http://134.139.127.34:8080/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (134.139.127.34:8080)
[01:08:03] + Retrying using alternative port
[01:08:03] Connecting to http://134.139.127.34:80/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (134.139.127.34:80)
[01:08:03] Could not transmit unit 06 to Collection server; keeping in queue.
[01:08:03] Project: 3864 (Run 56, Clone 4, Gen 23)
[01:08:03] + Attempting to send results [October 18 01:08:03 UTC]
[01:08:03] - Reading file work/wuresults_08.dat from core
[01:08:03] (Read 2468469 bytes from disk)
[01:08:03] Connecting to http://128.143.48.226:8080/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (128.143.48.226:8080)
[01:08:03] + Retrying using alternative port
[01:08:03] Connecting to http://128.143.48.226:80/
[01:08:03] - Couldn't send HTTP request to server
[01:08:03] + Could not connect to Work Server (results)
[01:08:03] (128.143.48.226:80)
[01:08:03] - Error: Could not transmit unit 08 (completed October 12) to work server.
[01:08:03] - 39 failed uploads of this unit.
[01:08:03] + Attempting to send results [October 18 01:08:03 UTC]
[01:08:03] - Reading file work/wuresults_08.dat from core
[01:08:03] (Read 2468469 bytes from disk)
[01:08:03] Connecting to http://128.143.48.227:8080/
[01:08:04] - Couldn't send HTTP request to server
[01:08:04] + Could not connect to Work Server (results)
[01:08:04] (128.143.48.227:8080)
[01:08:04] + Retrying using alternative port
[01:08:04] Connecting to http://128.143.48.227:80/
[01:08:04] - Couldn't send HTTP request to server
[01:08:04] + Could not connect to Work Server (results)
[01:08:04] (128.143.48.227:80)
[01:08:04] Could not transmit unit 08 to Collection server; keeping in queue.
[01:08:04] + Sent 0 of 5 completed units to the server
[01:08:04] - Autosend completed
Re: 134.139.127.31 Cannot connect to work server
No, you did it correctly. I just wasn't understanding what you were saying.
You do have 5 WUs that have failed to upload. That represents 3 work servers and 3 collection servers which is pretty bad, but not as bad as I was suspecting.
WU 00 on servers 171.64.65.111 and 171.67.108.17
WU 01 on servers 171.64.65.111 and 171.67.108.17
WU 02 on servers 128.143.48.226 and 128.143.48.227
WU 06 on servers 134.139.127.31 and 134.139.127.34
WU 08 on servers 128.143.48.226 and 128.143.48.227
Servers 171.64.65.111 and 128.143.48.226 are somewhat busy but you should be getting through. Server 134.139.127.31 is very lightly loades so I'm suspecting that it's something on your end.
What kind of router do you have? What happens if you temporarily remove it from the area of concern by connecting the PC directly to the modem and restarting the client.
You do have 5 WUs that have failed to upload. That represents 3 work servers and 3 collection servers which is pretty bad, but not as bad as I was suspecting.
WU 00 on servers 171.64.65.111 and 171.67.108.17
WU 01 on servers 171.64.65.111 and 171.67.108.17
WU 02 on servers 128.143.48.226 and 128.143.48.227
WU 06 on servers 134.139.127.31 and 134.139.127.34
WU 08 on servers 128.143.48.226 and 128.143.48.227
Servers 171.64.65.111 and 128.143.48.226 are somewhat busy but you should be getting through. Server 134.139.127.31 is very lightly loades so I'm suspecting that it's something on your end.
What kind of router do you have? What happens if you temporarily remove it from the area of concern by connecting the PC directly to the modem and restarting the client.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: 134.139.127.31 Cannot connect to work server
I have a Dlink DIR 655 and see nothing in the router logs that suggests it is an issue.Servers 171.64.65.111 and 128.143.48.226 are somewhat busy but you should be getting through. Server 134.139.127.31 is very lightly loades so I'm suspecting that it's something on your end.
I can hit all 3 of these IP's with my browser and get the OK as well as able to ping to them. That suggests to me that my connectivity is fine, but possibly the folding client isn't waiting long enough and in essence times out when attempting to send. I have even tried restarting the folding client to force a send right after getting the OK as well as successful ping, but still no luck.
For fun, I checked my firewall logs and see nothing of note and even tried restarting the folding client with it off and get the same results.
I can try to remove the router, but as it exists to share connectivity throughout my home to all my other pc's, that test may have to wait for a day I am not that busy as well as anyone else here needing access to the internet. ..but again, if I can ping to the server, I'm not sure how it is my router.
Let me know if you have any other suggestions in the meantime. I really appreciate the help!
** quick update **
Just finished another WU and that one was able to transmit successfully. Here is that bit of log info..
Code: Select all
[15:22:49] + Attempting to send results [October 18 15:22:49 UTC]
[15:22:49] - Reading file work/wuresults_03.dat from core
[15:22:49] (Read 210512 bytes from disk)
[15:22:49] Connecting to http://171.67.108.13:8080/
[15:22:54] Posted data.
[15:22:54] Initial: 0000; - Uploaded at ~34 kB/s
[15:22:55] - Averaged speed for that direction ~37 kB/s
[15:22:55] + Results successfully sent
[15:22:55] Thank you for your contribution to Folding@Home.
[15:22:55] + Number of Units Completed: 8
Re: 134.139.127.31 Cannot connect to work server
Still not able to connect to these and now have another queue failing even though I have had successful returns on others during this time. I now have 6 queues out of 10 not able to return work. Please read above message for more details.