New computer and problems with @home

My old computer died, well I think. I just went ahead and broke down and get a new one and when I installed @home I used my old name 'dc1984us' and put in the major geeks team code. It's been installed for 3 days now and it is on step 26 and it keeps saying 'Cannot connect to primary server' 'Cannot connect to secondary server' and ever so often the @home control panel will be on the screen. I have my windows firewall turned off. I have my mcafee firewall turned on, and i have allowed f@h full access. Any ideas or thoughts to cure this so I can start folding again?

 

First and foremost I myself would not ever shut down my firewall unless I knew I was on a secure network!
I use the freebie version of ZoneAlarm and have no troubles.
That 2cent worth over with why the hurry if only at step 26?
I use the console version non graphical and allow as a service using Windows XP when first using and thereafter never see it again.
Using win98se I use version 5 <which is not supposed to be used on said operating system> just Do Not allow the download of over 5MB WU while in/on this operation system and no prob-lems.
also as a note that has worked for me is when first configuring FAH I Do NOT allow:
Use Internet Exployer = no
Use proxy = no
I sure hopes this helps as we really need all the spare idle cpu cycles we can get "our"
major hands on...

"MajorGeeks.com - Geek it 'till it MHz."

*EDIT*
FYI
almost forgot when using Linux as your operating system you can save more cycles by Not loading up into the window manager.

 

My firewall is not shutdown. I am using McAfee's firewall instead of Windows. I'll try to download the non-graphical version and see what happens.