| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Alan Cresswell
Cruncher Joined: Apr 29, 2007 Post Count: 3 Status: Offline Project Badges:
|
Hi,
Sorry if this has been answered somewhere. I've had look through the threads here but nothing immediately leapt out as being relevant to my problem. I've been running the UD software on some computers here at work. At the moment they're idle because they have insufficient RAM for the projects currently available so I thought it would be a reasonable time to change to BOINC - especially as the new projects seem to be coming in as BOINC only. And, I've also got access to a higher spec machine not currently running the WCG agent, so thought I'd put BOINC on there too while I was at it. The software seems to install OK, asks for the project URL (as per the instructions I put in "http://www.worldcommunitygrid.org") but when it tries to communicate with the project it fails, saying "Project temporarily unavailable. Please try again later", before asking my user name. So far I've been trying for days, so it seems to be something other than the WCG server being down. I've tried messing around with the firewall here, both explicitely permitting the BOINC agent and turning it off completely (just as a test) without it communicating. I've also uninstalled and reinstalled the software a couple of times. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
All ingredients you provided info on seem fine, but for the part that it fails even before the actual sign in screen. The special hook with WCG is the security certificate for which a Start Here faq exists and the fact that port 443 and 80 need to be open on outgoing traffic to IP 129.33.89.133 + 134 (WCG servers). If you are writing from the problem PC, it wont be port 80.
----------------------------------------Firewalls are special. Are you talking of one on the computer or at the central gateway of your workplace (think latter)? Is there a proxy-server in-between? Added: Good old Ping in a command window to 129.33.89.134 will tell you if there is any obstruction at all for a signal to get to the servers.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Sep 3, 2007 10:49:56 AM] |
||
|
|
Alan Cresswell
Cruncher Joined: Apr 29, 2007 Post Count: 3 Status: Offline Project Badges:
|
Sorry, I must be a bit dense, but I'm afraid I didn't find your reply all that helpful
The special hook with WCG is the security certificate for which a Start Here faq exists Do you happen to know where this FAQ is? Because I couldn't find anything within the help section, either here or on the BOINC site. port 443 and 80 need to be open on outgoing traffic to IP 129.33.89.133 + 134 (WCG servers). If you are writing from the problem PC, it wont be port 80. Though the help section here does say you need port 443 open to outgoing traffic, I'm afraid I've no idea how to actually do that ... and the help files for Windows aren't exactly clear on the matter either. Very helpfully says something like "if you don't know what settings are needed consult the software supplier", and I'm not finding the information here. I'm assuming I need to enable these ports within the firewall settings ...Firewalls are special. Are you talking of one on the computer or at the central gateway of your workplace (think latter)? Is there a proxy-server in-between? There is a proxy-server. But, the settings for that aren't used for most applications (eg: browsers, email). The only thing that I've got here that seems to need them is AdAware (so it can connect to update), the UD agent doesn't. Besides, I can't see where in the BOINC agent to put proxy server settings. Good old Ping in a command window to 129.33.89.134 will tell you if there is any obstruction at all for a signal to get to the servers. That times out, so there's definitely an obstruction somewhere ... |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Sorry, I must be a bit dense, but I'm afraid I didn't find your reply all that helpful The special hook with WCG is the security certificate for which a Start Here faq exists Do you happen to know where this FAQ is? Because I couldn't find anything within the help section, either here or on the BOINC site. port 443 and 80 need to be open on outgoing traffic to IP 129.33.89.133 + 134 (WCG servers). If you are writing from the problem PC, it wont be port 80. Though the help section here does say you need port 443 open to outgoing traffic, I'm afraid I've no idea how to actually do that ... and the help files for Windows aren't exactly clear on the matter either. Very helpfully says something like "if you don't know what settings are needed consult the software supplier", and I'm not finding the information here. I'm assuming I need to enable these ports within the firewall settings ...Firewalls are special. Are you talking of one on the computer or at the central gateway of your workplace (think latter)? Is there a proxy-server in-between? There is a proxy-server. But, the settings for that aren't used for most applications (eg: browsers, email). The only thing that I've got here that seems to need them is AdAware (so it can connect to update), the UD agent doesn't. Besides, I can't see where in the BOINC agent to put proxy server settings. Good old Ping in a command window to 129.33.89.134 will tell you if there is any obstruction at all for a signal to get to the servers. That times out, so there's definitely an obstruction somewhere ...No worries, just Q&A. The fact that the ping fails means that you positively are fenced in. Pinging 129.33.89.133 probable will let you out, but 134 is the more important one. We have the Help files you've already consulted and the FAQs which are in the Start Here forum. Here's the link to the article: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=15682. One way or the other that file has gone missing at times. Just making sure it's there as it is integral to a secure connection with the WCG servers. Given it was your PC's firewall and switching it off making no change, there is little to be configured in that department. The inbuilt WinXP firewall is in fact by default set to stop incoming traffic, outward it's wide open. The University Firewall is a possible barrier. You'll likely need the proxy info from the University which can be entered by going to the 'advanced' menu taking 'options'. Copy the information from your Ad-Aware to either the HTTP or SOCKS as is appropriate to the Uni network setup. You'd be able to verify with the University IT department. The way UD agent connects and BOINC to WCG is different. We've found members able to connect with BOINC, but not with UD and vice versa.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Sep 3, 2007 1:22:13 PM] |
||
|
|
Alan Cresswell
Cruncher Joined: Apr 29, 2007 Post Count: 3 Status: Offline Project Badges:
|
Aha! Got the proxy server info in there and it's now doing the AIDS project ... now to go and repeat the process on some more computers to get them back to doing something useful while I'm not using them ...
Many thanks. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Excellent and if you feel boisterous, get yourself 3rd party BOINCview to manage it all from one desktop. It's the only tool i know that shows views listing all the devices you are hooked up to and displays things like colour-coded CPU efficiency for easy identification which clients good (green) are slow (yellow) or not work (red).
----------------------------------------ttyl
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|