I have been using BOINC 5.10.28 fine. Last night my computer had Windows patches installed, and proxy connection authentification failed. I tried installing 5.10.30, that also would not connected with the proxy. I had to go back to BOINC 5.8.16, which is working fine.

Anybody now if MS has made any changes to the NTLM authentificaiton procedures?

---

You need a second life? Seconlife.com

I have been using BOINC 5.10.28 fine. Last night my computer had Windows patches installed, and proxy connection authentification failed. I tried installing 5.10.30, that also would not connected with the proxy. I had to go back to BOINC 5.8.16, which is working fine.

Anybody now if MS has made any changes to the NTLM authentificaiton procedures?

I see some network changes upcoming for SP3, but I haven't paid attention to prior updates. Do you know which updates were applied last night?

I had some updates applied to my Windows 2000 Server system last week that seems to have trashed my entire cache of WUs on that machine. I ended up doing a detach and re-attach hoping that it would reset my daily quota which had been reduced to a whole 8/day/CPU. Didn't work though. I still have to check it out once I get home from work because it hasn't contacted SETI@Home in over three days.

---

I had some updates applied to my Windows 2000 Server system last week that seems to have trashed my entire cache of WUs on that machine. I ended up doing a detach and re-attach hoping that it would reset my daily quota which had been reduced to a whole 8/day/CPU. Didn't work though. I still have to check it out once I get home from work because it hasn't contacted SETI@Home in over three days.

Perhaps fortuitously, I haven't got round to patching my W2K server yet (it's only doing file/print server roles behind a hardware firewall, so I don't feel it's terribly urgent).

I can see two updates pending which might be significant for BOINC/SETI:

KB941568: Security Update for DirectX 9 for Windows 2000
KB937894: Security Update for Windows 2000 [vulnerability in Message Queuing Service]

HTH

I had some updates applied to my Windows 2000 Server system last week that seems to have trashed my entire cache of WUs on that machine. I ended up doing a detach and re-attach hoping that it would reset my daily quota which had been reduced to a whole 8/day/CPU. Didn't work though. I still have to check it out once I get home from work because it hasn't contacted SETI@Home in over three days.

Perhaps fortuitously, I haven't got round to patching my W2K server yet (it's only doing file/print server roles behind a hardware firewall, so I don't feel it's terribly urgent).

I can see two updates pending which might be significant for BOINC/SETI:

KB941568: Security Update for DirectX 9 for Windows 2000
KB937894: Security Update for Windows 2000 [vulnerability in Message Queuing Service]

HTH

How would MSMQ affect BOINC? I don't even have MSMQ installed on my XP installation... It would be cool though if the communication layer could be switched over to MSMQ with persistency. For those averse to Microsoft, another method could be WebSphere MQ (MQ Series).

I had some updates applied to my Windows 2000 Server system last week that seems to have trashed my entire cache of WUs on that machine. I ended up doing a detach and re-attach hoping that it would reset my daily quota which had been reduced to a whole 8/day/CPU. Didn't work though. I still have to check it out once I get home from work because it hasn't contacted SETI@Home in over three days.

Perhaps fortuitously, I haven't got round to patching my W2K server yet (it's only doing file/print server roles behind a hardware firewall, so I don't feel it's terribly urgent).

I can see two updates pending which might be significant for BOINC/SETI:

KB941568: Security Update for DirectX 9 for Windows 2000
KB937894: Security Update for Windows 2000 [vulnerability in Message Queuing Service]

HTH

How would MSMQ affect BOINC? I don't even have MSMQ installed on my XP installation... It would be cool though if the communication layer could be switched over to MSMQ with persistency. For those averse to Microsoft, another method could be WebSphere MQ (MQ Series).

I didn't know enough to judge whether it would be significant, so I left it in there for OzzFan to see and form his own opinion. For the record, I judged it safe not to bother mentioning the other two - IE6 security patches and Malicious Software Removal Tool.

. . . just after installing the MS Updates for XP Pro - i flushed the DNS etc . . . and everythings workin' fine on that box

---

BOINC Wiki . . .

Science Status Page . . .

