Need a little help w/ SetiQ--Got it. :)

[Woodie]

Can someone check to see if you can reach my Seti Queue?

tasetiq.dyns.cx
or
tasetiq.dyns.cx:5517

Thanks!

 

[Engineer]

No go from here. Are you using a router? If so, are you forwarding the port 5517?

 

[Woodie]

Thanks, Engineer.

Sort of a PITA...I had a dyns.cx address...but my new router will only do: dyndns.org, no-ip.com.

So I'm trying to do URL forward instead of a straight IP forward...but I don't think it's working.
I guess I'll just have to have all the clients start using tasetiq.dyndns.org instead.

Ok, I'll go create a tasetiq.dyndns.org forwarder instead. Be right back.

 

[Coquito]

Yeah, after you notified me that you would be playing with things abit, I thought nothing of it. I was using you queue up until this weekend, when I noticed I had several cached results that weren't sending.

Please let us know when we should hop back on, as I know too many people are using the main guys, & (knock on wood)if any one of those them blows a fuse, we would be in a heap of trouble.

Thanks for providing us with a stable queue for when berkeley goes bonkers on us.

 

[Woodie]

It should be up now....note the *new* queue name:
server: tasetiq.dyndns.org
port: 5517

 

[Engineer]

Originally posted by: Woodie
It should be up now....note the *new* queue name:
server: tasetiq.dyndns.org
port: 5517

Works just fine!


http://tasetiq.dyndns.org:5517/

 

[Coolkid]

Originally posted by: Woodie
Sort of a PITA...I had a dyns.cx address...but my new router will only do: dyndns.org, no-ip.com.

You should just be able to install one of these clients on one of your internal pcs, and it will update the IP for you

 

[Woodie]

Hmmm...took a quick look...but not clear it'll do what I need (Appears to assume that my PC is directly connected?) In any case, this is now working, so I'd rather leave it that way.

Thanks for the help! It's hard to check the queue from right here!