Port Forwarding to IIS not working from internal network

[Cuberice]

I hope someone can help me with this.

I have a Web App running on a IIS7.5 server on a PC at home. I set up the Port Forwarding on the Router's NAT Virtual Server to forward port 80 to 81 on the local machine running the IIS and my WebSite/App has a Binding to both port 80 and 81.

Using the external IP (DynDNS) address from my router, I can access my WebApp from outside (using 3g or so), seems like the Port Forward is wording.

But when connecting using my WIFI using the same DynDNS I get the Routers Setting page. Why is the the packet not forwarded to the IIS machine when connecting from the LAN?

Any Ideas?

 

[semaphore]

Are you going via http://host:81? Remembering that your router config runs its own httpd and is binded to 80, try changing the router binding to 8081 or something and see if that helps.

As for it working externally and not internally it could be a setting on the router not allowing public access to its config page thus allowing you to view your IIS server.

I am however guessing here.

 

[oldBastard]

Are you going via http://host:81? Remembering that your router config runs its own httpd and is binded to 80, try changing the router binding to 8081 or something and see if that helps.

As for it working externally and not internally it could be a setting on the router not allowing public access to its config page thus allowing you to view your IIS server.

I am however guessing here.

I think your first observation is correct.

You can either do;

A. Change your router's web page port.
B. Use your http:[servername]:[port] instead of the DynDNS internally.

 

[SBSP]

I'm Subscribed to this thread.

You mentioned

(using 3g or so),.....

Using ADSL/Fiber this is easy, but when it comes to mobile networks i always end up with 2 IPs , the Internal 3G (In ISPs Network) and the ISPs IP, Both IPs dont work with all of the Dynamic IP services which i have tried

 

[SauRoNZA]

Yeah either use the internal address and the correct port.

Or use a completely random port like 44 or something.