[jamesa]

hi,

I'm having serious difficulties with port mapping. I have read up on the different topics in the networking forum, and I've tried it all.

My network is set up as a cable modem plugging in to the WAN port of the airport. I have DHCP & NAT turned on, but the computer I wish to have the port open to the world I have set to manual IP address 10.0.1.201. This is outside the range of the DHCP IPs according to the Network tab of airport.

I have put in the desired port in Port Mapping, with the right IP address and right public/private ports. The thing is, when I telnet to the port I want open from within the network, it's fine. It's only when I try to use the port from outside the network there's a problem; so it's unlikely to be ipfw or anything running locally on the machine. Something is fishy with the airport.

The other thing; the Airport is not reporting my public IP address, which is a real pain in the ass because my ISP has a transparent proxy which screws things up like http://www.whatismyip.com

I got a friend to give me my IP, and I know it's right. But the port forwarding just won't work. I'm baffled.

Any help would be seriously appreciated.

-- james

[jamesa]

just as a follow up; I decided to open port 80, and turn on web sharing on my machine and port forward to it.

I ssh'd to a uni box and ran lynx with my ip address/~username.

What came up was a bit of a shock: the host http://pbg3.local/ could not be found. That's the rendezvous version of my computer name!

*Something* is getting through, but I think somehow Rendezvous is getting involved in this and screwing it up. It's like the ABS forwards the rendezvous address of the computer to the requesting machine outside of the network.

Telneting to the port still doesn't work. Man, this is killing me! Any help, really appreciated...

-- james

[jamesa]

I know that the port is opening and forwarding something because shields up is reporting that port 80 is open. If I then turn the firewall on on the server and block port 80, shields up loses it.

So *something* is getting through to the server; the ports are open, but something is still screwing it up.

-- james

[jamesa]

*bump*

help... please...