Uhm, at standard, the new 5.5.x versions don't show much messages in the Messages tab. You need to make a cc_config.xml file in the main BOINC folder and add to it what you want to be on, or off.

You can see the control options here: http://boinc.berkeley.edu/client_msgs.php

I'll add my cc_config.xml file as an example:

<cc_config>
<log_flags>
<task>1</task>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<state_debug>0</state_debug>
<task_debug>0</task_debug>
<file_xfer_debug>0</file_xfer_debug>
<sched_op_debug>0</sched_op_debug>
<http_debug>1</http_debug>
<work_fetch_debug>0</work_fetch_debug>
<proxy_debug>0</proxy_debug>
<time_debug>0</time_debug>
<net_xfer_debug>0</net_xfer_debug>
<measurement_debug>0</measurement_debug>
<poll_debug>0</poll_debug>
<guirpc_debug>0</guirpc_debug>
<scrsave_debug>0</scrsave_debug>
</log_flags>
</cc_config>

---

My first impression is that the Windows Boinc 5.5.16 works flawlessly behind NTLM. Each communication is done at the first try, no unsuccessful retries...

I tried to update Seti Beta, Boinc contacted the proxy, upon request immediately continued with authentication (no more attempts to go on unauthenticated), succeeded with it and sent request + received answer. (Then, off course, Pirates attempted few times to get a piece of work too and immediately got clear answer "Pirates@Home|Scheduler RPC succeeded [server version 503] - No work from project" within few seconds.

Some while later Malaria finished and then successfully uploaded its result in 4 seconds (exactly mixed with Pirates' request for work, which took 5 seconds). Then I manually reported Malaria's work, it took 5 seconds and said "malariacontrol.net beta|Scheduler RPC succeeded [server version 504]".

I hope the NTLM nightmare could be considered to be solved ;-)
But will keep it in eye...

If maybe Walt would be interested in my logs, I've switched on following flags (among others, while playing with them, ncpus=2 is a nice toy :) - file_xfer file_xfer_debug http_debug proxy_debug net_xfer_debug. Now I'm listening also to the boinc_alpha stream (but still too shy to post there :)

So, YES!!

Peter

My first impression is that the Windows Boinc 5.5.16 works flawlessly behind NTLM. Each communication is done at the first try, no unsuccessful retries...

My second impression is the same. Tried with 3 different projects - upload and report, first without authentification (I forgot to switch it on) - correctly failed, then authentificated - it correctly went through.

Looking forward to 5.6.1 (with better shortfalls)...

Peter

Looking forward to 5.6.1 (with better shortfalls)...

Peter

5.6.0 you mean... ;-)

It's out now, still in Alpha.

---

No, I've really meant 5.6.1, as JM7 commented on 5.6.0 probably haveing problems with shortfall calculations.

No, I've really meant 5.6.1, as JM7 commented on 5.6.0 probably haveing problems with shortfall calculations.

Peter ;-D

P.S.: But 5.5.16 is currently working good for me.

No, I've really meant 5.6.1, as JM7 commented on 5.6.0 probably haveing problems with shortfall calculations.

No, I've really meant 5.6.1, as JM7 commented on 5.6.0 probably haveing problems with shortfall calculations.

LOL

The forums hung up on me for 15 minutes... It's now only one post. But thanks. ;-)

---

Hi

Not happy to break your optimism...
Still cannot connect, even in 5.6.0.
I can try to set messages more detailed (actually I already did it), but there are some details obout our company proxy, which I don't want to spread over i-net. I can send detailed message list to Rom Walton or other BOINC team member, if the want it.



31.8.2006 6:08:12|LHC@home|URL: http://lhcathome.cern.ch/; Computer ID: 81548; location: home; project prefs: default
31.8.2006 6:08:12|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 1286707; location: work; project prefs: default
31.8.2006 6:08:12||General prefs: from SETI@home (last modified 2006-05-04 10:10:44)

31.8.2006 6:08:12||General prefs: using separate prefs for work
31.8.2006 6:08:13|SETI@home|Started upload of file 14ap06aa.18057.25584.890912.3.109_1_0
31.8.2006 6:08:13|SETI@home|Started upload of file 14ap06aa.18057.25584.890912.3.84_3_0
31.8.2006 6:08:13|SETI@home|Restarting task 15ap06ab.13135.10290.311076.3.108_3 using setiathome_enhanced version 515
31.8.2006 6:08:14|LHC@home|Sending scheduler request: To fetch work
31.8.2006 6:08:14|LHC@home|Requesting 63637 seconds of new work
31.8.2006 6:08:18|LHC@home|Scheduler RPC succeeded [server version 503]
31.8.2006 6:08:18|LHC@home|No work from project
31.8.2006 6:08:18|LHC@home|Deferring scheduler requests for 1 minutes and 0 seconds
31.8.2006 6:08:22||Project communication failed: attempting access to reference site
31.8.2006 6:08:22|SETI@home|Temporarily failed upload of 14ap06aa.18057.25584.890912.3.84_3_0: http error
31.8.2006 6:08:22|SETI@home|Backing off 1 hours, 25 minutes and 47 seconds on upload of file 14ap06aa.18057.25584.890912.3.84_3_0
31.8.2006 6:08:22|SETI@home|Started upload of file 15ap06ab.13135.10290.311076.3.105_2_0
31.8.2006 6:08:23||Access to reference site succeeded - project servers may be temporarily down.
31.8.2006 6:08:25||Project communication failed: attempting access to reference site
31.8.2006 6:08:26|SETI@home|Temporarily failed upload of 15ap06ab.13135.10290.311076.3.105_2_0: http error
31.8.2006 6:08:26|SETI@home|Backing off 5 minutes and 4 seconds on upload of file 15ap06ab.13135.10290.311076.3.105_2_0
31.8.2006 6:08:26|SETI@home|Started upload of file 15ap06ab.13135.10290.311076.3.86_0_0
31.8.2006 6:08:27||Access to reference site succeeded - project servers may be temporarily down.
...
Edit:
31.8.2006 6:18:23|LHC@home|Sending scheduler request: To fetch work
31.8.2006 6:18:23|LHC@home|Requesting 62633 seconds of new work
31.8.2006 6:18:28|LHC@home|Scheduler request failed: Error 400
31.8.2006 6:18:28|LHC@home|Deferring scheduler requests for 1 minutes and 0 seconds

---

I can send detailed message list to Rom Walton or other BOINC team member, if the want it.

Please send the log to me at elst93 at gmail dot com

---

Would like to say thank you to the guys at BOINC. I finaly found a new version that works with my network at work. Spok, try 5.6.3. I had all the same problems you were with my connection at work.

---

I had no time last month in work, so first testing today. Last week I just updated to BOINC 5.6.4, but no progress on my side. When I press <Retry> in Upload/Download tab, file status change to "Uploading" size goes up from i.e. 0/9.99 KB to 10.71/9.99 KB and then it stays for five minutes. After five minutes http error is announced.
The same behaviour is in BOINC 5.6.5

I have to wait for five minutes now and then I will messages to you, Ageless.

Spok

---

Yeah, long time ago I had time to do some testing at work. Good news, at least for me. Version 5.8.3 can communicate with servers, upload, download, etc.

Have no idea what happened, but it works :)

Spok

---

New libCurl version.... ;-)

---