Running BOINC 4.32 with S@H 4.09 and ClimatePrediction 4.10 on WinXP-SP2.

When rebooting Windows I get a pop-up "Connection Failed". I can see the BOINC Manager icon in the systray, and when I open it there are no projects, and an information at the bottom says "Disconnected".

When I exit BOINC Manager and start anew, then the projects attach and start crunching.

I have not seen this behavior before 4.32 (I think).

---

open BOINC, Go to file, then select computer, then hit OK and you should connect, if that fails enter localhost and then enter and that should connect.....

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

> open BOINC, Go to file, then select computer, then hit OK and you should
> connect, if that fails enter localhost and then enter and that should
> connect.....

Thanks; I will try that next time I reboot.

I have the same problem too..
I think the reason for this is antivirus software..
When my computer starts my antivirus(Norton 2005)
scans all programs in memory. This results boinc manager
to freeze for 3-4 seconds on the desctop.. This leads
to the expiration of the "waiting to connect" time.
The above post gives a solution but I think it is
boring to do this every time my pc boots...
So, why can't they extend this time ?

---

Firegate_13 Was Here!
BeWare!
Patras Wireless Metropolitan NetWork

> So, why can't they extend this time ?
>

I have the same issue, how can we get an extended delay added to the wish list?

---

> > So, why can't they extend this time ?
> >
>
> I have the same issue, how can we get an extended delay added to the wish
> list?
>
Agreed!
But why not have it try multiple times - let us say once every 15 seconds until it succeeds or until 2 minutes, then fail with the message box that it now has.
Does anybody involved in the maintenance of BOINC read these threads? If so can you confirm whether something will be done to address this problem? Can you please do the same for other threads?

---

BESTEST!

> But why not have it try multiple times - let us say once every 15 seconds
> until it succeeds or until 2 minutes, then fail with the message box that it
> now has.

End result would be some serious hammering of the server when everyone tries to connect after an outage. And it's already bad enough as it is.

Just increasing the intial timeout value by 20% would be more than sufficient i would think.

---

Grant
Darwin NT

> > But why not have it try multiple times - let us say once every 15
> seconds
> > until it succeeds or until 2 minutes, then fail with the message box that
> it
> > now has.
>
> End result would be some serious hammering of the server when everyone tries
> to connect after an outage. And it's already bad enough as it is.
>
> Just increasing the intial timeout value by 20% would be more than sufficient
> i would think.
>
I bow to your superior and more informed suggestion!

---

BESTEST!

i've registered myself on the bug reporting system and logged this isue there. I've included a link to this thread so let's see what happens.

---

I have the same problem on two PC's (Win2000 / WinXP pro SP2). It looks like my WinME machine does not have this problem. All are running Boinc 4.35.
To try to get Boincmanager to start later I introduced a delay of 60 seconds after logging on to Windows2000.


I made a bach file that started from the Windows startup folder, waited for 60 seconds and started Boincmanager. This is what happened:

