Ventrilo Tech Support - External users unable to connect to 2wire network.

I have a similar setup, and the same problem. This is my first post, so bear with me. Before I set my network up as defined by MindScrew, can we narrow this down? I am sure I have missed something along the lines of port-forwarding.

Quote:

Originally Posted by deadlystryker

AT&T FiOs. Multiple "set-top boxes" running on cat5 cables and coax.
Netgear gigabit switch in between.
192.168.1.101 (nate_pc) is my main, this box.
192.168.1.73 (server) running Ubuntu server 9.10. Remote administration of server through eBox.
The server is started on boot, in daemon mode (I guess...)
I am able to connect from my home network, but others cannot.
Outside connections can view my http server at hostname.
Ports are forwarded to 192.168.1.73 (TCP/UDP 3784. UDP 6100 after reading threads.)
DynDns Open Port Tool shows the port as "timed out", although I did have it show "open" once, but cannot return to that configuration.
Nmap shows port 3784/tcp as "tcpwrapped"
AIM: Deadlystryker88 best method of contact.

/etc/network/interfaces looks like

Code:

auto lo eth0

iface lo inet loopback

iface eth0 inet dhcp

Through eBox, I have an option of designating my eth0 interface as external.

Quote:

Originally Posted by eBox Administration

Traffic being routed through interfaces marked as external will be NATed. Also, services meant for the LAN users will not be available on external interfaces.