okay... we'll be waiting for your thoughts to be 'collected' ;-) --- more
below
----- Original Message -----
From: "Chuck Larrieu"
To: "EA Louie" ;
Sent: Wednesday, September 19, 2001 10:31 AM
Subject: RE: NAT and Telnet [7:20362]
> I'll have to think about the solution for a bit, but the reason it happens
> is really quite simple. I posted a problem like this a "Friday Folly" or a
> "Weekend Folly" a couple of months back.
>
> think in terms of router operation. e.g. what happens when a packet is
> received on an interface.
>
Actually, this is not really an order of operation issue.
> knowing router behaviour as well as protocol behaviour can help one solve
a
> LOT of problems
> ( hint, hint ;-> )
Here's a BIG hint: as a protocol, NAT is bi-directional. ;-)
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> EA Louie
> Sent: Tuesday, September 18, 2001 10:28 PM
> To: [EMAIL PROTECTED]
> Subject: NAT and Telnet [7:20362]
>
>
> I posted this on the Lab list...but I thought some folks here might enjoy
> the
> challenge, too. (Apologies to those who are on both for the cross-post)
>
> I was going to post a "how to" question about NAT, but I figured it out so
I
> thought I'd share the information with the list and challenge you with the
> solution.
>
> When using the address of the outside interface as the NAT overload
address,
> I
> could not telnet into the router. I could ping, but the telnet sessions
> would
> time out.
>
> I came up with a solution - can any of you figure out what it was? And
does
> anyone know the reason that this happens?
>
> -e-
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=20446&t=20362
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
