Well crap, I goofed. The setting "Show processes from all users" wasn't selected on my Task Manager so I wasn't seeing everything running. I rebooted my system and I checked it and now I can see that 'boinc.exe' is, indeed, running. So is 'boincmgr.exe' (I have it open right now) and 'boinctray.exe'. There is also a BOINC service that is Running.

But other than that, it ain't werkin' like it used to :-(

So the two main processes are indeed running and not being blocked. That brings us back to why something is blocking BOINCMGR.EXE from communicating with BOINC.EXE via port 31416, which is usually firewall software. What firewall program are you using?

When you connect to localhost, you should see the same information you normally would see in BOINC Manager about the tasks on your system and the projects you belong to.

McAfee SecurityCenter
Version: 11.0
Build: 11.0.623

McAfee Virus Scan
Version: 15.0
Build: 15.0.294

McAfee Personal Firewall
Version: 12.0
Build: 12.0.345

McAfee SiteAdvisor
Version: 3.4
Build: 3.4.0.143

In the Firewall section, 'Ports and System Services' sub-section, I can make an entry. Aside from the name and description fields are 'Local TCP/IP Ports' and also 'Local UDP Ports'. I appended port 31416 to the existing "Common Operating System Ports" of 5357. I also have an entry for "boinc" itself, with local port TCP/IP port 31416.

Are there any network/connection settings in the BOINC manager I should check while I'm at it?

No, the network/connection settings in BOINC are for external communications to the outside world, which doesn't seem to be a problem here.

BOINC Manager being unable to connect to a client is local traffic so the network/connection settings won't apply.

Unless the Windows Firewall is at play here too, I'm stumped since you already said that you've disabled the McAfee firewall completely, yet something is blocking local TCP/IP port 31416.

Maybe someone more familiar with McAfee can jump in with some suggestions. I personally don't use software firewalls for this very reason (too much hassle and I don't possess enough paranoia).

Stumbled across this at work while waiting for a query to run:
http://boinc.berkeley.edu/dev/forum_thread.php?id=6846
I'll have to read up on it but I'm pretty sure it applies to me as I have an ATI card.

you can run in PAE but you won't get the ATI drivers to run BOINC in windows 7. you can still run that way in XP. Try reinstalling BOINC and not clicking the PAE.

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

Only up to BOINC 6.12.37 will allow service install in WinXP and will do GPU detection, all versions since 6.12.38 will no longer do it; that includes the 6.13 range.

---

Open a command prompt (DOS box) and type "netstat"

Report what displays for port 31416

---

BOINC WIKI

Open a command prompt (DOS box) and type "netstat"

Report what displays for port 31416

Okay, I'll answer this first since it's low-hanging fruit:
*****************

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>netstat

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:61137 Mater:61138 ESTABLISHED
TCP 127.0.0.1:61138 Mater:61137 ESTABLISHED
TCP 127.0.0.1:61139 Mater:61140 ESTABLISHED
TCP 127.0.0.1:61140 Mater:61139 ESTABLISHED
TCP 127.0.0.1:61424 Mater:31416 SYN_SENT
TCP 192.168.1.100:61158 sea09s02-in-f27:http TIME_WAIT
TCP 192.168.1.100:61159 sea09s02-in-f27:http TIME_WAIT
TCP 192.168.1.100:61163 sea09s02-in-f27:http TIME_WAIT
TCP 192.168.1.100:61174 a184-84-183-24:http TIME_WAIT
TCP 192.168.1.100:61175 a184-84-222-82:http ESTABLISHED
TCP 192.168.1.100:61179 a184-84-183-48:http TIME_WAIT
TCP 192.168.1.100:61180 a184-84-183-48:http ESTABLISHED
TCP 192.168.1.100:61181 a184-84-183-48:http TIME_WAIT
TCP 192.168.1.100:61182 a184-84-183-48:http TIME_WAIT
TCP 192.168.1.100:61183 a184-84-183-48:http TIME_WAIT
TCP 192.168.1.100:61184 a184-84-183-48:http TIME_WAIT
TCP 192.168.1.100:61185 208.71.125.66:http TIME_WAIT
TCP 192.168.1.100:61196 a184-84-222-113:http ESTABLISHED
TCP 192.168.1.100:61198 a184-84-183-50:http ESTABLISHED
TCP 192.168.1.100:61199 a184-84-183-50:http ESTABLISHED
TCP 192.168.1.100:61200 a184-84-183-50:http ESTABLISHED
TCP 192.168.1.100:61208 208.71.125.66:https TIME_WAIT
TCP 192.168.1.100:61262 a184-84-183-24:http TIME_WAIT
TCP 192.168.1.100:61264 a184-84-183-50:http TIME_WAIT
TCP 192.168.1.100:61309 sz0124a:http TIME_WAIT
TCP 192.168.1.100:61310 login:https TIME_WAIT
TCP 192.168.1.100:61344 apache2-snort:http TIME_WAIT
TCP 192.168.1.100:61346 thinman:http TIME_WAIT
TCP 192.168.1.100:61348 unknown79:http TIME_WAIT
TCP 192.168.1.100:61350 thermalthree:http TIME_WAIT
TCP 192.168.1.100:61351 thermalthree:http TIME_WAIT
TCP 192.168.1.100:61353 121.127.233.90:http TIME_WAIT
TCP 192.168.1.100:61381 aus3:https TIME_WAIT
TCP 192.168.1.100:61422 192.168.1.1:http ESTABLISHED
TCP 192.168.1.100:61423 ANTONETT-MOBL:http SYN_SENT