Windows started normally, as well as the batch file. 45 Seconds after logging on (it's a slow PC), Windows and all programs completely started. For 15 seconds there was no harddisk activity. Then the batch file continued and started Boincmanager..... and the "connection failed" message appeared again. :-(

So this delay does NOT help. Closing and starting Boincmanager after the failure works fine. Or just going to "file-select computer" and pressing Enter works to get a connection.


It looks like only the first time Boinc starts from the startup folder after a system boot it is not able to establish a connection. Strange.

Curious.
Is everyone with "Connection Failed" on every boot running behind a Software Firewall or Virus protection?
Also, do links to projects through GUI cause problems?
I have intermittant problems with ZoneAlarm.
Seen other reports of AntiVirus software not working nice with BOINC.

---

<blockquote>Curious.
Is everyone with "Connection Failed" on every boot running behind a Software Firewall or Virus protection?
Also, do links to projects through GUI cause problems?
I have intermittant problems with ZoneAlarm.
Seen other reports of AntiVirus software not working nice with BOINC.</blockquote>

here is my Sort of Work around,

The best way so far is to Install the new App but dont run it untill
you go to internet apps and re give it permissions. BOINC.EXE BOINCmgr. and BOINC.SCR....... Then run the program.

Works 98% of the time.

---

At the moment I have three PC's with this problem, two without. For the other PC's I'm afraid to upgrade, because they are on someones desk at work and I don't want to bother that people with the popup windows. And well... if they only click the error window away, Boinc doesn't work anyway.

The three PC's that do have the problem all have a firewall. Two are using ZoneAlarm, the other is using the internal Windows XP SP2 firewall. So the problem is not specific to ZA.
The Windows firewall does NOT ask anything after upgrading Boinc, it just allows the program access and does not bother about upgrades. So I assume this should always work.

PC1: Pentium 4 - 2.26GHz - 512Mb RAM - WinXP Pro SP2 - Windows firewall
PC2: Pentium 4 - 2.4GHz - 512Mb RAM - Win2000 - ZoneAlarm firewall
PC3: Pentium 3 - 500MHz - 128Mb RAM - Win2000 - ZoneAlarm firewall


Two computers (at home) do NOT have this problem. They are connected to PC1 for internet access (ADSL) and do not have a firewall installed.

Boinc is installed as single user on all 5 PC's.

Both my machines have the problem - one with XP Pro SP1 and the other with WIN2K - both running ZoneAlarm, one with Symantic Anti-Virus and the other with e-Trust Anti-Virus.

---

BESTEST!

ok.
For me the fix is in 4.43
This bug seems to be gone in all 4 crunchers with this problem.
Somebody else here wanna give it a shot?

---

I've got 4.42 and have this problem too. Zonelabs seems to think BOINC is trying to connect before ZoneAlarm has a chance to fully load. The part of ZoneAlarm that has loaded is blocking the connection until it finishes loading and finds out what the program is that's trying to connect. I've had alerts since I upgraded from an earlier version a couple of days ago.

svchost.exe caused some alerts trying to connect to Port 53 of a DNS server via UDP, here's the info on Zonelabs' site:
http://fwalerts.zonelabs.com/fwanalyze.jsp?record=ZLN32950396863444-1025/12bf5600103f68f6b9a001103&tab=details

Another repeated alert tried to connect to Port 80 of another computer via TCP (flag:S)
http://fwalerts.zonelabs.com/fwanalyze.jsp?record=ZLN32950396863444-1025/e0c07c0103f68f7edf00b77&tab=details

Hope this helps track down the problem.

---

ok.
For me the fix is in 4.43
This bug seems to be gone in all 4 crunchers with this problem.
Somebody else here wanna give it a shot?

Still got the same problem here with 4.43

---

I've got 4.42 and have this problem too. Zonelabs seems to think BOINC is trying to connect before ZoneAlarm has a chance to fully load. The part of ZoneAlarm that has loaded is blocking the connection until it finishes loading and finds out what the program is that's trying to connect. I've had alerts since I upgraded from an earlier version a couple of days ago.

svchost.exe caused some alerts trying to connect to Port 53 of a DNS server via UDP, here's the info on Zonelabs' site:
http://fwalerts.zonelabs.com/fwanalyze.jsp?record=ZLN32950396863444-1025/12bf5600103f68f6b9a001103&tab=details

Another repeated alert tried to connect to Port 80 of another computer via TCP (flag:S)
http://fwalerts.zonelabs.com/fwanalyze.jsp?record=ZLN32950396863444-1025/e0c07c0103f68f7edf00b77&tab=details

Hope this helps track down the problem.

Fairly sure these alerts are caused by BOINC, but can anyone else with a firewall (or anyone from BOINC) verify this for me? It's possible I have another program causing these alerts.

---

I've got 4.42 and have this problem too. Zonelabs seems to think BOINC is trying to connect before ZoneAlarm has a chance to fully load. The part of ZoneAlarm that has loaded is blocking the connection until it finishes loading and finds out what the program is that's trying to connect. I've had alerts since I upgraded from an earlier version a couple of days ago.

svchost.exe caused some alerts trying to connect to Port 53 of a DNS server via UDP, here's the info on Zonelabs' site:
http://fwalerts.zonelabs.com/fwanalyze.jsp?record=ZLN32950396863444-1025/12bf5600103f68f6b9a001103&tab=details

Another repeated alert tried to connect to Port 80 of another computer via TCP (flag:S)
http://fwalerts.zonelabs.com/fwanalyze.jsp?record=ZLN32950396863444-1025/e0c07c0103f68f7edf00b77&tab=details

Hope this helps track down the problem.

Fairly sure these alerts are caused by BOINC, but can anyone else with a firewall (or anyone from BOINC) verify this for me? It's possible I have another program causing these alerts.

Nope, these alerts seem not to be caused by BOINC starting up after all. I got the Connection Failed pop-up this morning with no firewall alerts for the last 2 days, go figure!

---

Still got the same problem here with 4.43

Yep. After a couple days and several reboots this problem reappeared on one of my hosts so far.
Aaargh!