Re: (ASCEND) NAT on P75: Incoming Connections Possible only on Well-Known Ports

To: Rob Myers - Unicom Communications <rmyers@unicom.net>
Subject: Re: (ASCEND) NAT on P75: Incoming Connections Possible only on Well-Known Ports
From: Peter Chow <peter@interq.or.jp>
Date: Wed, 04 Mar 1998 12:44:51 +0900
CC: ascend-users@max.bungi.com
Organization: interQ Inc.
References: <Pine.GSO.3.95.980303112822.1053A-100000@s325b.unicom.net>
Reply-To: peter@interq.or.jp
Sender: owner-ascend-users@max.bungi.com

You have to hang up and re-establish the connect.  Mentioned
in the release notes.

Rob Myers - Unicom Communications wrote:
> 
> I have found that when you make changes to your translations (ports, etc)
> you have to hang up and redial or possibly reset the unit.  They don't
> take effect immediately, it's been my experience.
 
----------------------------------------------------------
Peter Chow
Chief Technical Advisor
InterQ Inc.
Tokyo, Japan
peter@interq.or.jp
----------------------------------------------------------
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

References:

(ASCEND) NAT on P75: Incoming Connections Possible only on Well-Known Ports

From: Rob Myers - Unicom Communications <rmyers@unicom.net>

Prev by Date: (ASCEND) tftp
Next by Date: Re: (ASCEND) MPP over multiple B channels?
Prev by thread: (ASCEND) NAT on P75: Incoming Connections Possible only on Well-Known Ports
Next by thread: (ASCEND) connection issues (unstable)
Index(es):
- Main
- Thread