[c-nsp] Re: cisco-nsp Digest, Vol 38, Issue 30

[Church, Chuck]

Add 1.2.3.4 as a secondary IP address to the server sitting on the
inside.  Put a host route to 1.2.3.4 on the router, with 192.168.1.10 as
the next hop.


Chuck Church
Lead Design Engineer
CCIE #8776, MCNE, MCSE
Netco Government Services - Design & Implementation
1210 N. Parker Rd.
Greenville, SC 29609
Home office: 864-335-9473
Cell: 703-819-3495
cchurch at netcogov.com
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4371A48D


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of admin2
Sent: Thursday, January 12, 2006 1:00 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Re: cisco-nsp Digest, Vol 38, Issue 30

> Hello all,
>
> on on of our customer sites we have 1812 router.
> Public IP: 1.2.3.4 /30
> Lan IP: 192.168.1.1 /24
>
> Router is doing nat in following configuration:
> access-list 1 permit 192.168.1.0 0.0.0.255
> ip nat pool customer 1.2.3.4 1.2.3.4 netmask 255.255.255.252
> ip nat inside source list 1 pool autovia overload
> ip nat inside source static tcp 192.168.1.10 25 1.2.3.4 25 extendable
>
> Problem is, that it is impossible to connect to 1.2.3.4:25 from lan:
> telnet 1.2.3.4 25
> Trying 1.2.3.4...
> telnet: Unable to connect to remote host: Connection refused
>
> >From outside everything is ok:
> Trying 1.2.3.4...
> Connected to 1.2.3.4.
> Escape character is '^]'.
>
> Any suggestions, how to enable lan connects to 1.2.3.4:25 ?
> Many thanks for any ideas.
>
> Best regards,
>
> Jan Gregor
>
>

Hey,

U can try to put "ip nat outside" on your lan interface, then it would
work
but you
cant use both external/internal address to connect to so you have to
deside.

Martin


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/