That's sorta what I did, make DNS entries for the internal IP addresses,
then point the servers to those. A bit of a pain, but it works... I was
looking for a more elegant solution (-:
Thanks to all that replied!
Greg
----- Original Message -----
From: "Lupi, Guy"
To:
Sent: Thursday, May 03, 2001 10:12 AM
Subject: RE: NAT question [7:3050]
> I have also had this problem with clients who host web sites internally.
> They try to get to the website by name and it of course resolves to the
> public address, which they then try to get to from the "inside" network
and
> it fails. In those cases we have had to put host file entries on the
> workstations to resolve the name to the private address for all inside
> machines.
>
> -----Original Message-----
> From: Evans, TJ [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 03, 2001 12:52 PM
> To: [EMAIL PROTECTED]
> Subject: RE: NAT question [7:3050]
>
>
> If I recall correctly access to/through
> the external addresses of internal machines from internal machines is a
> no-no.
>
>
> Internally - all should be well; i.e. - machines are able to communicate
> openly with each other
>
> Internal 2 External systems - all should be well, and if you have static
> address assignments they should be used appropriately.
>
>
> External 2 Internal - all should be well; i.e. - systems outside the
> firewall can access your internal systems fine
>
> Internal 2 External address of Internal system - um, no.
>
>
>
> Thanks!
> TJ
>
> -----Original Message-----
> From: Greg Smythe [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 03, 2001 12:10
> To: [EMAIL PROTECTED]
> Subject: NAT question [7:3050]
>
> Hello --
>
> I have some static NAT translating going on in my lab, and if I am
"inside"
> and try to telnet to the "outside" IP address of a machine, I get
connection
> refused. Telnetting to the "inside" IP address of the machine works. I do
> have
> an inbound access list on the "outside" interface, but it is allowing
telnet
> to the machine. Upon doing a show access-list command I see that the line
> for
> telnet is not even getting hit. So why can't I telnet to an "ouside" IP
from
> the "inside"? Strange thing is that I can ping the "outside" IP ok, but
any
> other sort of connections to it fail.
>
> Thanks!
>
>
> Greg
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
****************************************************************************
> *
> The information in this email is confidential and may be legally
privileged.
> It is intended solely for the addressee. Access to this email by anyone
else
> is unauthorized.
>
> If you are not the intended recipient, any disclosure, copying,
distribution
> or any action taken or omitted to be taken in reliance on it, is
prohibited
> and may be unlawful. When addressed to our clients any opinions or advice
> contained in this email are subject to the terms and conditions expressed
in
> the governing KPMG client engagement letter.
>
****************************************************************************
> *
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=3202&t=3050
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
