Message boards :
Number crunching :
Boinc 4.56, Win XPSP2 and Zone Alarm?
Message board moderation
Author | Message |
---|---|
gregh Send message Joined: 10 Jun 99 Posts: 220 Credit: 4,292,549 RAC: 0 |
Just to get this straight from the start, there is no "this is what is causing it" here but asking for any input from people with the same config. I use XPSP2 and Boinc4.56 on 2 computers and on one with a P3 1.13Ghz CPU no probs. I use it on this one with a P4 3.4 and the same XP and Boinc and problems. I use only Windows firewall on the slower computer as it is connected via lan to this one connected directly to the net. This computer uses Zone Alarm Pro latest version. Zone Alarm Pro (referred to as ZAP from now on in this letter ;-} ) blocks things incoming and outgoing depending on your settings as we all know. It blocks certain things that people are unaware about, too, from time to time and I have noted and fixed that problem for myself. However, I was wondering if maybe it is causing my problem mentioned below and am asking for anyone with the same sort of setup as me if they suffer the same. When I start my machine, I dont let Boinc start in windows startup any longer as more often than not, it just wouldnt work. It didnt display me as connected to any project or any of the work I had ready to process. It would also take about 3 clicks on it to max or min Boinc. However, it WOULD show up in Task Manager as 2 Seti@Home WUs running and taking up CPU time. Unsure if this means work IS being done, I never let it do that, end the tasks and restart the prog and it would then come up normally, all well. Unfortunately it has gone back to the bad old ways and is doing as described above when I boot into Windows then manually start Boinc. I exit Boinc, shut down the manager, Boinc client and each Seti WU in Task Manager and start again. Sometimes it can take 3 times for this to come up normally. Today I thought about ZAP so when the Boinc problem I described came up again, I shut down ZAP first and then stopped all Boinc and Seti stuff from running in Task Manager and started Boinc normally. All came up fine and quicker than normal. As ZAP does monitor even 127.0.0.1, I wondered if it is possible that 4.56 Boinc and latest ZAP are intermittently interfering with each other or actually that ZAP is doing the interfering. Anyone with the same setup as me got any thoughts on this? I realise it isnt happening on CPUs that dont do hyper but it is to my 3.4Ghz P4 with ZAP so I dont expect anyone with a slower CPU that doesnt do hyper to have a problem therefore no use saying "it doesnt happen to me" unless you have a similar system to mine. Sorry if that sounds rude. There was no way I could type it more nicely so please take for granted I didnt mean for it to upset anyone. Anyway, help appreciated from people with similar systems. Even if you dont use ZAP, maybe you could download the 30 day free trial and see if you can make it happen? Thanks. Greg. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
I use Zone Alarm (Not Pro), and I have similar problems every time that I install a new version of BOINC. To get things to work, BOINC must be allowed to access the internet (port 80) and act as a server for the trusted area for port 1043. In 4.50 and later, the GUI and the CLI are both running, and the GUI communicates with the CLI over port 1043, and can do so remotely. If you are going to set up remote administration, you need to set up the BOINC CLI to allow the communication. This can be done with either a switch which I believe is -allow_remote_config. Or preferably, it can be done with a config file, remote_hosts.cfg, which contains the name or IP of each possible controlling PC. I would not recommend allowing this across a firewall. BOINC WIKI |
gregh Send message Joined: 10 Jun 99 Posts: 220 Credit: 4,292,549 RAC: 0 |
> I use Zone Alarm (Not Pro), and I have similar problems every time that I > install a new version of BOINC. To get things to work, BOINC must be allowed > to access the internet (port 80) and act as a server for the trusted area for > port 1043. In 4.50 and later, the GUI and the CLI are both running, and the > GUI communicates with the CLI over port 1043, and can do so remotely. If you > are going to set up remote administration, you need to set up the BOINC CLI to > allow the communication. This can be done with either a switch which I > believe is -allow_remote_config. Or preferably, it can be done with a config > file, remote_hosts.cfg, which contains the name or IP of each possible > controlling PC. I would not recommend allowing this across a firewall. > Thanks for that but the switches dont apply to V4.56. |
SURVEYOR Send message Joined: 19 Oct 02 Posts: 375 Credit: 608,422 RAC: 0 |
I use Norton Personal Firewall. Every time I install a new version NPF ask if I want to allow it to access the net, I say yes and let it connect to all IP address, as I have 6 projects running. Maybe Zone Alarm needs to be set to all IP Addresses. Fred BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha |
Heffed Send message Joined: 19 Mar 02 Posts: 1856 Credit: 40,736 RAC: 0 |
> I use Zone Alarm (Not Pro), and I have similar problems every time that I > install a new version of BOINC. To get things to work, BOINC must be allowed > to access the internet (port 80) and act as a server for the trusted area for > port 1043. ZA Pro will allow you to set an application to "changes frequently" to avoid this issue, but I prefer to have it ask me every time. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.