Thread 'Unable to connect using 7.2.33 (x64)'

Message boards : BOINC Manager : Unable to connect using 7.2.33 (x64)
Message board moderation

To post messages, you must log in.

AuthorMessage
mmathis

Send message
Joined: 8 Jan 14
Posts: 5
United States
Message 51949 - Posted: 8 Jan 2014, 17:30:03 UTC
Last modified: 8 Jan 2014, 17:30:59 UTC

I've been unable to connect for the past week (approx.) using the client above. I've uninstalled, reinstalled, read some old posts and opened the firewall to both boincmgr and boinc. Nothing is working.

Any assistance out there?

btw, I'm on a Windows 7 Professional OS.
ID: 51949 · Report as offensive
ChristianB
Volunteer developer
Volunteer tester

Send message
Joined: 4 Jul 12
Posts: 321
Germany
Message 51956 - Posted: 9 Jan 2014, 16:05:41 UTC

Hi,

you may try and connect using 127.0.0.1 as computername. That helped others that also couldn't connect using opensuse. This may be related.

Regards
ID: 51956 · Report as offensive
mmathis

Send message
Joined: 8 Jan 14
Posts: 5
United States
Message 51960 - Posted: 10 Jan 2014, 1:59:10 UTC - in response to Message 51956.  

Where would I assign a computer name? What is odd is that everything in the boincmanager is blank. It's as though everything is wiped out. I thought that a lot of that information was retained on the local machine.
ID: 51960 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15571
Netherlands
Message 51961 - Posted: 10 Jan 2014, 2:12:48 UTC - in response to Message 51960.  

All of that is blank, because BOINC Manager cannot make contact with the BOINC client. BM is just a graphical user interface that allows you to easily command the client. The client does all the hard work, and will log everything and keep track of what task runs and which is to start next, etc.

So when BM can't make contact with the client, it can't show any of that information and therefore everything is blank.

When you get the message that BM can't make contact with the client, it should give you an option to retry. In the option fields that you get then, the top one should have the computer name, or IP address. The bottom one the password (if that applies). Normally leaving either field blank and pressing OK will fix things, but not for everyone.

This is always due to some restriction (software, aka firewall, anti-virus, anti-malware, a combination of those; but also a virus or trojan or worm) on the user's computer, for if it weren't, and it were a bug, there'd be hundreds of people asking about it around here.
ID: 51961 · Report as offensive
mmathis

Send message
Joined: 8 Jan 14
Posts: 5
United States
Message 51962 - Posted: 10 Jan 2014, 2:14:23 UTC - in response to Message 51960.  
Last modified: 10 Jan 2014, 2:15:10 UTC

Okay, after reading some posts in other threads, I uninstalled 7.2.33 and installed the downlevel version 7.0.64. With NO other changes, everything is working fine.

There is _something_ wrong with 7.2.33.

All's well for now, just won't upgrade.

Thanks Christian and Ageless for your thoughts.
ID: 51962 · Report as offensive
mmathis

Send message
Joined: 8 Jan 14
Posts: 5
United States
Message 51972 - Posted: 11 Jan 2014, 3:06:31 UTC - in response to Message 51962.  

Okay, my apologies. 7.2.33 isn't the problem, my machine is. After I loaded the downlevel version, all worked good. I reboot and _boom_ same problem, can't connect to local host.

I've done virusscans and malware scans... nothing found. more research.

Thanks for keeping me honest.

Mike
ID: 51972 · Report as offensive
mmathis

Send message
Joined: 8 Jan 14
Posts: 5
United States
Message 51981 - Posted: 12 Jan 2014, 13:22:54 UTC - in response to Message 51972.  

All is working now. I did a system restore from 1/1/2014 and whatever was 'bad' is no longer here. Running successfully on 7.2.33 (x64)
ID: 51981 · Report as offensive

Message boards : BOINC Manager : Unable to connect using 7.2.33 (x64)

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.