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

TeAm AnandTech SETI needs some help with Redirecting one PORT to another

Smoke

Smoke

Distributed Computing Elite Member
I need some help in REDIRECTING one PORT to another PORT.

I am running a SetiQueue for TeAm AnandTech. This is a program that serves as a backup server for our SETI TEAM. Members point their Seti Software to my IP ADDRESS including a specific PORT and the software program handles the rest.

Problem:

A long time SetiQueue Operator (OrangeKid) has decided to stop providing the services of his SetiQueue. Many of our TeAm AnandTech Members that normally use his Queue have now been redirected to my server. All users of the OrangeKid SetiQueue that direct their Seti Clients to his IP ADDRESS of teamanandtech.seti.com have been forwarded to my server: smokeball.dns2go.com. All of that is fine and OK BUT Orange Kid used PORT 5001 for his server ? I am using PORT 5517 for mine. I?ve been told that I need to REDIRECT all of the Clients coming in to PORT 5001 to PORT 5517. I don?t know how to do this and I would appreciate some help.

I am using a Linksys Router and the OS is WindowsXP Professional.
 
My router is Linksys BEFW11S4 V.2

I'm not sure about "Iptables page".

It has a page named FORWARDING with a sub-page named PORT TRIGGERING.

???
 
I took a look at the user's guide, and I don't see how we can get this done with the linksys. Let's hope someone else will chime in here with an answer.
Can you get your clients out there to switch ports?
 
Getting the Clients to just change their PORT Numbers and HOST Address would definitely be the best solution "for me".

It is my understanding that many of the Clients cannot get to the machines to make the necessary changes. We would not want to lose the production from those computers.

I have attempted a "fix" but I am not sure if it is going to work. Within the SetiQueue Program itself is a redirect for a Proxy Server. I installed a 2nd instance of SetQueue and setup its Host/Port as "smokeball.dns2go.com:5001" but redirected it to Proxy Host/Port "smokeball.dns2go.com:5517". I do not have any evidence that this has fixed the situation. I would have expected a flood of Results and requests for new WUs if this "fix" worked.
 
Yes, I'm forwarding PORT 5001 and PORTS 5501 - 5599 to the Server Machine on my LAN.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top