Need help setting up web server (yes, another one!)

[slightly]

Hi

I noticed another user was having almost identical issues to me in setting up his web server over an Airport, but he managed to solve them: unfortunately, I'm still having trouble. So I'm hoping someone can help.

Here's my setup. I have a TiBook G4, connected via an Airport to a DSL connection. I've turned the Apache server on, and amended the /etc/httpd/httpd.conf file so that both "Port" and "Listen" are set to "8000" (port 80 is blocked by Verizon DSL, I think). Because I have dynamic DSL, I've signed up at dyndns.org, but the name resolution isn't part of the problem: I simply can't access my site using the external IP if I'm connected through the Airport.

If I remove the Airport and connect my computer directly to the DSL (disabling Airport in the Network preferences and enabling the Built-in Ethernet) I can access the site through my external IP address (using port 8000) just fine. The name resolution works too, which is a nice bonus.

However, when I reconnect the Airport (and set the Network preferences back), my computer gets given an internal IP of 10.0.1.3. Connecting to the site using http://10.0.1.3:8000 works fine. Connecting using the IP that I get through checkip.dyndns.org does not.

I have set up the Port Forwarding in the Airport Admin utility as follows:

Public Port:8000 Private address: 10.0.1.3 Private Port: 8000

and reset both the Airport and the Apache server, and still no joy.
Is there anything else I need to do? In the Network panel of the Airport Admin, I have a "single IP address" (since I only have one computer), and I haven't enabled either DHCP or Airport-Ethernet bridging (I assume this is the correct setup).

Any ideas, anyone?

Many thanks
Matt Clifton

[mikemc]

Try turning on airport ethernet bridging, and allowing the DSL DHCP assigned address to hit your machine... You said you only have one machine, so having the airport just be a connector between the air and land lines would work... If that works, then you know its the port forwarding that's faultering here...

[slightly]

Well, I enabled "Airport to Ethernet bridging" in the Airport Admin, and restarted the ABS and server, and I don't see any difference. (Should I have done anything else? I left the Network preferences on "Airport") I'm getting the same result - can access through 10.0.1.3, but not my external IP.

Is the bridge supposed to apply the external IP straight through to my computer (that's what I infer from your reply...)? I'm not sure that that's happened, since I'm still 10.0.1.3 in Network preferences.

I had a go at turning off "Distribute IP addresses" in the Airport Admin, but it wouldn't allow me to do that since I'm on PPPoE.

:confused:

Matt

[mikemc]

I put my settings up on my site... you can get them at:

http://www.mikemccue.com/pics/pic1.tiff

http://www.mikemccue.com/pics/pic2.tiff

The PPPoE might be the issue, I'm not sure...

I have the following setup

CABLE -> SERVER -> AIRPORT ->LAPTOP

my airport acts as a bridge between the server and laptop... the server distributes ip's in the 192.168.x.x range for the local network. The AIRPORT initially wanted to hand out 10.1.x.x addresses to the laptop, but turning on the bridge and stopping the distribute IP's, now the address assigned from the server goes to the LAPTOP.

So, taking out the server, the situation is the same, only your dsl provider would be supplying the ip... it should be able to go right through to the LAPTOP...

I apologize for the .tiff pictures... I can't open them in IE. You'll probably have to save them to disk to open them... I'm learning, no picture converter yet... <G>

Good luck,
Mike

[slightly]

Thanks for the screenshots, but alas, it didn't work for me. I suspect it might be the PPPoE, too. I think that's the only way I can connect to my DSL, since plain "Ethernet" didn't connect me.

Looks like I'm going to have to try AppleCare....my hopes aren't high....

Thanks again
Matt