Hi Ben,

thanks for reply but DNS solution is not exactly what i need, because then
you are not able to use port forwarding option. This is important if you are
using different services on separate servers. For example under FQDN name
mail.mydomain.com I have mailserver on internal server1 but webmail is on
internal server2. So I need to forward requests to ports 25,465,995,993 to
server1 but requests for port 80,443 to server2. So DNS solution is usable
only in simple scenarios.

Some another solution?


Ben Hartmann-2 wrote:
> 
> Hi Caizi,
> 
> maybe I've got another solution for you...
> 
> The way we've solved this is DNS. Certainly we've got an external dns
> mail entry on a public dns server. But inside our office network is our
> internal dns server responsible and so we've configured an dns entry to
> point from our (external) mailserver dns entry to the internal ip of the
> mailserver. This way all our laptop users can configure their mailclient
> to mail.*com and wherever they are they get either the public ip
> (through a public dns server outside the office network) or they get the
> internal ip of our mailserver (through our internal dns server).
> 
> Hope you anderstand what I mean...
> 
> Hope that helps,
> Ben Hartmann
> 
> Caizi wrote:
>> -----Original Message-----
>> From: Caizi [mailto:ca...@seznam.cz] 
>> Sent: 07/18/2009 12:14 PM
>> To: efw-user@lists.sourceforge.net
>> Subject: [Efw-user] NAT Loopback change in Endian Firewall 2.2
>>
>>
>> Please does somebody know why there is change of IP NAT Loopback
>> behaviour in
>> EFW 2.2? Or how to correct problem?
>>
>> I need access internal servers from LAN by external IP with port
>> forwarding.
>> For example we have some users with laptops who occasionally work from
>> home
>> so their email client is set to the WAN IP, but when they bring the
>> laptop
>> into the office they are unable to connect to the mail server without
>> changing their email client to the LAN IP of the mail server.
>>
>> Before I was using EFW 2.1.x and there it worked correctly without any
>> special options. But with 2.2  it is not working. I could succesfull
>> ping or
>> access endian web admin interface https://external-ip:10443 but
>> accessing
>> some other services in internal network is not working.
>>
>>
>> Thanks for help.
>>   
> 
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge  
> This is your chance to win up to $100,000 in prizes! For a limited time, 
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full
> prize  
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> Efw-user mailing list
> Efw-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/efw-user
> 
> 

-- 
View this message in context: 
http://www.nabble.com/NAT-Loopback-change-in-Endian-Firewall-2.2-tp24549413p24555302.html
Sent from the efw-user mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Efw-user mailing list
Efw-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/efw-user

Reply via email to