Link to home
Start Free TrialLog in
Avatar of madeoninfo
madeoninfoFlag for Greece

asked on

Forwarding port 80 requestes to server in LAN

Hi, I am trying to forward http requests from my router to a web server in our company LAN. I have tried many combinations with the port redirection utility that the router is offering with no success. I tried the same with a Linksys router and it worked fine which eliminates possible problems in the LAN or the Web Server. Unfortunately my ISP doesn't support well the Linksys router so I have opted for the D-Link that they supplied to me.

Could anybody share their experience with the D-Link DSL-2640B port redirection. I tried 80, 8080, 8081... but no luck...
Avatar of Kamran Arshad
Kamran Arshad
Flag of Pakistan image

Hi,

Change the ports to 80 in below article and check if any firewall is ON:

http://portforward.com/english/routers/port_forwarding/Dlink/DSL-2640B/Utorrent.htm
Avatar of Rob Williams
Following from the same site more directly references port 80:
http://www.portforward.com/english/routers/port_forwarding/Dlink/DSL-2640B/HTTP.htm

One thing to check is web management enabled on the D-Link from the Internet? If so and it is set to use port 80 you will not be able to forward port 80 to an internal web server.
Avatar of madeoninfo

ASKER

Hi,

Thanks for the links but I have tried all the mentioned settings. My last attempt to do the redirection without conflicts has stopped at the following point with no success.

1) For the remote management I setup the 8081 port (remote-management.png)
2) If I try to redirect the 80 port I get a strange message about the port 80 being used  (port-forward-to-80.png)
3) I changed the port of the web server to 8080 and tested it locally in our LAN which works fine and I made a forwarding of the port 8080 to the internal server (port-forward-to-8080.png)

Still no luck as when I attempt to connect to the web server from the outside world nothing happens... :(
remote-management.png
port-forward-to-80.png
port-forward-to-8080.png
Perhaps try disabling Remote HTTP management all together in the 2 boxes. I have seen a few routers where you have to do this.
Internally though for your port forwarding to your web server you must use port 80, you cannot change that, at least not easily.
After deactivating the remote administration and redirecting the port 80 I noticed the following:

1) I still cannot connect to the server with the static IP that I have when I attempt it from within the LAN that the server and router resides
2) I tested the connection to the server from a PC outside the LAN and it connected successfully

How can it be possible to connect from outside the LAN and not from within. My limited knowledge on the subject pointed me to a loopback issue in the router so I setup a DNS name linked to the static ip and attempted to connect with this name. Again outside the LAN everything is OK but from within no connection :(
ASKER CERTIFIED SOLUTION
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I am using the Externel/Public IP. It worked fine with the Linksys router that I had so I thought that it should work with my D-Link. The linksys by the way had NAT settings you could adopt to your needs unlike the d-link router. I tried to get more info from D-Link but gave up shortly. The important is that the web server is up and running and that the problem probably resides in the router itself.

For more input on hair pinning I checked out this link: http://searchunifiedcommunications.techtarget.com/sDefinition/0,,sid186_gci1037278,00.html it might come handy to someone else in the future

Thanks RobWill for putting my mind at rest and giving good advice
Some routers support hair-pinning and some don't. It's hard to find documentation that will tell you whether most units do. It seems a lot of the small office and home routers do not.

Thanks madeoninfo,
Cheers
--Rob