|
Title: Internal webserver - can't reach webpages from internal pc Post by: mrt on Wednesday 23 June 2010, 08:13:56 pm Hi,
I have EFW 2.3 and one internal webserver hosting my Exchange server and own domain (e.g. mydomain.com). I can reach my server outside my network with OWA (Outlook Web Access) with mail.mydomain.com and use Exchange on iPhone. But, if I sit inside my network and type mail.mydomain.com I can't reach it, I only see Firefox "warning" me that I com to my official IP:10443 (e.g. 88.125.36.27:10443. Also my www.mydomain.com get the same "warning". If I type the ip adresse for the internal exchangeserver I can reach it, but not if I use dns name. What could this be? Regards Title: Re: Internal webserver - can't reach webpages from internal pc Post by: mrt on Tuesday 29 June 2010, 05:41:15 am Any hint?
Title: Re: Internal webserver - can't reach webpages from internal pc Post by: mrt on Monday 05 July 2010, 10:56:07 pm This is a "zzzzz" Endian forum.
Is there anyone who can help me with some DNS issue? Regards... Title: Re: Internal webserver - can't reach webpages from internal pc Post by: medic215 on Tuesday 06 July 2010, 03:06:19 am No replies??? Seems like every issue that is a real issue is never replied to on this forum. I have a similar problem, but it is a local chat/IM server that I cannot access using the FQDN (i.e. chat.mydomain.com) as I could with an older version of Endian.
Title: Re: Internal webserver - can't reach webpages from internal pc Post by: mrkroket on Wednesday 07 July 2010, 07:53:23 am People usually help with problems they have had and they resolved.
So if no one suffered this issue, maybe no one helps. IMHO it seems that the system is not forwarding on GREEN. You have a rule on RED to port forward some traffic to an internal server. Let's name mail.mydomain.com as 88.125.36.27. If you reach your firewall from RED, the port forwarding rule is fired, and the traffic is routed to the internal IP of your mail server. BUT, from inside the IP 88.125.36.27 is for the firewall, and if you try to use http://88.125.36.27 the port forwarding rule isn't fired (as it is a rule for RED only). Your possible options: 1- Change your internal DNS resolution to point mail.mydomain.com to the internal IP. Go to Network->Edit hosts. Create a new host: IP: <<IP of the internal server>> hostname: mail domain: mydomain.com Apply. Test nslookup mail.mydomain.com to see if resolves to the internal IP 2- Create an static route to your mailserver (not sure if it works). |