Questions and Answers :
Windows :
GUI RPC request from non-allowed address?
Message board moderation
Author | Message |
---|---|
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
I am running BOINC v4.09 on a Pentium 166MHz Classic with Windows 95A doing SETI 4.03 WUs. Everything was working fine, it downloaded a workunit and completed it, sent it back and, because none of my systems are receiving workunits at this moment (the scheduler probably needs to catch up to WU requests), it can't download anymore. However, on my Messages tab, I have displayed every second: "GUI RPC request from non-allowed address 84.250.108.0". This only started after it attempted to reconnect for a WU. I have scanned for virii with no results. Does anyone know what this is? EDIT - the IP address has now changed to 160.238.71.0 after I attempted to force SETI/BOINC to update itself after one of my other machines finally received a WU. |
Link Send message Joined: 20 May 99 Posts: 22 Credit: 1,192,239 RAC: 0 |
Are you running BOINCView? If so, create a text file named remote_hosts.cfg in your BOINC directory (normally c:\Program Files\BOINC). In this file place the name or IP address of the machine running BOINCView. Besides getting rid of your message, you will have some nice control over your remote machines. |
Morgan the Gold Send message Joined: 11 Feb 01 Posts: 11 Credit: 4,345,964 RAC: 0 |
DoRpc also uses rpc gui feature to manipulate and monitor remotely |
Trane Francks Send message Joined: 18 Jun 99 Posts: 221 Credit: 122,319 RAC: 0 |
You'll *definitely* want to have your firewall block that port. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
I want to thank everyone for their efforts, but I have found the solution. It was a combined anomoly between Windows 95 being half crashed yet still running somehow (BSODs were popping up on some apps and I kept trying to quit the app without taking Windows down - yeah, I should reboot anytime I get a BSOD, but I try to keep them running as long as possible) and the other problem was because of an overheated Pentium chip. The passive heat sink seemed to be causing the Win95 errors and the crashes. Upon changing the CPU to a Pentium 166MMX with a built-in active fan/heat sink assembly, the errors have ceased. Thanks again everyone. |
©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.