We handle the situation exactly the same way... it is however useful
if your developers use relative refernces off the web root for images and
pages... that is to say pages should be linked as
\main_page\sales\northwest\images\logo.gif and not
"www.someplace.net/sales/northwest/images/logo" This will help as no
further resolution or pass through the DNS is required....
-----Original Message-----
From: William Bartholomew [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 18, 2000 6:00 PM
To: [EMAIL PROTECTED]
Subject: Re: Can't Access "inside URL" from an "inside client"
A packet can not go through NAT twice... i.e. if you use the
domain which resolves to a public IP address it will go through the
router (NAT) and then back to the server (NAT) which will fail... we
had this problem and the solution for us was to set up an internal
DNS server that resolved the domain names for our servers to
private IP address... instead of www.somesite.com resolving to
1.1.1.1 you get it to resolve to 192.168.0.1...
You could also achieve the some outcome using hosts files.... I
think...
HTH
Regards,
William Bartholomew MCP MCSE CNA CCNA
Assistant Network Administrator
Brisbane Boys' College
Phone: +61 (07) 3309-3622
Mobile: (0418) 199-661
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