I can see two updates pending which might be significant for BOINC/SETI:

KB941568: Security Update for DirectX 9 for Windows 2000
KB937894: Security Update for Windows 2000 [vulnerability in Message Queuing Service]

HTH

How would MSMQ affect BOINC? I don't even have MSMQ installed on my XP installation... It would be cool though if the communication layer could be switched over to MSMQ with persistency. For those averse to Microsoft, another method could be WebSphere MQ (MQ Series).

I didn't know enough to judge whether it would be significant, so I left it in there for OzzFan to see and form his own opinion. For the record, I judged it safe not to bother mentioning the other two - IE6 security patches and Malicious Software Removal Tool.

Well, if applied to BOINC, the benefit would be guaranteed result upload/download delivery. The projects could also conceivably make the auto-abort functionality a persistent queue.

Anyway, the major problem is that it would be impossible to manage due to the computers not being forced to adhere to a specific installation policy. People could go in and tinker with their persistency setting or uninstall it (or not install it in the first place)...

Edit: Ozzfan's issue seems to be something related to memory access. The information about that particular error code is vast and diverse if you look for it on Google...

I see some network changes upcoming for SP3, but I haven't paid attention to prior updates. Do you know which updates were applied last night?

I the following update logs where created:
KB937894.log
KB941568.log
KB941569.log
KB942615.log
KB944653.log
KB893357.log
KB898461.log
KB910437.log
KB916595.log
KB920342.log
KB920872.log
KB922582.log
KB927891.log
KB936357-v2.log


I have not checked out what they are yet.

[Edit} >>>>>>
I turned on http-debug, and proxy-debug. This is what part of the log showed when not working with 5.10.28.....................
===========================================================================
20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] info: Issue another request to this URL: 'http://boinc.bio.wzw.tum.de/boincsimap_cgi/cgi'
20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] info: About to connect() to proxy 172.16.1.80 port 8080 (#0)
20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] info: Trying 172.16.1.80...
20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] info: Connected to 172.16.1.80 (172.16.1.80) port 8080 (#0)
20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] info: Proxy auth using NTLM with user 'mpirwad'
20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Sent header to server: POST http://boinc.bio.wzw.tum.de/boincsimap_cgi/cgi HTTP/1.1

Proxy-Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=

User-Agent: BOINC client (windows_intelx86 5.10.28)

Host: boinc.bio.wzw.tum.de

Pragma: no-cache

Accept: */*

Accept-Encoding: deflate, gzip

Referer: http://boinc.bio.wzw.tum.de/boincsimap_cgi/cgi

Proxy-Connection: Keep-Alive

Content-Type: application/x-www-form-urlencoded

Content-Length: 0



20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Received header from server: HTTP/1.1 407 Proxy Authentication Required

20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Received header from server: Proxy-Authenticate: NTLM TlRMTVNTUAACAAAAAwADADgAAAAGgokCRmXEaMfLl+wAAAAAAAAAAIYAhgA7AAAABQLODgAAAA9NUEkCAAYATQBQAEkAAQAMAFMASQBSAEkAVQBTAAQAGgBhAGQALgBtAHAAaQBjAC4AbQBiAC4AYwBhAAMAKABzAGkAcgBpAHUAcwAuAGEAZAAuAG0AcABpAGMALgBtAGIALgBjAGEABQAaAGEAZAAuAG0AcABpAGMALgBtAGIALgBjAGEAAAAAAA==

20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Received header from server: Cache-Control: no-cache

20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Received header from server: Pragma: no-cache

20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Received header from server: Content-Type: text/html; charset=utf-8

20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Received header from server: Proxy-Connection: Keep-Alive

20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Received header from server: Set-Cookie: BCSI-CS-B8802DA337D7EC3C=2; Path=/

20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Received header from server: Connection: Keep-Alive

20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Received header from server: Content-Length: 830

20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] info: the ioctl callback returned 0
20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] Received header from server:

20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] info: Ignoring the response-body
20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] info: Expire cleared
20-Dec-2007 11:47:48 [---] [http_debug] [ID#2] info: Closing connection #0

---

You need a second life? Seconlife.com

This is what is looks like when it works with 5.8.16:
==============================================================================

2007-12-20 14:40:41 [---] [http_debug] [ID#0] info: Issue another request to this URL: 'http://boinc.bio.wzw.tum.de/boincsimap_cgi/file_upload_handler'
2007-12-20 14:40:41 [---] [http_debug] [ID#0] info: Examining connection #0 for reuse
2007-12-20 14:40:41 [---] [http_debug] [ID#0] info: Connection #0 seems to be dead!
2007-12-20 14:40:41 [---] [http_debug] [ID#0] info: Closing connection #0
2007-12-20 14:40:41 [---] [http_debug] [ID#0] info: About to connect() to proxy 172.16.1.80 port 8080 (#0)
2007-12-20 14:40:41 [---] [http_debug] [ID#0] info: Trying 172.16.1.80...
2007-12-20 14:40:41 [---] [http_debug] [ID#0] info: Connected to 172.16.1.80 (172.16.1.80) port 8080 (#0)
2007-12-20 14:40:41 [---] [http_debug] [ID#0] info: Proxy auth using Basic with user 'mpirwad'
2007-12-20 14:40:41 [---] [http_debug] [ID#0] Sent header to server: POST http://boinc.bio.wzw.tum.de/boincsimap_cgi/file_upload_handler HTTP/1.1

Proxy-Authorization: Basic bXBpcndhZDoxMW5vdjA1

User-Agent: BOINC client (windows_intelx86 5.8.16)

Host: boinc.bio.wzw.tum.de

Pragma: no-cache

Accept: */*

