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

how do i set up SETIQ on a SINGLE machine with DIALUP?

TuffGuy

Diamond Member
i'm using WinME. what proxy do i set the seti client to look for? when i'm disconnected the computer doesn't have an IP address, so what do i use? thanks for the help.
 
A single machine with SetiQ and the client on the same box, right? Did you try the loopback address (127.0.0.1) so it looks for WU's from itself? I haven't done this so I'm kinda guessing. Okay, it's a total guess but it's reasonable, right? 😉

Rob

Edit: Try pinging loopback or 127.0.0.1 first before trying. As long as you've got TCP/IP setup it should work, I think. 😉
 
that's what i tried, but 127.0.0.1:5517 only works when i'm online. i get an error when i'm disconnected, so the seti client doesn't get a new workunit from setiq.
 
Just checked my SetiQ...

Open SetiQ and look under Settings | Queue Server, what do you have as the IP/Subnet/Port?

Rob
 
IP - 0.0.0.0
Subnet - 0.0.0.0
Port - 5517

i checked winipcfg and i get addresses for these when i'm online, but when i'm offline they revert to 0.0.0.0
 
if i ping with either 127.0.0.1 or tuffguy, it can find my computer. as soon as i add the :5517 it tries to connect. is my syntax wrong?
 
I'm not sure if/how this will affect your SetiQ connecting to Berkeley but I think you should be able to input 127.0.0.1 as the address and 5517 as the port in your SetiQ settings. That should allow your client to connect to itself since you can ping the loopback address both online and offline.

As far as the ping, your syntax isn't wrong. You just can't specify a port when you use ping so it doesn't recognize the command.

Rob
 
Sukhoi: Bah! There's no challenge in that! Spoilsport! 😉 j/k

It's a better idea but I'd still like to see this work. Plus, the new SetiQ has such cool features & stats! 🙂

Rob
 
Um, someone needs to go to bed... Alarm goes off in a little over 5 hours. I'm glad tomorrow is Friday. Oh wait, today is Friday (EDT)! 🙂

Out...

Rob
 
i like setiq cuz of the stats. 😀

robor - i already tried that but it didn't work. this is driving me crazy. it's almost as though setiq is not setting itself up on port 5517.
 
I think you have the " going too far over,this is my shortcut commandline for SETI to join the old SETIQ I currently run

"C:\Program Files\SETI CLI\setiathome-3.03.i386-winnt-cmdline.exe" -verbose -proxy 192.xxx.x.x:5512

Note the " stops just after the exe
(yes I replaced numbers with x)
 
Did you get it working yet Tuffguy?

If not, try replacing your ip number with the word "localhost". Put it exactly where your ip would be. This means the switch should read -proxy localhost:5517



I have had to do this on two machines that are running my two setiQs.

Thanks agan Poof!
 
Just buy a $5 NIC and stick it in there and give it an IP addy but don't hook it up to anything, and then it'll work fine. 😉
 
Your welcome. But the real thanks go to Poof who originally helped me out. Especially cool, since she is on the ars technica seti team. But thats ok we still like her.
 
Back
Top