(ASCEND) [ASCEND] Incoming Ping/Telnet fail on a P50 with NAT/SAM

To: ascend-users@bungi.com
Subject: (ASCEND) [ASCEND] Incoming Ping/Telnet fail on a P50 with NAT/SAM
From: Carroll-Net <larry@carroll.com>
Date: Fri, 17 Apr 1998 10:12:43 -0400
Sender: owner-ascend-users@max.bungi.com

Greetings,

I have a Pipeline 50, which is given a Static IP when it connects to the Net,
and all outward functions seem to work fine.

However, I am unable to ping or telnet into the router from a remote site.

I spent an hour on the phone with Ascend support yesterday, who assured me 
that setting a static mapping would work, which doesn't seem to.

Using the natl command the router does give me back the proper IP yet I 
cannot ping/telnet/traceroute to it.

Has anyone had any experience with this?


---
Larry Siegel			| C A R R O L L - N E T, Inc.
201-488-1332 voice		| New Jersey's Premier Internet Service Provider
201-525-0424 dialup		|         
http://www.carroll.com	| Ask about our ISDN service!


++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

Follow-Ups:

Re: (ASCEND) [ASCEND] Incoming Ping/Telnet fail on a P50 with NAT/SAM

From: Mailing List Subscriber <mlist@kamel.starvo.com>

Prev by Date: RE: (ASCEND) Monitoring Peak Capacity?
Next by Date: Re: (ASCEND) mlppp + ascend + 3com impact + linux
Prev by thread: (ASCEND) FAQ..
Next by thread: Re: (ASCEND) [ASCEND] Incoming Ping/Telnet fail on a P50 with NAT/SAM
Index(es):
- Main
- Thread