| 42 | | This means BOINC can't do any communication at all. The likely problems are: |
| 43 | | * Connectivity: you don't have a network connection. Check your network or modem connection (if your web browser can get to outside sites, this is not the problem). See this [http://support.microsoft.com/kb/326155/ information on Windows networking troubleshooting] from Microsoft website. |
| 44 | | * Personal firewall software (!ZoneAlarm, Norton Personal Firewall, !McAfee, etc.) is blocking BOINC. |
| 45 | | * The first time you run BOINC, your personal firewall will bring up a dialog asking if boincmgr.exe and boinc.exe should be allowed to communicate (say yes). |
| 46 | | * If this dialog doesn't appear, bring up your personal firewall program and add an 'exception' entry allowing BOINC to communicate. If it already has an entry for BOINC, delete it. Detail vary between firewall packages. |
| 47 | | * You may have accidentally installed more than one firewall. Uninstall or disable all but the primary one. |
| 48 | | * Proxy server: there are two kinds of proxies, HTTP and SOCKS. You may be using one or both. Most home computers do not use proxies. To find out if you're using a proxy, look at the Internet settings of your web browser. (Firefox: Tools/Options/General/Connection Settings; Internet Explorer: Tools/Internet Options/Connections/Settings). Copy the settings there (server, port, etc.) to the BOINC dialog. |
| 49 | | * (Windows) SETI@home: if it appears to attach OK, but the Messages tab has repeated '''shared memory error''' messages from the server: uninstall BOINC and delete the install directory (typically C:\Program Files\BOINC). Reinstall BOINC, but in a different directory (such as C:\Program Files\BOINC2). |
| 50 | | * Some DSL customers in the UK report needing to set MTU=1492 in their modem/router and rebooting it. |
| | 38 | This means BOINC can't do any communication at all. Check the common [TroubleshootClient/Network network problems]. |