Accept-Encoding: deflate, gzip

Referer: http://boinc.bio.wzw.tum.de/boincsimap_cgi/file_upload_handler

Proxy-Connection: Keep-Alive

Content-Type: application/x-www-form-urlencoded

Content-Length: 271



2007-12-20 14:40:41 [---] [http_debug] [ID#0] info: Expire cleared
2007-12-20 14:40:41 [---] [http_debug] [ID#0] Received header from server: HTTP/1.1 200 OK

2007-12-20 14:40:41 [---] [http_debug] [ID#0] Received header from server: Date: Thu, 20 Dec 2007 20:40:41 GMT

2007-12-20 14:40:41 [---] [http_debug] [ID#0] Received header from server: Server: Apache/2.2.3 (CentOS)

2007-12-20 14:40:41 [---] [http_debug] [ID#0] Received header from server: Content-Type: text/plain; charset=UTF-8

2007-12-20 14:40:41 [---] [http_debug] [ID#0] Received header from server: Transfer-encoding: chunked

2007-12-20 14:40:41 [---] [http_debug] [ID#0] Received header from server: Proxy-Connection: Keep-Alive

2007-12-20 14:40:41 [---] [http_debug] [ID#0] Received header from server: Connection: Keep-Alive

2007-12-20 14:40:41 [---] [http_debug] [ID#0] Received header from server: Age: 0

---

You need a second life? Seconlife.com

This is what is looks like when it works with 5.8.16:

2007-12-20 14:40:41 [---] [http_debug] [ID#0] info: Proxy auth using Basic with user 'mpirwad'

I have no clue about the difference between Basic and NTLM, but clearly there is a difference there. Perhaps 5.10.xx using Basic would also work? Again, no clue on how you go about changing that kind of stuff. Never felt the need to proxy anything, as a router is good enough for me...

Edit: On the positive side of things, if NTLM doesn't work for you on 5.8.16 or 5.10.xx, then you would be the lucky winner of the "Help Figure Out Why NTLM Proxies Don't Work" award...so that maybe finally the minimum version can be moved up to get rid of the 5.2.6 and older BOINC clients...

Reposting from BOINC V5.2.5* and earlier :-(:

There are a couple of recent threads on the BOINC dev message board which seem to throw some constructive light on this problem:

Communication via proxy is never authenticated: a user with access to his own proxy logs has shown that BOINC is working to the proxy in 'anonymous' mode, rather than using the security credentials provided.

Internet access thru proxy: a free download with worked example configuration gets round the problem, pending a fix.

Seems like a similar set of problems/diagnosis/workround.