-
From: Tolstykh, Andrew [mailto:atolst...@integrysgroup.com]
Sent: 27 February 2009 07:24
To: John Kougoulos; Shaikh,NM,Nasir,JRS1 R
Cc: cisco-nsp@puck.nether.net
Subject: RE: [c-nsp] Interesting NAToverload issue
Long term your client should consider migrating to the RPC over HTTPS
connectivity
-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of John Kougoulos
Sent: Wednesday, February 25, 2009 5:49 AM
To: nasir.sha...@bt.com
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Interesting NAToverload issue
Hello,
you could split the usage of nat pools based
Hi,
I have a client who has moved their Microsoft Exchange servers to a service
provider location (as part of a de-perimeterization strategy). These servers
are reachable via the Internet. Thus, the client IP are NATted before they
cross the corporate boundary.
There are about 45000 users.
@puck.nether.net
Subject: Re: [c-nsp] Interesting NAToverload issue
Hello,
you could split the usage of nat pools based on statistics of the source
IP addresses eg use 1 ip/overloaded nat pool for even source IPs and
another IP for the odd source IPs
Best Regards,
John
On Wed, 25 Feb 2009, nasir.sha
Hello,
you could split the usage of nat pools based on statistics of the source
IP addresses eg use 1 ip/overloaded nat pool for even source IPs and
another IP for the odd source IPs
Best Regards,
John
On Wed, 25 Feb 2009, nasir.sha...@bt.com wrote:
Hi,
I have a client who has moved
