Hello jazzz,
What type of system are you installing on? Have you downloaded the BOINC package from WCG? What choices did you make when the installation program asked? What security programs are you trunning?

It has to be something simple.

Lawrence

Let's first establish if boinc.exe is loaded by visiting TaskManager. If the client was installed as service [protected application execution], then in the service tab BOINC would be showing as 'running'.

Then for boincmgr.exe to be able to connect to boinc.exe port 31416 must be open over localhost IP 127.0.0.1 to pass the RPC calls. In 99.9% of the cases this is transparent and the security suite has a pop-up or an option to auto-approve and remember the decision. With Norton semtex I am unsure... I've just last week uninstalled it after a 45 day of 60 day free trial [it came pre-installed with the machine]. Some of these purported 'security' packages deserve a visit of the hammer and wooden stick. They're a bigger impairment than a help [IMNSHO].

--//--

Success! - I think
I had to chmod the boinc-client file in /etc/init.d
start the client daemon
edit the /var/lib/remote_hosts.cfg to get rid of the 127.0.0.1 reference
then linked the BOINC_MANAGER to the desktop (for ease of use)
I then got the project list appearing and then I was able o click the project I wanted.
It started with no errors and I'm waiting for an update which will be slow as I'm connected via a cell phone/bluetooth combo which I think is G2 fast.
Sorry to ramble but mildly chuffed I got the thing working. Haven't used vi (or vim) for about 15 years.
Richard

Yes, as I've said in my last post few up, boincmgr.exe needs to connect to boinc.exe and does that via the localhost IP, which never leaves the machine [nothing suspicious but to some overzealous firewall software]. localhost = 127.0.0.1 unless you could specify differently, but expect the OS deals with this autonomously. Never had to specify differently even with NIC and WIFI simultaneously active.

Disabling network NIC has from long ago tests by me led to make it impossible for this to work, and networking you need to fetch tasks and report results. In my case only WIFI is active, and if that goes down, getting often failing tasks, a persistent weakness in BOINC IMHonestO. Much been said and much been ignored on this matter since 2006 when I first started using BOINC.

--//--