[Since EBCDIC]

Dad's got a Belkin router with three computers hanging off. IP addresses via DHCP from the router, getting values like 192.168.2.x. Each box is advertising its IP to dyndns.org so I can refer to each machine by name; necessary for me.

I turned the router's firewall off since each Mac OS X box has one (over which I have better control).

Here's the question: must I choose one machine to control ahead of time and then set up port-forwarding to that machine? (Doesn't each Belkin router give the same bunch of IPs to its clients and then send out TCP/IP packets with its own IP, parcelling them to the appropriate machine upon it's return?) As long as I have DHCP I can use only one machine behind the NAT, but if I got static IPs I could get to all three?

Did I get that right?

[kampl]

Here's the question: must I choose one machine to control ahead of time and then set up port-forwarding to that machine? (Doesn't each Belkin router give the same bunch of IPs to its clients and then send out TCP/IP packets with its own IP, parcelling them to the appropriate machine upon it's return?) As long as I have DHCP I can use only one machine behind the NAT, but if I got static IPs I could get to all three?

Did I get that right?

I am assuming that your dad is PAT'ing to the single ISP provided address for all machines on his local network. Soo, with inbound connections to his private LAN, one can only PAT a service to a single device inbound.

For instance, if he had a telnet server set up, the router could only forward inbound telnet connections to his private LAN to one host. If there are multiple telnet servers on the local LAN, an address pool statically NAT'ed would be required to make them all available to the Internet.

Following me?