Can't get HTTP port forwarding to work!!!!!!!!!

[snikde]

Okay,

My head hurts! I am getting ready to set up a new 2003 Small Business Server Premium Edtion. In an effort to teach myself web serving basics I am working with my current NT server and a MAC OS X machine to test serve a few simple web pages. I have Verizon DSL (dynamic IP, I use NO-IP tool to update DNS) running through a Linksys Firewall Router. I have IP forwarding set to the MAC running OS X and Apache. Internally when enter

http://90.0.0.21

into the browser, Viola! Web Page is there. If I type in

http://141.154.XXX.XXX

(the dynamic IP) of Verizon... nothing! The router is supposedly set up to port forward port 80 requests to the Mac but nada. I had a NetGear router and took it back because I thought it was bad. Do I need to NIC's in the web server? I am pretty savvy and had the Mac doing this sometime back when it had two NIC's in it and one of them attached to the DSL modem, the other using an internal series of IP's. I have also tried running Xitami on the NT server but same problem. I do have WinProxy running on the NT server but its HTTP and FTP ports are disabled so as not interfere with the web requests inbound. I just use it for mail filtering.
I called Verizon to see if they port block. They don't. Just want to publish two or three pages to the web. I figure once I get this licked I can move onto SBS 2003. STUMPED IN MASSACHUSETTS.

 

[DJCordel]

Hello...

Have you tried from outside of the router/firewall to access the server. I had the same problem, and when accessing the server from any machine that is on the same network (behind the same router/firewall), it could only be done using the local IP. But if I used a machine outside of the router/firewall, everything worked just fine with no problems. I think it has something to do with the way the router handles the request. In my case, the router actually holds the IP from my ISP, and my machines behind the router use private IP's with port forwarding. So when I make a request for my own IP, all it does is go right to my router. The router does not send my request to the ISP DNS servers and then back to itself so that the traffic can be port forwarded. Its almost like the router is one step ahead of the game, but in a bad way. Anyways, Im sure there is a technical explaination for why it does this, but if your situation is like mine, you will find that when you try it from outside your network, it will work just fine. And for inside, its a good chance you may just have to use the local IP address to access it.

Anyways, hope any of that helped!

Jason

 

[snikde]

Jason,

I have tried reaching the web server from the "outside" I even had the router vendor try it from CA. No luck. Inside the router it all works. Outside it doesn't. I am ready to through in the towel. Thanks though.

Guy

 

[DJCordel]

Hello...

Have you tried to access from another port number? For example, set your server to respond to port 4500, set your router to forward on 4500, and use the address

http://141.154.XXX.XXX:4500

from a computer outside your network to try and access it. The only reason I say to try this is because; my ISP blocks port 80, but if I called them and asked them if they did, I’m positive that they would say they do not. The reason is, the guy you speak with on the phone is most definitely not the guy that would be making the decision to block port 80, and I imagine he would not know even if they were. Anyways, I guess it’s worth a try. Well, hope you get it working, I know how these things can be very frustrating!

Jason

 

[snikde]

Jason,

I did try your suggestion but it still does not work. I cannot believe the router is bad because that would mean that two in a row were bad, and works for other protocols like browsing outbound. I just must have something really messed up!!!!

Guy

 

[cjkenworthy]

You may have allowed incoming traffic on port 80 TCP, but the router may be fire-walling traffic out: i.e. the request can come in, but not be returned to the client. Try allowing port 80 outwards on TCP if this is the case.

An idea to try?