On your behind-nat-firewall allstar server, enable telnet on port 21. Change your firewall to forward port 4569 to <LAN-allstar-server-ip>:21. Then, from an outside ip (friends house), try to telnet to your own <ISP-IP>:4569. You should hit the inside server's telnet login.

If this is NOT the case then your firewall/forwarding setup is wrong.

/S

—————

iThing: Big thumbs & little keys. Please excuse typo, spelling and grammar errors • Good planets are hard to find – think before you print • My desire to be well-informed is currently at odds with my desire to remain sane.

On Apr 15, 2012, at 4:31, Ken Robinson <ken-robinson@o2.co.uk> wrote:

Hi Scott / Tim,

I am afraid I have run out of ideas, I have even changed the 4569 port to 4568 just in case 4569 was still trying to latch itself onto the defunct G0LCE server.

I also changed the port access in my router settings and in iax.conf files.

I have my own dns server here and I can see my system and the portal talking to each other so I can only think that it is a port forwarding problem.

One point, I have Echolink enabled and have the correct ports open too, does Echolink use the Allstar port 4569 too or does it access via the Echolink ports.

If the answer is “it uses its own ports” then my theory of it being a port forwarding problem is shot down as it would need 3 ports to be setup wrong

Could it be that the data on the Allstar Portal has been screwed up because of the way I originally set 2 servers on there. If so how can we un screw it

Would re installing everything from here be worth trying?

Regards Ken G0LCE

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users