Geekzone: technology news, blogs, forums
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.

44 posts


Topic # 147300 15-Jun-2014 17:22
Send private message

Slightly complicated set-up, will do my best to explain. All fairly cobbled together.

I am running my own mailserver (using hMailserver), has been up and running for a couple of years, working fine. I have a URL, which keeps the IP address accurate with the MX records etc, no problem with any of this.

I just received an updated modem from Orcon, as I am upgrading from ADSL2+ to VDSL. Set up all the port forwarding to replicate the old modem, and put it in place.

All looks like it's working fine, can RDP in from externally, so the port forwarding is definitely working.

However, INTERNALLY on the LAN, I suddenly can't check the email over IMAP. It announces that it can't connect to the server.

The email clients had been set to my dynamic URL, and had always resolved fine, even when locally. It always used to just identify my router as having the appropriate external IP address, and then port forward from there to the server. However, it seems like with this new router, this isn't working. I've run through all the configuration options I can see, turned off all firewalls etc, but still no luck. Router is a NF4V provided by Orcon, running on their Genius platform.

I had an email client on the same machine as the mail server, which was also connecting to the dynamic URL and failing. When I set it to, it works fine. However, pinging the dynamic URL also works fine, as does the RDP connection, so the issue isn't with the DNS resolution.

Any thoughts of how to make this work? Setting to the local IP address won't work, because I need to take several of these devices outside the LAN.

Filter this topic showing only the reply marked as answer Create new topic
27267 posts

Uber Geek
+1 received by user: 6695

Biddle Corp
Lifetime subscriber

  Reply # 1066094 15-Jun-2014 17:28
One person supports this post
Send private message

You need hairpin NAT or NAT loopback, something the vast majority of routers don't support or have enabled by default.

44 posts


  Reply # 1066098 15-Jun-2014 17:34
Send private message

I can enable "Lan Loopback" on each individual NAT entry. Would that be it?


'That VDSL Cat'
9062 posts

Uber Geek
+1 received by user: 1993


  Reply # 1066099 15-Jun-2014 17:34
Send private message

markboynz: I can enable "Lan Loopback" on each individual NAT entry. Would that be it?

sounds about right, no harm in trying regardless!

#include <std_disclaimer>


Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

44 posts


  Reply # 1066103 15-Jun-2014 17:45
Send private message

Seems to have worked, thanks! I still seem to have some issues, but not the ones I was having, so back to the troubleshooting drawing board!

100 posts

Master Geek
+1 received by user: 9

  Reply # 1066139 15-Jun-2014 18:54
Send private message

or split DNS, have a static A record entry for the DYNDNS name that points to the Internal IP (eg. 192.168.x.x.) and then when the devices are external to LAN they will pick up the external IP.

Filter this topic showing only the reply marked as answer Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:

Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:

Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:

Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.