ADSL ROuter and DMZ Settings

[shearder]

HI All

I am connecting via ADSL. I have configured a DDNS Service with Siteloutions. This all seems fine. I can connect to my ADSL Router via my browser using the external dynamic IP and i can get to the configuration console. I can ping the IP too, obviously.

Now the problem is this, forgetting the time taken to propogate the DNS settings etc, i have configured my ADSL router to forward all requests to any port to an internal server. This i did using the DMZ settings.

I have setup a temporary website on the server using port 80 and stopped all other sites. I then tried to connect to my external IP which should, theoretically, forward the request to my server using port 80, (i hope i am correct so far) but it is not opening the home page. I have checked the default documents in IIS and all is well. it SHOULD open... any ideas will be appreciated!

Regards and thanks,

Sean

[bakedjake]

Did you try connecting to your site from an external IP (one not behind your firewall)? Cheap NAT routers have a problem directing traffic out of then back into a NATed enviornment.

[shearder]

Nope... i haven't tried from an external IP address. However, with that said, if i understand your question correctly, i did manage to access my router via webbrowser to the external IP... is this not the same idea?

*shrug*

[bakedjake]

No, not the same thing. You're accessing the router by connecting to an internal IP, I imagine?

Try connecting to your site via AOL or something. See if it works. If not, run a traceroute and see where it dies.

And welcome to WebmasterWorld, Sean!

[shearder]

First, thanks for the replies so far -

I do access the router via internal IP i.e. 192.168.8.1 but the external IP is i.e. 123.123.123.123 and this is what i used to test with the browser using port 8080. (123.123.123.123:8080)

I then get access authentication request and then can access "remote admin"

I hope that made more sense...

[bakedjake]

It did, and that should work. The reason it's working is because the device does have an actual external IP adreess of 123.123.123.123. The only translation its doing for you to respond to that is just internal.

When you try to request 123.123.123.123:80, it will try and do a double NAT onto itself(in->out->,fw->in), and this will fail.

Try it from an external source. It very well might work.

[shearder]

Thanks again. I shall try that.