GUI RPC request from non-allowed address?

Questions and Answers : Windows : GUI RPC request from non-allowed address?
Message board moderation

To post messages, you must log in.

AuthorMessage
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 29722 - Posted: 24 Sep 2004, 18:16:08 UTC
Last modified: 24 Sep 2004, 18:41:05 UTC

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.
ID: 29722 · Report as offensive
Profile Link
Volunteer tester

Send message
Joined: 20 May 99
Posts: 22
Credit: 1,192,239
RAC: 0
United States
Message 29796 - Posted: 24 Sep 2004, 22:32:04 UTC
Last modified: 25 Sep 2004, 19:15:40 UTC

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.

ID: 29796 · Report as offensive
Profile Morgan the Gold
Volunteer tester
Avatar

Send message
Joined: 11 Feb 01
Posts: 11
Credit: 4,345,964
RAC: 0
Canada
Message 29913 - Posted: 25 Sep 2004, 7:39:13 UTC

DoRpc also uses rpc gui feature to manipulate and monitor remotely
ID: 29913 · Report as offensive
Profile Trane Francks

Send message
Joined: 18 Jun 99
Posts: 221
Credit: 122,319
RAC: 0
Japan
Message 30134 - Posted: 25 Sep 2004, 23:57:23 UTC

You'll *definitely* want to have your firewall block that port.
ID: 30134 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 30356 - Posted: 26 Sep 2004, 19:57:31 UTC

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.
ID: 30356 · Report as offensive

Questions and Answers : Windows : GUI RPC request from non-allowed address?


 
©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.