We are setting up a new network at work, and on the test system, neither Boinc nor SetiClassic will connet. I know that Classic uses port 5517, does Boinc use the same port.

Hopefully, I'll be able to convince the new admin to allow Boinc and/or Seti traffic through.

TIA

I believe that the boinc connection to the servers uses HTTP only. There is a different port used to allow remote control of the CLI.

> I believe that the boinc connection to the servers uses HTTP only. There is a
> different port used to allow remote control of the CLI.
> <a> href="http://www.boinc.dk/index.php?page=user_statistics&project=sah&userid=9915">
>

I assume you mean port 80? I don't think so, since as I said Boinc will not connect on the new network, and browsers work fine.

I ran Classic SETI behind a firewall that didn't allow ANY incoming ports, and it NEVER had any trouble. Classic SETI did not need any incoming ports opened because the client initiated all communications; the server just replied back through the same channel.

I'm running SETI/BOINC behind the same firewall and I have NOT opened any incoming ports at all. The SETI/BOINC client is NOT listening for any ports at this time, and it initiates all communications; the server replies back through the same channel.

What I'm saying is that you should not have to open any INCOMING ports for SETI/BOINC. You will have to allow OUTGOING connection attempts (mine defaults to "outgoing=open"). I just tested here and found that the SETI/BOINC client requests a connection TO port 80 on the server. The port on the client end (my system) is whatever port number the system choses as "next"; it changed every time I did an "Update" of the project. This is normal.

> > I believe that the boinc connection to the servers uses HTTP only. There
> is a
> > different port used to allow remote control of the CLI.
> > <a>
> href="http://www.boinc.dk/index.php?page=user_statistics&project=sah&userid=9915">
> >
>
> I assume you mean port 80? I don't think so, since as I said Boinc will not
> connect on the new network, and browsers work fine.
>
>

Sometimes helps to define the orxy server when using a proxy

-proxy servername:80 worked just fine.