• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

At least 10 new computers for TA Seti@home if you can answer this question

IJump

IJump

Diamond Member
I currently run RC5, and crack quite a few blocks. When that is over, I look to move to Seti@home. I have one problem that I have to beat if I am going to run it:

I run MS Proxy Server with authentication to log all internet traffic here at work. The seti@home client won't connect to the Seti servers through my proxy. I have quite a few machines that could be put on if I could get around this somehow. Any one have any ideas? I may put 5 or 10 machines on Seti@home now if I can get this fixed.

Any ideas?
 
(10 systems... Gotta try and help... 10 systems... gotta try and help...)

The authentication is what's throwing the monkey wrench into things... I run MSProxy here but without authentication.

Here's an idea. Download SetiQueue and install it on your MSProxy server, it will be the only system which has to connect with Berkeley. All of your clients will upload and download wu's to and from your Seti proxy, never having to communicate outside of your internal LAN. To your Seti clients, SetiQ looks like the servers at Berkeley.

The SetiQ server listens for Seti clients on port 5517 by default, but you can configure that to be any port you desire. I'd suggest running the CLI version of Seti on your clients because of the performance benefits over the GUI, but you can configure the GUI clients to use SetiQ as well. If your proxy server is 192.168.0.1, for example, and you are going to use port 5517 to communicate with the proxy, you'd run the CLI as follows:

setiathome-3.03.i386-winnt-cmdline.exe -proxy 192.168.0.1:5517

If you want to run GUI clients, you can configure them to use the IP of your proxy server and port 5517. (Just make sure you configure the GUI to go to a blank screen!)

An added benefit of SetiQ is that even if Berkeley goes down, you'll still have a backlog of wu's on the SetiQ server to keep your clients well fed for any number of days. It does a good job of determining how many wu's to keep queued. You just tell it how many days you want stored and it figures out how many wu's to keep in it's queue based on the clients production. And the stats you can get from SetiQ about your clients are fantastic.

Does this sound like it might work???????
 
We have the same situation here. I was able to come up with two ways to do this. Both ways required installing the MS Proxy Client. Without the proxy client, nothing we did (5 of us fighting with it) would get the Seti client to connect through the firewall.

First way is to install the client software on all computers and just let them connect. Second way (better in my opinion) is to install the MS client software on one computer and have that one run SetiQueue for the other systems...


Or, if installing software on the firewall/proxy itself is an option, Ohio Dude's idea would work as well. 🙂
 
Or if worse comes to worse, you could install SETIQ on a PC, and then fetch/flush manually by taking the WU's to your house and dumping them through a SETIQ running there.
 
I really don't want to try to take disks back and forth from work to the house. I may have a couple hundred PCs running seti when RC5 is finished.
 
IJump --

I believe you can configure SetiQ to communicate through a proxy/firewall that requires authentication. So, if installing SeqtiQ on the proxy/firewall system is not an option, you could set up one of your clients behind the firewall as the Seti queue server and have all of the other clients point to it. Then just configure that one client to authenticate to MSProxy.
 
That sounds like a better plan. I have my RC5 pproxy running on one of my personal computers here at work. Makes it easier to watch. I will try putting seti-q on here and see if I can get it working.
 
Manually transfering WU's really isn't as bad as it seems, especially if you have a CD-RW drive at home. WU's to be crunched are about 360 KB. Finished results are about 3 KB. Thus you could fit 1800 WU's on a CD-RW to bring to work from home, and 460 finished WU's on each floppy to take back home. It isn't as bad as it sounds like if you can't get the SETIQ proxy to access the outside world. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top