|
Posted by Leythos on May 17, 2006, 8:54 pm
If you were Registered and logged in, you could reply and use other advanced thread options
eugenio@iatmgu.com says...
> I recently got a domain...www.mydomainname.com for discussion purposes.
> This domain points to the external public ip of my firebox and port 80
> is nated throught to an internal web server. If I browse to
> http://www.mydomainname.com from a computer outside my firewall
> everything is ok, but If I browse to it from a computer within the
> network it does not work. I think this has to do with "loopback" but
> I'm not sure. In the traffic monitor on the firefox it shows something
> like this when I try to browse from the internal pc:
>
> 05/16/06 10:06 http-proxy[4395]: [<int ip here>:1662 <ext ip
> here>:80] Error while sending/receiving: Can't receive data from server
> (Connection refused)
>
> The tracert from the internal pc looks like this:
>
> Tracing route to www.mydomainname.com [<ext ip here>]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms <ext ip here>.something.so.so.net [<ext
> ip here>]
>
> Trace complete.
>
> On a linksys router I just have to uncheck "Internet NAT redirection"
> and everything is fine, but I don't know what to do on a firebox.
I've never seen "loopback" work on any Firebox, and I don't even think
it's an option. I've put in about 80 of them over the last couple years
and always used an internal DNS server to resolve the public names to
the local network addresses so that it never has to loopback.
--
spam999free@rrohio.com
remove 999 in order to email me
| 
XML site map