Messages

That did the trick.

Thank you Fred.

Thanks Fred

Encrypt was already deselected (empty box).
Passwords in place but I re-entered to be sure.
Restarted BT - no change.....

Hi,

Have a problem that I don't think is any BT defect but does stop BT from fully functioning.

I have used BT successfully for some time, but last week replaced my main machine and ran into the problem.
Machine is...
Asus P5K WS
Core 2 Duo E4500
Win XP Pro SP3 and all updates (fresh install)
BT 1.15
Boinc 6.10.58

Problem is BT reads & displays remote machines fine but I have no control functions at all.

The log displays the following which I assume is the problem...
ERROR: CryptAcquireContext ---- Error 80090016

Have Gurgled for solutions but failed to resolve it.
Tried a couple of things eg flushing RSA folder to no avail.
Much of what I have found associated with the problem I simply don't understand.

From MS...
CryptAcquireContext errors
The following are the most common error codes and possible reasons for the error.

    * NTE_BAD_KEYSET (0x80090016)
          o Key container does not exist.
          o You do not have access to the key container.
          o The Protected Storage Service is not running.
       
Protected Storage is running but keys I don't understand and can't advise status.
I note that if I start BT in the previous main machine I have normal full control of Boinc on the new machine, so it is a one way deficiency only.

I would be grateful if someone can tell me if the above mentioned error is really the problem. And also if someone can help me solve the issue or even point me to where I can find an easily understood solution.

Thanks.

I can now confirm that this was the problem all along.

On the project website I have checked the returned task results of cruncher from a couple of days ago and BT says they were returned by another machine.

It seems to me that following numerous machine boots, router boots and a BT upgrade, this instance of BT has somehow failed to recognise reassigned dynamic LAN IP's.
The BT on the main machine has clearly coped as it has not failed to connect all along.

Solved!!  Party time!
Put hammer away.

Went out for a while and on return noticed in BT that machine 5 had picked up a new task for a project it isn't allowed to run.  How strange.  Checked project website and found that task was issued to machine 9. Ah ha!
Carefully compared work in BT with work in BMgr on machines.  Oops nothing adds up in several machines.
BT computers tab -> IP addresses are wrongly assigned to machines.  eg BT shows machine 9's IP and data as being from machine 5.
Manually changed/corrected 4 IP addresses and all is well - with all computers now connected.

How this came about I have no idea.  Perhaps it was a BT error all along? I'm not even sure if this was the problem from the beginning of the troubles.

Anyway thanks for your generous efforts to help Fred.

Cheers

Reinstalled Boinc for no change.
Reset router and tried several other things too.

Then I uninstalled all the network drivers on the machine which I have BT on.
Installed latest drivers.
Bingo, that fixed cruncher.  Connecting OK now.

Downside is I now have 2 other machines I can't connect to with all the same symptoms. Identical messages etc. Main machine still connects to everything fine.
Definitely a case of one step forward and two back!
Getting close to the big hammer repair.

Seems to me this is not a BT defect at all, but any further suggestions are welcomed.

Cheers.

Already had the cc_config option in place before posting.
Obviously that didn't help.

It sure is a head scratcher.
I just don't see any logical answer.
If cruncher had a problem, main machine also shouldn't connect.
If 2nd machine had a problem it shouldn't connect to the other 5 machines.

I have stopped fetching new tasks and when cruncher runs out of work in about 6 hrs I'm going to reinstall Boinc.  Don't have any reason to think that will fix it but trying anything at this stage.

Indeed it is.
Started out with names as mentioned in my 1st post.
Have since added IP.
Current status is name only of main machine (connects), name plus IP of second machine.
Have redone the file twice to ensure no invisible spaces or other corruption exists.

From boinc messages...

23/09/2010 10:42:51 p.m.      GUI RPC request from non-allowed address 10.1.1.10

I have turned off Win firewall and uninstalled AVG , rebooted to no avail.
What stumps me is one machine can access and other can't.
If it was firewall or AV I'd expect both machines to be blocked.

(10.1.1.10 is the correct IP for the BT machine that can't connect)

Not sure if relevant but might eliminate some possibilities...

Cruncher is a boinc dedicated machine.
Well not even a whole machine - just a mobo, psu and hdd sitting on a shelf in the basement.
Nothing else runs on it other than OS, AV and Boinc.
I operate it by remote desktop.

Hi Fred,

Yes BT log....
23 September 2010 - 20:22:38 Connect, read error ---- Host: 10.1.1.9,cruncher,Port: 31416, Error Number: -102

Just updated to .74 no change.

31416 is open and boinc.exe is listening on it....

Protocol           [TCP]
Program [PID]   boinc.exe [2704]
State              Established
Local Address   10.1.1.9 (cruncher)
Port              31416
Remote Address    10.1.1.13
Remote Port   1052
Path and File   C:\Program Files\BOINC\boinc.exe   
Description   BOINC client

(NB 10.1.1.13 is main machine)
When I close BT on main machine....

Protocol           [TCP]
Program [PID]   boinc.exe [2704]
State              Listening
Local Address   0.0.0.0  (cruncher)
Port              31416
Remote Address    0.0.0.0
Remote Port   0
Path and File   C:\Program Files\BOINC\boinc.exe   
Description   BOINC client

Since my last post I have tried remote connections using Boinc Mgr. Same result.
I can connect to all other machines except cruncher from 2nd BT machine. 
Main machine connects through BM to any/all including cruncher without any problems.

Greetings.

I have 7 (6+localhost) machines monitored by BT from my main PC.  I have now installed BT on one of the other machines on the network and can't get it to connect to one other machine - the others all connect fine.  All machines including the troublesome one are still connected OK to the 1st copy of BT.
The problem shows as being a read error -102.
Have extensively read old threads regarding connection issues but not found any solution.

Running BT .71, Win XP SP3, all config files identical and password is common to all machines. Have traditionally used names in hosts files without trouble but have added IP (and rebooted) but no change.   
All running the same firewall and AV settings. Don't have TThrottle on any.

Any suggestions welcome and appreciated as I've run out of ideas.