I still can't connect, but I do see the new port.

---

hmmm

Have you done a cold boot(not just restart) afterwards?

Have you tried removing the permissions for all boinc items from your software firewall, then rebooting? It might get your firewall to recognize the exe's and ask about permission for them. I don't use the screensaver and when I upgrade boinc versions, I'm asked twice for permission. Once for boincmgr.exe and then again for boinc.exe. Are you?

tony

[edit], if I were using the screensaver, then when it tried to start I'd get asked for "outbound" access for the screensaver

hmmm

Have you done a cold boot(not just restart) afterwards?

Have you tried removing the permissions for all boinc items from your software firewall, then rebooting? It might get your firewall to recognize the exe's and ask about permission for them. I don't use the screensaver and when I upgrade boinc versions, I'm asked twice for permission. Once for boincmgr.exe and then again for boinc.exe. Are you?

tony

[edit], if I were using the screensaver, then when it tried to start I'd get asked for "outbound" access for the screensaver

Actaully I rebooted and I am good. Thanks.

When do you think this version will be released to the public?

---

Actaully I rebooted and I am good. Thanks.

When do you think this version will be released to the public?

I have no ETA on the next officially recommended release. I know we have another alpha client coming later this week. We've been through 1/2 a dozen since 5.2.13.

Glad it worked for you.

tony

Well I thought I had resolved the cannot connect issue when I modified the gui_rpc_auth.cfg file per some suggestions. That worked until I rebooted following a windows update.

The PROBLEM is back. I tried the various suggestions of executing boinc from a command prompt and that did allow boinc manager to connect and work to start but in all cases closing the command window disconnected the boinc manager and stopped all work. Yes boinc was still running in the background but nothing was actually happening.

Any more suggestions? Is someone working on a fix?

---

Following my previous post and query instead of opening a command window I tried executing boinc directly from the Start>run command with the redirectio parameter. This time when I closed out the command window that opened, boinc manager remained connected.

Again does anybody know the progress or timeline of a fix.

---

Following my previous post and query instead of opening a command window I tried executing boinc directly from the Start>run command with the redirectio parameter. This time when I closed out the command window that opened, boinc manager remained connected.

Again does anybody know the progress or timeline of a fix.

If you've read my previous posts, you'd know why it's doing what it's doing and how to fix it (as long as you accept the problems that come with developmental client). A new developmental version is on it's way. Noone knows when this developmental branch will be mature enough to release as official.

tony

Yes you are correct but that is a little more intimate to the firewall than I wanted to get. After your response I went to the NVIDIA firewall and discovered that custom one had a boinc 5.2.13 allow entry in it. I enabled custom 1 and everything is back to normal. Thanks

Following my previous post and query instead of opening a command window I tried executing boinc directly from the Start>run command with the redirectio parameter. This time when I closed out the command window that opened, boinc manager remained connected.

Again does anybody know the progress or timeline of a fix.

If you've read my previous posts, you'd know why it's doing what it's doing and how to fix it (as long as you accept the problems that come with developmental client). A new developmental version is on it's way. Noone knows when this developmental branch will be mature enough to release as official.

tony

---

Having tried everything I knew how to do, and most of what has been shown on the forum, I am still unable to connect. The following information is included, with the statement that both boinc.exe and boincmgr.exe are ok'd by my firewall, and in the authorized list.

[quote}Microsoft Windows XP Home[Version 5.1.2600] SP2
(C) Copyright 1985-2001 Microsoft Corp.

C:\\Documents and Settings\\John Egan.LOST-JOHN>netstat -a

Active Connections

Proto Local Address Foreign Address State
TCP lost-john:59 lost-john:0 LISTENING
TCP lost-john:auth lost-john:0 LISTENING
TCP lost-john:epmap lost-john:0 LISTENING
TCP lost-john:microsoft-ds lost-john:0 LISTENING
TCP lost-john:1025 lost-john:0 LISTENING
TCP lost-john:5101 lost-john:0 LISTENING
TCP lost-john:6060 lost-john:0 LISTENING
TCP lost-john:1082 lost-john:0 LISTENING
TCP lost-john:1268 lost-john:0 LISTENING
TCP lost-john:1604 localhost:31416 SYN_SENT
TCP lost-john:netbios-ssn lost-john:0 LISTENING
TCP lost-john:1035 cs21.msg.dcn.yahoo.com:nntp ESTABLISHED
TCP lost-john:1172 host86-139-14-215.range86-139.btcentralplus.com:
411 ESTABLISHED
TCP lost-john:1219 64.12.25.213:https ESTABLISHED
TCP lost-john:1270 sip23.voice.re2.yahoo.com:https ESTABLISHED
TCP lost-john:1527 c-f2fa72d5.1421-1-64736c10.cust.bredbandsbolaget
.se:13018 TIME_WAIT
TCP lost-john:1564 adsl-160-134.cytanet.com.cy:10424 TIME_WAIT
TCP lost-john:1583 62.23.204.20:http CLOSE_WAIT
TCP lost-john:1590 72.20.24.118:7000 ESTABLISHED
TCP lost-john:1605 c-f2fa72d5.1421-1-64736c10.cust.bredbandsbolaget
.se:13018 ESTABLISHED
TCP lost-john:1617 moonbeam.ircdshell.com:6667 ESTABLISHED
TCP lost-john:1698 kendo.shellux.net:7000 ESTABLISHED
TCP lost-john:2437 ats-rdd.dial.aol.com:5190 ESTABLISHED
TCP lost-john:2439 205.188.5.224:5190 ESTABLISHED
TCP lost-john:2457 baym-cs306.msgr.hotmail.com:1863 ESTABLISHED
TCP lost-john:3100 adsl-68-73-151-34.dsl.ipltin.ameritech.net:1411
ESTABLISHED
TCP lost-john:3435 68.44.60.252:1217 ESTABLISHED
TCP lost-john:4572 71-32-121-233.eugn.qwest.net:4411 ESTABLISHED
TCP lost-john:4574 host86-135-117-26.range86-135.btcentralplus.com:
50 ESTABLISHED
TCP lost-john:5002 edtntnt2-port-51.dial.telus.net:1024 ESTABLISHE
D
TCP lost-john:10696 64.125.158.115:7000 ESTABLISHED
TCP lost-john:epmap lost-john:0 LISTENING 0
TCP lost-john:1025 lost-john:0 LISTENING 0
UDP lost-john:microsoft-ds *:*
UDP lost-john:isakmp *:*
UDP lost-john:1026 *:*
UDP lost-john:1041 *:*
UDP lost-john:1047 *:*
UDP lost-john:1074 *:*
UDP lost-john:2463 *:*
UDP lost-john:3544 *:*
UDP lost-john:3618 *:*
UDP lost-john:4500 *:*
UDP lost-john:4596 *:*
UDP lost-john:1028 *:*
UDP lost-john:1032 *:*
UDP lost-john:1082 *:*
UDP lost-john:1267 *:*
UDP lost-john:1282 *:*
UDP lost-john:1900 *:*
UDP lost-john:2440 *:*
UDP lost-john:3203 *:*
UDP lost-john:3285 *:*
UDP lost-john:3482 *:*
UDP lost-john:discard *:*
UDP lost-john:netbios-ns *:*
UDP lost-john:netbios-dgm *:*
UDP lost-john:router *:*
UDP lost-john:1064 *:*
UDP lost-john:1900 *:*

C:\\Documents and Settings\\John Egan.LOST-JOHN>

Boinc Manager v5.3.17[/quote]

---