Hi,

I've been running Vista SP2 beta and RC, and remote connect to Boinc on Vista SP2 has not been a problem, but after SP2 RTM was installed I am no longer able to connect to Boinc from a remote computer. No error is reported on the Boinc manager I'm connecting from (it simply stays indefinitely on "connecting to xxxx.."), and on the remote Vista SP2 host there is no firewall port-blocks listed.

Bottom line is that the only change is the installation of the final version of SP2, and Boincmanager or BoincView are no longer able to remotely view/connect to boinc on the Vista SP2 host.

I know there are reports of other software that did encounter problems after SP2 RTM, but I've not seen Boinc listed (or generic rpc-issues)...

Anyone else...?

Morten

---

Morten Ross

My first guess would be that they closed all the firewall ports. Including the one that BOINC is trying to use. You may have to explicitly list the port as being open rather than to look to see if it is closed. I do not recall the port numbers that BOINC uses to connect...

My first guess would be that they closed all the firewall ports. Including the one that BOINC is trying to use. You may have to explicitly list the port as being open rather than to look to see if it is closed. I do not recall the port numbers that BOINC uses to connect...

BoincView says It's: 31416

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Hi,

I stated in initial post "..there is no firewall port-blocks listed.", so that's not the issue, unfortunately. Turning firewall off also does not change a thing.

Detatching from domain to see if some group policy setting was related to the changed behaviour also did not change the outcome.

Even switched between wired and wireless NIC, but same outcome.

There must be some undocumented change in SP2 RTM from SP2 RC, as RC did not have this behaviour.

Are there anyone else running Vista x86 Ultimate SP2 RTM?

Morten

---

Morten Ross

If boinc is not listed in your firewall then boincs ports are closed. You have to add boinc as allowed application in your firewall.
If boinc is already listed, as you state ports are open, you should check the settings what is allowed

.... And how does this apply when the firewall is turned off, as I have described?

---

Morten Ross

I missed that

Is it a fresh install of vista + sp2 or is it the system that was running the betas of sp2?

If it's your beta testing system i suggest to do a clean install of vista + sp2 to eliminate the possibility of interference with any beta junk

i'm installing sp2 atm, so you can wait until it's done, but be patient, it's my slowest notebook ;)

If it's your beta testing system i suggest to do a clean install of vista + sp2 to eliminate the possibility of interference with any beta junk

Hello,

I suggest not to install the SP2 until it is "officially" released and updates for other programs are available to work with the new version.

---

Am Ende ist nur Verwirrung

The RTM version is the officially version

I just installed it and the installation process was smoothly with a little hickup where it presented me the installer of hhd hexeditor again. But after installing hhd again everything works fine including BOINC and remote BOINC.

The RTM version is the officially version

I just installed it and the installation process was smoothly with a little hickup where it presented me the installer of hhd hexeditor again. But after installing hhd again everything works fine including BOINC and remote BOINC.

It is possible that XP has different rights/requirements and the account BOINC is on does not have the right to access the network. Rights can be a real pain.

---

i think there's no XP involved - all vista

and BOINC teached me the pain of rights, try to run it on a vista domain-client with restricted user rights and BOINC-devs better keep away from you ;)

i think there's no XP involved - all vista

and BOINC teached me the pain of rights, try to run it on a vista domain-client with restricted user rights and BOINC-devs better keep away from you ;)

You're right. Given that it is Vista, and Vista has a lot more "security" I would expect an update to SP2 to block applications -- not in a firewall, but to simply limit access to the IP stack itself.

---

The RTM version is the officially version

I just installed it and the installation process was smoothly with a little hickup where it presented me the installer of hhd hexeditor again. But after installing hhd again everything works fine including BOINC and remote BOINC.

Hi,

What did you test?

Did you test that a host other than the Vista SP2 could connect to BOINC on the Vista SP2 host?

Connecting to remote BOINCs FROM the Vista SP2 works OK, but not from remote hosts TO BOINC on the Vista SP2.

Morten

---

Morten Ross

I connected from a vista sp1 host using BOINC Manager

Perhaps i can test sp2 on a vista 64 host today

the host i tried yesterday has uac turned off with an admin account

OK i installed a new vista business x64 as a domain client today, sadly i forgot to test remote BOINC before i installed ESET smart security, so my first try to connect to BOINC from another host ended at the ESET firewall. I disabled the firewall and everything runs as expected. I set up a firewall rule and it still works - in both directions.

I believe one of the betas in conjunction with the rtm messed up your system

Hi Holger,

Yup - it seems so, as not even uninstalling SP2 helped (!!)...

I'm not sure I want to spend much more time on this, as I have no other issues a nd this is not really an important lack of functionality.

Thanks for your input :-)

Morten

---

Morten Ross