Problem #1: your rules are incorrect, and the init-script even tells you that if you care to read the output.
Problem #2: whatever service you're running on port 10080, it's only listening to the loopback addresses 127.0.0.1 and ::1, and thus can't ever be reached from any other machine, no matter what you change in your firewall rules.
You need to check the service that's opening port 10080. It should listen on your outgoing IP (IP address of the interface that's connected to other machines) which is not happening according to the netstat result. That's because iptables is not loading correctly.
The iptable rules that you have mentioned have syntax error. It should be
-m state --state NEW
First flush the rules:
iptables -F
Then, correct the syntax and reload iptables.
If you have nmap installed, you can run a check on the opened ports both from the local machine and from the client machine to see if the port has opened up successfully or not.
You can get the same result by running the following commands on the server:
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 10080 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 10081 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 10082 -j ACCEPT
but still failed when apply the configuration.
If the case like this. Is there any possibility to open the port. so the port accessable from other server?
Ok, without focusing on iptables too much, lets first clear up what you want to do. HTTP forwarding via SSH? How exactly? Do you run your SSH client with dynamic forwarding?