C:\Windows\system32>

*****************
Lemme know what this tells you, please.

you can run in PAE but you won't get the ATI drivers to run BOINC in windows 7. you can still run that way in XP. Try reinstalling BOINC and not clicking the PAE.

Thanks for the suggestion! I loaded http://boinc.berkeley.edu/dl/boinc_6.12.43_windows_x86_64.exe and made sure PAE was NOT selected. I let the installer launch BOINC and it automatically connected to localhost and displayed my SETI and Milkyway projects.

WHEW!

Thanks to those who offered assistance, I appreciate it.

Hmmm, I think I may have celebrated too soon. Communication keeps being deferred. Milkyway won't get a schedule update for 24 hours. SETI is just a pending request. Even the screen saver says BOINC is not running. Grr. I also keep getting a pop-up that reads, "Communicating with BOINC client. Please wait..." with two buttons, one to Cancel and the other to Exit BOINC Manager. Clicking the Cancel button just has the pop-up display again and again and again and etc.

I looked at your errored WU's and they seem to have the same problem. To many exits. So basically BOINC is stopping and starting constantly. I'm beginning to wonder if you have a bad case of malware on your PC

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

It tells me that something on this computer is connected to Mater on port 31416

---

BOINC WIKI

JMVII, here ya go!:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>netstat

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:31416 Mater:49168 ESTABLISHED
TCP 127.0.0.1:49168 Mater:31416 ESTABLISHED
TCP 127.0.0.1:49243 Mater:49244 ESTABLISHED
TCP 127.0.0.1:49244 Mater:49243 ESTABLISHED
TCP 127.0.0.1:49245 Mater:49246 ESTABLISHED
TCP 127.0.0.1:49246 Mater:49245 ESTABLISHED
TCP 192.168.1.100:49237 161.69.92.7:https ESTABLISHED
TCP 192.168.1.100:49241 milkyway:http LAST_ACK
TCP 192.168.1.100:49242 milkyway:http LAST_ACK
TCP 192.168.1.100:49247 ec2-184-72-47-190:https ESTABLISHED
TCP 192.168.1.100:49248 ec2-50-18-122-194:http ESTABLISHED
TCP 192.168.1.100:49255 8.18.25.6:https ESTABLISHED
TCP 192.168.1.100:49256 sea09s01-in-f14:http ESTABLISHED
TCP 192.168.1.100:49257 ec2-184-72-47-190:https ESTABLISHED
TCP 192.168.1.100:49261 apache2-snort:http TIME_WAIT
TCP 192.168.1.100:49265 milkyway:http CLOSE_WAIT
TCP 192.168.1.100:49266 sea09s02-in-f13:http ESTABLISHED
TCP 192.168.1.100:49267 pw-in-f101:http ESTABLISHED

C:\Windows\system32>

Look better? "Mater", as in "Tow-Mater" is our home computer :-D

Here's what I did (uhg):
I did a search on "uninstall catalyst control center" and found a thread that recommended using the Uninstall Tool from http://www.crystalidea.com/. This allowed me to fully remove the damn ATI Catalyst <ahem> tool, including registry entries. Yes, yes, I created a system restore point and backed up my registry so unbunch yer knickers. Rebooted the computer. I then uninstalled BOINC and I also deleted ALL BOINC FOLDERS! This was necessary because my first attempt to uninstall and then reinstall still left me with the same problem. Okay, BOINC totally off my system. Reboot. Install the latest version recommended here http://boinc.berkeley.edu/download_all.php and made sure the PAE was NOT checked. Run BOINC automatically (checked the box) from the install window and clicked the Finish button. The manager came up and was blank. I added SETI and used my user account to do so [Note to developers, freakin' excellent idea, thanks for implementing that feature!!!]. I turned on everything (network, GPU, run always), Updated, and was up and running...YAHOO! I then added Milkyway. No issues. Every thing is running from where I left off. I tested the screen saver and that's fully functional as well. Sha-weet!

I hope this will help anyone else in the future. Thanks to all for your assistance. Again, LOL.

---

Yes, it does look a bit better.

---

BOINC WIKI