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

SETI: Queue/Identification question.

D

dxkj

Lifer
There are about 90 computers that I want to connect to this queue, and I want to view them individually with a Machine name so I can keep track of which ones are producing, and which ones have issues.

The IP address on the inside is setup for inside use only, by the time it gets to the oustide (and connects to the queue), it is a number randomly assigned per reboot. Since these computers are reset each day, they will have a different IP address each day.


I know I could set a port for each machine, but that is problematic because we use a zen/ghost type image to install OS/programs onto these computers all at once.

So I guess the question is, does anyone have any other ideas/options available that I may not know about 🙂.

Thanks!


PS The queue is on the outside.... if the queue was on the inside it would work, but there isnt a dedicated machine that I would trust enough on the inside (of the firewall).


 
Could you setup a q inside the network and send the machines to that q? Then have that q send to the outside q .
 
Originally posted by: Freewolf
Could you setup a q inside the network and send the machines to that q? Then have that q send to the outside q .
Click to expand...

if the queue was on the inside it would work, but there isnt a dedicated machine that I would trust enough on the inside (of the firewall).
Click to expand...


Other people besides me have access to these machines, and might

1) Turn off the computer
2) Close the setiqueue because they dont know better/or they do know better ;evil;
3) Format the computer because of a small problem they dont know how to fix
4) etc
 
Use seti hide on each machine so you can set a cache on each machine so if the q is down for whatever reason they will still be crunching until the q is back up.
 
That is probably the most viable option, now to try to gain some experience with SETI hide... havnt gotten it to work quite right yet.



Other option is, to do this for each 90 computers.

1) Kill process
2) Clear WU in progress on each machine
3) Connect to Queue and download WU
4) Load setiqueue page, Assign port
5) Edit registry for this port

Ok, trying to see if I can get a batch file to do most of my dirty work
 
That is probably the most viable option, now to try to gain some experience with SETI hide... havnt gotten it to work quite right yet.



Other option is, to do this for each 90 computers.

1) Kill process
2) Clear WU in progress on each machine
3) Connect to Queue and download WU
4) Load setiqueue page, Assign port
5) Edit registry for this port

Ok, trying to see if I can get a batch file to do most of my dirty work
 
Originally posted by: Freewolf
Could you setup a q inside the network and send the machines to that q? Then have that q send to the outside q .
Click to expand...

Won't work ,at least not for showing individual machine names ,the 1st Q will just bundle all the names under its own name🙁

dxkj
If you can't assign a port to each PC the I don't see how your going to get individual machine stats
 
Been out celebrating a birthday (not mine) and just got in. hiccup ssh 'cuse me 😛 😀

Bryan, check out the MACHINE NAME that is registered on the Q inside the firewall. Does each machine have a unique name?

If they do, I may have a solution. I'm going to bed, check back in the morning. burp

😱
 
Originally posted by: Smokeball
Been out celebrating a birthday (not mine) and just got in. hiccup ssh 'cuse me 😛 😀

Bryan, check out the MACHINE NAME that is registered on the Q inside the firewall. Does each machine have a unique name?

If they do, I may have a solution. I'm going to bed, check back in the morning. burp

😱
Click to expand...

yes, each have a Unique Name 🙂
 
OK on the "unique name". This will assist you in assigning a PORT NUMBER to each computer.

Now you need to edit the "Service Install" on each machine accordingly.

You will need a ROSTER to keep all of the machines and port numbers straight ... that's what I have to do with The TeAm's SetiQueue. 😉
 
That's why I said :-

dxkj
If you can't assign a port to each PC the I don't see how your going to get individual machine stats

🙁
 
Originally posted by: Assimilator1
That's why I said :-

dxkj
If you can't assign a port to each PC the I don't see how your going to get individual machine stats

🙁
Click to expand...

Is there anyway i can get them to identify by their machine name rather than their ip address when they reach the queue?


They ip addresses are random, but their machine names are constant. Thats how they are identified when used on an internal queue.
 
If you stopped using the internal Q & just had the machines flush directly to the external Q then yes you could do it

Haven't we just come full circle??😕
 
Originally posted by: Assimilator1
If you stopped using the internal Q & just had the machines flush directly to the external Q then yes you could do it

Haven't we just come full circle??😕
Click to expand...

The machine name they report to the external queue is based on their IP number, its not the "true" machine name.


I decided to just try to go with an internal queue.


And using setihide wont work unless we could get it to start up as a service before anyone logs in.
 
Originally posted by: Assimilator1
Yeah but if you have an external Q , when you assign a port to a machine it uses the machines name & not the IP
Click to expand...

We can't do ports since only port 5517 is open, rest are blocked.
 
To id every machine on an internal setiqueue, it should be enough to use one queue and throw a seti-service-install on every machine, and they should be detected by their name... If needed, setihide or setidriver should be usable as local caching on every machine.

If you on the other hand wants to detect their name on an external SetiQueue, this should also be easy, just install setiqueue to EVERY machine, and on the external queue you will get clients connecting as machinename.username.client-version.client-type
Example from Smokeball's queue: MINIME.The TeAm.3.3.i386-winnt-cmdline
Looking closely Crazee has 2 external queues connected, but Smokeball has manually given the 1st another name...


 
Originally posted by: Rattledagger
To id every machine on an internal setiqueue, it should be enough to use one queue and throw a seti-service-install on every machine, and they should be detected by their name... If needed, setihide or setidriver should be usable as local caching.

If you on the other hand wants to detect their name on an external SetiQueue, this is also be easy, just install setiqueue to EVERY machine, and on the external queue you will get clients connecting as machinename.username.client-version.client-type
Example from Smokeball's queue: MINIME.The TeAm.3.3.i386-winnt-cmdline
Click to expand...

Great idea! Now why didn't I think of that🙂
 
Originally posted by: Assimilator1
If you stopped using the internal Q & just had the machines flush directly to the external Q then yes you could do it

Haven't we just come full circle??😕
Click to expand...
This doesn't work, since you this way mostly will either connect as something.ADSL.something or something.DIALUP.something, and this will change EVERY time you connects... atleast for dialup. 🙂
Just take a look on any awailable public setiqueue. 😉 SetiQueues on the other hand shows up as posted above, and always shows up italic
 
BTW, everyone has said use SETIHIDE for the clients, but the SETIQ can be installed as a service, which means it will run hidden, IIRC, without a system tray icon to temp people to close it. So find the least used, always on PC and setup SETIQ as a service on that PC, and have it connect to the outside Q. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top