> DHCP will assign IP to your machines and IP assigned have a lease time, when
> expired DHCP will assign a new I, I think this cause BOINCView cannot reach
> your machines. Try using manual assign IP to all the machines and disable the
> DHCP server.

Which is why I did a complete network restart from cold (completely powered off) units including the DHCP server. After that, usually the reservations are always for the same IP, but this will allow you to use the names and not the static IP addresses.

Golly I can't wait for the cross-platform GUI comes out so we can skip all this folderal ...

---

I have noticed the following that may be related:

When you ungrade either SETI or BOINC and select the "autostartup" option, the installation probram DOES NOT append the "-allow_remote_gui_rpc" flag to the startup call to BOINC in the startup fule.

As a result, computers previously configured to use this flag when running BOINCView need to be re-configured after SETI/BOINC updates.

It is a pain -- but since the old version of SETI is still running, we must still be in beta test.

Good Luck!

---

> > ... For now, I will run it using the
> > command line switch, but if anyone can think of anything else, I would
> sure
> > like to hear it.
>
> Ok, last desparate test ...
>
> I THINK I had this same problem ... Memory is the second thing to go
> you know ... I forget what is first ...
>
> I had to take all the machines down ... reset the DHCP server (in my case the
> router on the cable modem). Then I borught each machine up one at a time.
> Then I had to add the machines one at a time to BOINC VIew ...
>
> My last shot ...
>
> Other than that ... I am at a loss ...
>
> I know BOINC VIew has a few oddities (of course that also may be because I
> have not updated to the very latest) for example, if a machine restarts it
> does not always catch it when it comes back online, I have to stop and restart
> BOINC View ...
>

DHCP will assign IP to your machines and IP assigned have a lease time, when expired DHCP will assign a new I, I think this cause BOINCView cannot reach your machines. Try using manual assign IP to all the machines and disable the DHCP server.

---

<a href='http://www.studiotraffic.com/index.php?refid=76536'><img src='http://www.studiomatrixsystem.com/banner/ban_1.gif' border="0"></a>

> ... For now, I will run it using the
> command line switch, but if anyone can think of anything else, I would sure
> like to hear it.

Ok, last desparate test ...

I THINK I had this same problem ... Memory is the second thing to go you know ... I forget what is first ...

I had to take all the machines down ... reset the DHCP server (in my case the router on the cable modem). Then I borught each machine up one at a time. Then I had to add the machines one at a time to BOINC VIew ...

My last shot ...

Other than that ... I am at a loss ...

I know BOINC VIew has a few oddities (of course that also may be because I have not updated to the very latest) for example, if a machine restarts it does not always catch it when it comes back online, I have to stop and restart BOINC View ...

---

Well, after going over it with a fine tooth comb, we can conclude beyond a shadow of doubt that the "remote_hosts.cfg" file indeed exists with a single entry, 192.168.0.1 which is definitely the ip address of the boincview host. We can also conclude that I am telling boincview the right ip address to look for, and that it is indeed reaching that machine as evidenced by the "GUI RPC request from non-allowed address 192.168.0.1" that is showing up in the messages tab of said remote machine. I also decided to try it via direct file access and it works however, that is not the desirable way to do it. So, I then started up Boinc using the "-allow_remote_gui_rpc" switch, and that too works. Now, the question is, why is the Boinc client either not seeing the "remote_hosts.cfg" file, or is ignoring it? For now, I will run it using the command line switch, but if anyone can think of anything else, I would sure like to hear it.

---

> O.K., neither the host name or ip address(verified) works. I can ping the
> machine, it shows up on my network, and I can access files on it. So, I
> switched it from Win98se to Win XP. Still no go. Now with XP, again, I can
> ping, access files, etc... WTF?

Did you create the file called "remote_hosts.cfg" on the machine that you cannot "see"?

In my case, I have BOINC View on the "EQ2" machine, so the file on EQ1 has the file with the single line "EQ2".

Last thing to check is to make sure that the "EQ2" is a full line with a <RETURN> at the end ...

---

Not sure what that prob is - I have 4 Win98 PC's that work fine with BOINCview...only PC that I can't use BOINCview is a Win95 box (yes, I said Win95 LOL!)

---

<a><img src="http://boinc.mundayweb.com/stats.php?userID=525">

<a><img src="http://www.wombatradio.com/stats/rtb/sig.php">

O.K., neither the host name or ip address(verified) works. I can ping the machine, it shows up on my network, and I can access files on it. So, I switched it from Win98se to Win XP. Still no go. Now with XP, again, I can ping, access files, etc... WTF?

---

> Speaking of BoincView, I have a problem maybe you guys can help me with. I
> have 4 local boxes and Boincview works fine with 3 of them, but I can't get it
> to work with the fourth. The one that won't work is the only Win98SE machine,
> the rest are Win XP. I have setup the remote_hosts.cfg just like all the other
> ones, but I keep getting "GUI RPC request from non-allowed address". Is there
> something about Win98 or what?
>
When I had a Win98 machine on-line, it is currently crunching Classic again, I had to use the Ip address, the name would not work.

---

try to use the native IP adress instead of hostname

make a ping to the win98er, if no response, check the propper tcp/ip settings
of the win98 machine.

Verify the IP adress used...

Speaking of BoincView, I have a problem maybe you guys can help me with. I have 4 local boxes and Boincview works fine with 3 of them, but I can't get it to work with the fourth. The one that won't work is the only Win98SE machine, the rest are Win XP. I have setup the remote_hosts.cfg just like all the other ones, but I keep getting "GUI RPC request from non-allowed address". Is there something about Win98 or what?

---

Thanks lol!

---

Yes, BOINCview (or perhaps similar apps) causes that. If you are using BOINCview, you need to setup a remote-hosts.cfg file to allow your local IP's remote GUI access. This procedure is described on BOINCviews website.

---

<a><img src="http://boinc.mundayweb.com/stats.php?userID=525">

<a><img src="http://www.wombatradio.com/stats/rtb/sig.php">

Are you running BoincView?

---

It started with 4.09 but it is also on 4.12 what up, how do i stop it?

--- - 2004-10-13 17:40:16 - GUI RPC request from non-allowed address 192.168.0.3
--- - 2004-10-13 17:40:18 - GUI RPC request from non-allowed address 192.168.0.3
--- - 2004-10-13 17:40:19 - GUI RPC request from non-allowed address 192.168.0.3
--- - 2004-10-13 17:40:21 - GUI RPC request from non-allowed address 192.168.0.3
--- - 2004-10-13 17:40:22 - GUI RPC request from non-allowed address 192.168.0.3
--- - 2004-10-13 17:40:24 - GUI RPC request from non-allowed address 192.168.0.3
--- - 2004-10-13 17:40:25 - GUI RPC request from non-allowed address 192.168.0.3
--- - 2004-10-13 17:40:27 - GUI RPC request from non-allowed address 192.168.0.3
--- - 2004-10-13 17:40:28 - GUI RPC request from non-allowed address 192.168.0.3
--- - 2004-10-13 17:40:30 - GUI RPC request from non-allowed address 192.168.0.3
--- - 2004-10-13 17:40:31 - GUI RPC request from non-allowed address 192.168.0.3

---