I have a router set up with persistant port forwarding to forward all DNS connections to port 53 to port 80 on my server comp. My problem is that my dynamic dns can only be connectied to from computers in my lan because the ip of my host is 192.168.2.1 the default router setting. I have a client that updates the ip for my site on dyndns.org, but it always gives the IP 192.168.2.18 and that is my server computer in the network. I have also went to ip listing sites and have tried to have people connect to the ip they say I have, which is, as I have found to be, the WAN IP address for my router, but they get errors, and even on my server machine, it does not load anything, but no errors. I have the router setup to connect to my isp with PPPoE, I have the choice of doing dynamic IP but I havent tried that yet. I have had many people try to get to my site online but they just get errors or get their own router config site. I need people to be able to connect to my network and view my site, server is apache 2. Any help will be hugely appreciated.

Heh, your problem is because you're giving out a reserved IP. It cannot be routed across the Internet because it's reserved for use on private networks.

What is the WAN IP on your router? I suspect it's a private IP. I think what's happening is that you have a DSL router doing PPPoE and your Internet IP is actually on the WAN side of the DSL router. You then have a broadband router (Linksys?) plugged into the LAN side of the DSL router. Now the port on the broadband router is labled "WAN" but it's actually plugged into the LAN port on the DSL router and the DSL router is using a private IP, since the Internet IP is already assigned to the WAN side of the DSL router. Now your broadband router has a private IP on the WAN side, and of course it will use a private IP for the LAN side as well (like it's supposed to.

You need to log into Dyndns.org and try to create a new host record in your zone. By default it will fill in the IP address you are connecting from for the IP of the new host. That's the IP you need to use.

By the way, you're not really forwarding port 53 to port 80, are you? Those are for two different things. Port 53 is DNS, port 80 is HTTP.

thank you, but the problem is still there. I logged into dyndns and made a new host, but the problem still exists, no one else can view the page except me. my WAN IP and gateway etc are:
and my router is unfortunately a microsoft router ( cheapest one there ) Its the mn-500 basestation. Thanks, any more help would be great.

Interesting ports on adsl-68-76-144-21.dsl.akrnoh.ameritech.net (68.76.144.21):
(The 1147 ports scanned but not shown below are in state: filtered)
Port State Service
21/tcp open ftp
113/tcp closed auth
5050/tcp closed mmcc

I assume you're using ameritech and you're in Arkansas? Hopefully that is you and not someone else I just scanned...

Any way, the IP is reachable. It looks like the outside of your router is what's responding. It's very normal for broadband firewall/routers to have port 113 closed instead of stealthed to improve performance with certain Internet applications that attempt to contact an Ident server.

It looks like you just didn't setup your forwarding rules properly, or perhaps your ISP filters inbound traffic?

PS Do you have an HTTP server running on your network? If so, try forwarding port 8888 to port 80 on your web server IP. I'll try to connect to port 8888 and see if I can see your website. That should confirm everything is working. If you mimic that setup for port 80 and it still doesn't work, then it means your ISP is filtering it unfortunately.

Yea thats me, but I'm in Wisconsin. I get the exact address thing as you when I ping myself so thats good. Im going to forward that port right now... And yes, I have apache 2 running right now on my server machine.

sucess! Everyone Ive asked has been able to access http://68.76.144.21:8888/ and it works, but how do I get http://68.76.144.21 just plain old that to work? do I forward port 80 to my server port 80?
Than you sooo much. If I could pay you I would. You've actually took the time to read my post

Wow yeah it works. All I can say is... interesting color scheme? Heh heh.

Yes, now try forwarding 80 -> 80. You should be able to have that coexist with the same rule for 8888. If you set them up exactly the same and 8888 works while 80 does not, that means Ameritec is one of the mean-spirited ISPs that's giving it's users second-rate service.

Edit: Ohh, you're golden.

Thank you so much, I forwarded 80 to 80 and it worked fine. hhahah the colors are temporary, but they look kinda cool on my machine Thank you again!