Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[thomas.alrek]

Hi.

I have a minor issue with a DFL-800 i set up.
I am hosting a website on the public WAN address, and it works great. I can reach the server from the outside, using both the dns name, and the ip.

But, when I try to reach the server from inside my LAN, it just times out.
I have read some other topics about how I have to configure NAT Loopback, but I can't get it to work.

My network is setup like this:

WAN1 -> DFL-800 -> LAN, no DMZ.


I tried to make a rule for http outbound (SERVER_IP -> LAN -> CORE -> WAN1_IP), both a SAT rule, and a NAT rule, and a "ALLOW" rule, but none seems to help.


Could anyone here point me in the right direction, I am totally stuck.

 

Best regards,
Thomas

[FurryNutz]

Link>Welcome!

• What region are you located?

Is there any information in the User Manual about this?

I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.

[thomas.alrek]

Thanks for the reply. I am located in Norway.

I must add that I can reach the server if I use its internal LAN ip address. But then I would have to either setup a local DNS, or modify all clients hostfile, and I was hoping to avoid this.

I tried to setup NAT Loopback as described in one of the supplemental manuals I found on D-Links ftp, but those where written with DMZ in mind. I tried to adapt it as well as I could without the DMZ configuration, but I couldn't get it to work.

If no one have some smart trick, or anything, I will try to call D-Link, but I was hoping someone else has had this problem before.

[FurryNutz]

Can you try the configuration with using DMZ?

[Rara Avis]

Make a port forward like the one you made to allow the WAN to access the server, use the following rules.

SAT lan/lannet core/wan1_ip SAT_Dest Server_IP
NAT lan/lannet core/wan1_ip

Your web server will see all the traffic as coming from the DFL itself, but it should work.

A DNS split horizon is a more elegant solution if you want to keep the server on the LAN however.  If only to limit the unnecessary NAT.

a DMZ is a better solution yet, separate your risk classes.

[thomas.alrek]

Thanks buddy, this worked! Really appreciate it

[FurryNutz]

Glad the information helped.

Enjoy.