Seti Queue Change: Woodie's TA Queue

[Woodie]

For the (few) users of my public Seti Queue:

I had to change the public name of the queue from:
tasetiq.dyns.cx on port 5517
to
tasetiq.dyndns.org on port 5517

I still have all your stats, just moved to a new server, with upgraded network. (no more token/ring. 😀)

Please update your clients, and thank you for your patience during the upgrade.

 

[Unforgiven]

another good free dns redirector is no-ip.com if you are interested. its what i use for my queue and ftp server on a dynamic ip.

 

[Unforgiven]

nm just read your other post, sorry for not catching the other one first.

 

[Woodie]

bump

 

[soni]

Hi Woodie, I will update my page tonight 🙂

I presume you still want to be on the public SetiQueue list?

 

[Woodie]

Soni: yes, please. You were on my list of people to contact, but work was interfering with my life. Again. 😉

and another bump.

 

[Coquito]

Finally pointed both my online rigs in your direction again. Sorry about getting your stats machine confused. 45 clients is kind of an overstatement. I really don't know what verizon is doing to you/me.

 

[Woodie]

LOL...yes you show lots of clients! Isn't DHCP wonderful??

 

[Coquito]

Anyway I can get that cleaned up on my end?

 

[thawolfman]

Woodie! :Q

What's going on man!? 🙂

-Ben-

 

[Woodie]

Bump. I have a few "extra" WUs...anyone want some?

 

[bunker]

Woodie, you can open another port, say 5518, and dedicate it to Coquito.

All he has to do is change the port in set driver then your queue should know it's him every time by that port.

Edit one of his clients on your queue with his name and that port number and it should be easier for both of you to track.

 

[Woodie]

Bunker:

Thanks for the tip. I'll try and set that up tonight, and see if that helps.

Do I still have to go through the existing clients, and use the merge clients function?

 

[bunker]

After he starts sending to the same port, you should be able to merge any other clients into that one that you changed the port on and not have to do it again after that. It shouldn't create any more clients as long as it's sending to a specific port.