Address translation

It seems like this would come up with any web server and also
with just apache using rewrite rules.
The question is, can I teach DW that the page I'm editing is
at a particular web address?
I'm trying to move from prototype.js and scriptaculous that
Ruby on Rails uses to spry. I think that the way spry does things
will ultimately win out. The essential part of all this is to allow
web pages to be designed by designers and they tend to like tools
like Dreamweaver -- not vi or emacs like I use. And, much of the
niceness that RoR offers doesn't work, doesn't fit with spry and at
the same time, DW has the equivalent features. So, I'm trying to
come up with a "game plan" of having RoR be the server engine with
pages designed by DW. I'm currently using DW CS3.
Here is the first challenge: With RoR, you go to "restful"
addresses like /items or /items/18. /items will be the list of
items while /items/18 will show a page for item number 18.
By default, /items comes into RoR and goes to the index
method in the ItemsController. And then that (by default) renders a
page that originally lives at /app/view/items/index.html.erb. All
that can change if I explicitly tell Rails to render a particular
page but I'd like to "go with the flow" if possible.
So, utopia (in my new feature overload stupor) would be if I
could open app/view/items/index.html.erb in DW and just tell it
that it is an html page and its real web address is going to be at
/items. In particular, when I "test", I'd like to be able to just
hit the default "test in browser" button and have it work.
There are countless other ways to go about doing this but,
right now, I think I'd rather teach DW the address of each page
than retrain RoR. While /items isn't too hard, it seems like it
will get more and more difficult with the /items/10 page or even
the /items/10/edit page.
This is closely related to but not quite the same as server
side includes. The page that RoR actually renders is the result of
a number of pages that are spliced together. I *think* I want to
move entirely away from that; abandon RoR's templates and use DW's
templates.
Part of my ignorance is all the "application server"
technologies that DW "knows" about I don't know anything about. But
I don't understand why DW has to know which type of technology the
server is using at all. That seems very wrong to me.
Last... if there is anyone here that would like to start a
separate mailing list or something for people trying to use
Dreamweaver and Ruby on Rails, please let me know.
(By the way, I have found "Ruby Weaver". It doesn't actually
address the particular issues that I'm concerned about.)
Thank you,
Perry

Hi
Have you already placed any kinda natting in your ISA server ? coz i have seen the ISA server itself taking care of Natting and connected to the public interface of the router ethernet.
Do revert what kinda port mapping you require here in the router and what kinda addressing you have got over there at present ?
Also possible do post out a schematic diagram with the equipments and ips in place.
normal port translation works with this simple CLI..
ip nat inside source static tcp x.x.x.x 8000 p.p.p.p 80
where x.x.x.x is your internal ip and p.p.p.p is your public ip which you used to reach the outside world.
regds

Similar Messages

  • On UPnP and NAT (Network Address Translation)

    Why UPnP is an often asked Question.
    This article goes a long way to say why.
    A couple of Quotes
    *What is UPnP?*
    Universal Plug and Play (UPnP) is an architecture for pervasive peer-to-peer network connectivity of PCs and intelligent devices or appliances, particularly within the home. UPnP builds on Internet standards and technologies, such as TCP/IP, HTTP, and XML, to enable these devices to automatically connect with one another and work together to make networking - particularly home networking - possible for more people.
    *Are there other ways to solve the problem of NAT traversal? If so, why is using UPnP the best choice?*
    Yes, there are other ways to solve this problem, but no other mechanism currently exists as an industry standard to address this problem in an automatic way for the consumer and in such a universally-applicable way for the developer.
    Simply Automated Starter Package
    Other approaches require either manual intervention by the user or they require special development efforts by the Internet gateway device vendor and the software developer to handle the NAT traversal needs of specific applications. As a result, UPnP is uniquely able to solve this important problem.
    *Consumer does the work.* The manual intervention methods of NAT traversal require a consumer to use a browser, a graphical user interface-based tool on the PC, or a command line interface tool on the PC to change some settings on the Internet gateway device in the home. While some technical enthusiast users have little difficulty with this, many consumers do not feel comfortable doing this. Further, many consumers may not even realize that NAT traversal problems are interfering with their use of services across the Internet. _The user may be attempting to play a multi-player game or engage in some other peer-to-peer service but find he or she cannot connect for some reason._ This leads to troubleshooting, support calls, customer dissatisfaction, and reluctance on the part of the user to try new services or experiences in the future.
    *Developer does the work.* To avoid requiring the consumer to solve this NAT traversal problem manually, some Internet gateway device vendors have written and included application layer gateway support into their devices. This application layer gateway software is designed with specific applications in mind. In other words, the device vendor writes and tests specific code that will automatically enable one application to go through the NAT. If the application software is updated, the application layer code the device vendor wrote may have to be updated and tested again. This one-at-a-time way of chasing the NAT traversal problem is manageable for device vendors when there are only a few peer-to-peer or relevant applications to consider, but this approach does not scale well to 100s or 1000s of applications, can be very expensive to pursue, and likely requires specific knowledge of how each of these applications function. The better way to approach this problem is to have the device vendor add software or firmware to their device once to understand UPnP and have other devices and software be able to communicate with the NAT device using this same technology. UPnP is uniquely able to fulfill this role today.
    I have underlined a passage in the last.
    I hope this helps in some way.
    6:58 PM Tuesday; January 1, 2008

              Look for bindAddr in the weblogic.properties doc.
              weblogic.system.bindAddr
              You can use a dns name instead of an ip address
              Mike
              David Chen <[email protected]> wrote:
              >We are planning to add a client that needs to access our weblogic cluster
              >through firewalls with IP address translation. According to the WebLogic
              >(5.1) documentation, this could be done by opening port 7001 in the
              >firewalls, and BIND WebLogic SERVER INSTANCES TO DNS NAMES. Does anyone
              >know how to bind WebLogic server instances to DNS names? Should it be
              >done in weblogic.properties?Thanks in advance,David [email protected]
              

  • Question on cluster and firewall IP address translation

    We are planning to add a client that needs to access our weblogic cluster through firewalls with IP address translation. According to the WebLogic (5.1) documentation, this could be done by opening port 7001 in the firewalls, and BIND WebLogic SERVER INSTANCES TO DNS NAMES. Does anyone know how to bind WebLogic server instances to DNS names? Should it be done in weblogic.properties?Thanks in advance,David [email protected]
              

              Look for bindAddr in the weblogic.properties doc.
              weblogic.system.bindAddr
              You can use a dns name instead of an ip address
              Mike
              David Chen <[email protected]> wrote:
              >We are planning to add a client that needs to access our weblogic cluster
              >through firewalls with IP address translation. According to the WebLogic
              >(5.1) documentation, this could be done by opening port 7001 in the
              >firewalls, and BIND WebLogic SERVER INSTANCES TO DNS NAMES. Does anyone
              >know how to bind WebLogic server instances to DNS names? Should it be
              >done in weblogic.properties?Thanks in advance,David [email protected]
              

  • Sticky load balancing not working  because of Address Translation

              This came up before - see below. I don't understand what the
              soltion is/was.
              WL Server puts it's ip address in the WebLogicSession cookie
              which is an internal address 192.168.201.41
              WL proxy knows WL Server only by an external address like 139.141.38.21. Since
              it does not know of any WLS with an IP
              address of 192.168.201.41, it round-robins the request instead
              of sending it to the primary WLS.
              Any help is much appreciated.
              Mike Reiche
              Robert Patrick <[email protected]> wrote:
              >Hi,
              >
              >A very typical configuration is to put the web server in the DMZ (i.e.,
              >between
              >an outer and inner firewall) and proxy the requests from the web server
              >to the
              >WebLogic server (which sits behind the inner firewall). Since all of
              >these
              >proxied requests use HTTP and a single port, the only port that needs
              >to be
              >opened in the inner firewall is an HTTP port (the outer firewall will
              >only need
              >an HTTP and/or HTTPS port opened).
              >
              >Hope this helps,
              >Robert
              >
              >Eytan Ben-Meir wrote:
              >
              >> Thanks Patrick,
              >>
              >> May be you can suggest options for securing a WLS behind a firewall?
              >>
              >> Thanks again,
              >>
              >> Eytan
              >>
              >> Robert Patrick wrote:
              >>
              >> > Hi,
              >> >
              >> > The problem is that we encode location information (e.g., IP address(es))
              >> > in the session id. If the plugin sees a session id, it decodes the
              >> > session id to find out where to route the request (i.e., which server
              >in
              >> > the cluster contains the HttpSession object for that session). Since
              >the
              >> > plugin cannot find the machine whose IP address is encoded in the
              >session
              >> > id (because of the network address translation), this will not work.
              > In
              >> > general, distributed application software needs to be modified to
              >be
              >> > capable of handling network address translation -- to my knowledge,
              >> > WebLogic Server has not been modified to support this feature (though
              >the
              >> > Enterprise version of the product has had this support for years).
              >> >
              >> > Hope this helps,
              >> > Robert
              >> >
              >> > Eytan Ben-Meir wrote:
              >> >
              >> > > Hi,
              >> > >
              >> > > Configuration:
              >> > > WLS 4.5.1 on Solaris 2.7 inside a firewall.
              >> > > SonicWall firewall with NAT (Network Address Translation).
              >> > > Netscape Enterprise Server 4.0 outside the firewall with Weblogic
              >> > > NSAPI-BRIDGE (sp 5)
              >> > >
              >> > > The problem:
              >> > > When a browser request is sent to the NE web-erver (directed to
              >the
              >> > > firewall who then redirects to a Weblogic servlet).
              >> > > IF The servlet creates a httpsession (with or without cookies)
              >the
              >> > > request fails (the firewall blocks a request directed directly
              >at the
              >> > > non-routable ip address of the Weblogic machine inside the firewall.
              >> > > IF on the other hand the servlet does not create a http session,
              >all
              >> > > works fine.??????????
              >> > > Does any body know something about this????
              >> > >
              >> > > Thanks,
              >> > >
              >> > > Eytan
              >
              

              This isn't my problem.
              "Mike Reiche" <[email protected]> wrote:
              >
              >This came up before - see below. I don't understand what the
              >soltion is/was.
              >
              >WL Server puts it's ip address in the WebLogicSession cookie
              > which is an internal address 192.168.201.41
              >
              >WL proxy knows WL Server only by an external address like 139.141.38.21.
              > Since
              >it does not know of any WLS with an IP
              >address of 192.168.201.41, it round-robins the request instead
              >of sending it to the primary WLS.
              >
              >Any help is much appreciated.
              >
              >Mike Reiche
              >
              >Robert Patrick <[email protected]> wrote:
              >>Hi,
              >>
              >>A very typical configuration is to put the web server in the DMZ (i.e.,
              >>between
              >>an outer and inner firewall) and proxy the requests from the web server
              >>to the
              >>WebLogic server (which sits behind the inner firewall). Since all of
              >>these
              >>proxied requests use HTTP and a single port, the only port that needs
              >>to be
              >>opened in the inner firewall is an HTTP port (the outer firewall will
              >>only need
              >>an HTTP and/or HTTPS port opened).
              >>
              >>Hope this helps,
              >>Robert
              >>
              >>Eytan Ben-Meir wrote:
              >>
              >>> Thanks Patrick,
              >>>
              >>> May be you can suggest options for securing a WLS behind a firewall?
              >>>
              >>> Thanks again,
              >>>
              >>> Eytan
              >>>
              >>> Robert Patrick wrote:
              >>>
              >>> > Hi,
              >>> >
              >>> > The problem is that we encode location information (e.g., IP address(es))
              >>> > in the session id. If the plugin sees a session id, it decodes
              >the
              >>> > session id to find out where to route the request (i.e., which server
              >>in
              >>> > the cluster contains the HttpSession object for that session).
              >Since
              >>the
              >>> > plugin cannot find the machine whose IP address is encoded in the
              >>session
              >>> > id (because of the network address translation), this will not work.
              >> In
              >>> > general, distributed application software needs to be modified to
              >>be
              >>> > capable of handling network address translation -- to my knowledge,
              >>> > WebLogic Server has not been modified to support this feature (though
              >>the
              >>> > Enterprise version of the product has had this support for years).
              >>> >
              >>> > Hope this helps,
              >>> > Robert
              >>> >
              >>> > Eytan Ben-Meir wrote:
              >>> >
              >>> > > Hi,
              >>> > >
              >>> > > Configuration:
              >>> > > WLS 4.5.1 on Solaris 2.7 inside a firewall.
              >>> > > SonicWall firewall with NAT (Network Address Translation).
              >>> > > Netscape Enterprise Server 4.0 outside the firewall with Weblogic
              >>> > > NSAPI-BRIDGE (sp 5)
              >>> > >
              >>> > > The problem:
              >>> > > When a browser request is sent to the NE web-erver (directed to
              >>the
              >>> > > firewall who then redirects to a Weblogic servlet).
              >>> > > IF The servlet creates a httpsession (with or without cookies)
              >>the
              >>> > > request fails (the firewall blocks a request directed directly
              >>at the
              >>> > > non-routable ip address of the Weblogic machine inside the firewall.
              >>> > > IF on the other hand the servlet does not create a http session,
              >>all
              >>> > > works fine.??????????
              >>> > > Does any body know something about this????
              >>> > >
              >>> > > Thanks,
              >>> > >
              >>> > > Eytan
              >>
              >
              

  • Tuxedo and Network Address Translation(NAT) at Firewall

    We made a sucessful connection through the firewall without Network Address Translation
    (NAT)on the firewall, from one network to the other and what we found happened
    was that the client machine makes a connection on port 8090 and then sets up a
    successful connection to the server (WSL).The client then very soon afterward
    makes another connection on
    another high-port and everything works (WSH connection).
    Whats not happening with NAT is that the second connection is not being made to
    the firewall. The firewall and the router are not blocking the call. It is just
    not being made.
    Thanking you in advance!!!
    Nathaniel

    Nathaniel,
    Take a look at the WSL -H option at
    http://edocs.bea.com/tuxedo/tux80/atmi/rf540.htm#1534543
    Regards,
    Peter.
    Got a Question? Ask BEA at http://askbea.bea.com
    The views expressed in this posting are solely those of the author, and BEA
    Systems, Inc. does not endorse any of these views.
    BEA Systems, Inc. is not responsible for the accuracy or completeness of
    the
    information provided
    and assumes no duty to correct, expand upon, delete or update any of the
    information contained in this posting.
    Nathaniel Sebolai wrote:
    We made a sucessful connection through the firewall without Network Address Translation
    (NAT)on the firewall, from one network to the other and what we found happened
    was that the client machine makes a connection on port 8090 and then sets up a
    successful connection to the server (WSL).The client then very soon afterward
    makes another connection on
    another high-port and everything works (WSH connection).
    Whats not happening with NAT is that the second connection is not being made to
    the firewall. The firewall and the router are not blocking the call. It is just
    not being made.
    Thanking you in advance!!!
    Nathaniel

  • Kann W530 SLAT (Second Level Address Translation) ?

    Hallo,
    Unterstützt der im W 530 verbaute Prozessor SLAT (Second Level Address Translation)?
    Danke
    Rainer Borchmann
    CEO smarttechnics

    The W530 supports SLAT and will run Hyper-V.

  • GC 11G AND Network Address Translation

    HI,
    I have simple question , Is Network Address Translation supported with GC 11g. I know it is not on 9i.
    thanks.

    I can't find anything on this on the internet. So creating a SR is an option.
    The only note I found was: Agent Fails to Upload Through Load Balancer, Secures Successfully [ID 1149610.1] suggesting you can use NAT.
    Eric

  • Carrier Grade Network Address Translation (CG-NAT)

    Hello,
    I live in the UK.  One of the largest ISPs, BT, has begun trialling carrier grade network address translation (CG-NAT).  In a nutshell, this introduces double NAT - first your broadband router, then the ISP's "router".  This is before the ISP has introduced IPv6.
    I fear it is only a matter of time before my ISP also introduces CG-NAT.  Will/does Skype work in a CG-NAT scenario?  If not, what are my options?
    Kind regards,
    Anwar

    I am new to Oracle VM. The dom0 and domU are set up by someone else. So I don't know the details. In the domU, I can't even ping the 10.244.69.35 address of the dom0.
    # ping 10.244.69.35
    PING 10.244.69.35 (10.244.69.35) 56(84) bytes of data.
    From 192.168.200.50 icmp_seq=2 Destination Host Unreachable
    From 192.168.200.50 icmp_seq=3 Destination Host Unreachable
    From 192.168.200.50 icmp_seq=4 Destination Host Unreachable
    The Cisco switch on the 10.*.*.* network is owned by IT and I can't change anything on it. This is why I try to set up NAT on the dom0. I would appreciate any help so that I can access the 10.*.*.* network from the domU.

  • Static Port Address Translation 8.4

    Hello Experts,
    Is the static Port Address Translation is bidirectional in 8.4 ???
    I have configured static port address translation for the 2 server with same Public IP for the port 80 and 23. The strange thing is when they initiate a connection to the outside world they are allowed access to the internet as they are not included in the Dynamic Port address translation pool.
    object network inside network.
    subnet 192.168.10.0 255.255.255.0
    Can anybody help me.
    Thanks

    Hello Dears
    Packet tracer for the Static port redirection server IP's.
    ciscoasa(config)# sh conn
    1 in use, 1 most used
    TCP outside 1.1.1.1:23 inside 2.2.2.2:28826, idle 0:00:09, bytes 149, flags UIO
    ciscoasa(config)# sh xlate
    2 in use, 3 most used
    Flags: D - DNS, i - dynamic, r - portmap, s - static, I - identity, T - twice
    TCP PAT from inside:2.2.2.2 23-23 to outside:3.3.3.3 23-23
        flags sr idle 2:11:34 timeout 0:00:00
    TCP PAT from inside:10.10.10.1 8080-8080 to outside:3.3.3.3 80-80
        flags sr idle 2:11:34 timeout 0:00:00
    ciscoasa(config)# sh local-host
    Interface management: 0 active, 0 maximum active, 0 denied
    Interface inside: 1 active, 2 maximum active, 0 denied
    local host: <2.2.2.2>,
        TCP flow count/limit = 1/unlimited
        TCP embryonic count to host = 0
        TCP intercept watermark = unlimited
        UDP flow count/limit = 0/unlimited
      Conn:
        TCP outside 1.1.1.1:23 inside 2.2.2.2:28826, idle 0:00:21, bytes 149, flags UIO
    Interface outside: 1 active, 1 maximum active, 0 denied
    local host: <1.1.1.1>,
        TCP flow count/limit = 1/unlimited
        TCP embryonic count to host = 0
        TCP intercept watermark = unlimited
        UDP flow count/limit = 0/unlimited
      Conn:
        TCP outside 1.1.1.1:23 inside 2.2.2.2:28826, idle 0:00:21, bytes 149, flags UIO
    ciscoasa(config)# packet-tracer input inside tcp 2.2.2.2 28826 1.1.1.1 23    
    Phase: 1
    Type: FLOW-LOOKUP
    Subtype:
    Result: ALLOW
    Config:
    Additional Information:
    Found flow with id 15, using existing flow
    Result:
    input-interface: inside
    input-status: up
    input-line-status: up
    Action: allow
    ciscoasa(config)# sh conn
    1 in use, 1 most used
    TCP outside 1.1.1.1:23 inside 10.10.10.1:31862, idle 0:00:18, bytes 149, flags UIO
    ciscoasa(config)# sh xlate
    2 in use, 3 most used
    Flags: D - DNS, i - dynamic, r - portmap, s - static, I - identity, T - twice
    TCP PAT from inside:2.2.2.2 23-23 to outside:3.3.3.3 23-23
        flags sr idle 2:15:10 timeout 0:00:00
    TCP PAT from inside:10.10.10.1 8080-8080 to outside:3.3.3.3 80-80
        flags sr idle 2:15:10 timeout 0:00:00
    ciscoasa(config)# sh local-host
    Interface management: 0 active, 0 maximum active, 0 denied
    Interface inside: 1 active, 2 maximum active, 0 denied
    local host: <10.10.10.1>,
        TCP flow count/limit = 1/unlimited
        TCP embryonic count to host = 0
        TCP intercept watermark = unlimited
        UDP flow count/limit = 0/unlimited
      Conn:
        TCP outside 1.1.1.1:23 inside 10.10.10.1:31862, idle 0:00:36, bytes 149, flags UIO
    Interface outside: 1 active, 1 maximum active, 0 denied
    local host: <1.1.1.1>,
        TCP flow count/limit = 1/unlimited
        TCP embryonic count to host = 0
        TCP intercept watermark = unlimited
        UDP flow count/limit = 0/unlimited
      Conn:
        TCP outside 1.1.1.1:23 inside 10.10.10.1:31862, idle 0:00:36, bytes 149, flags UIO
    ciscoasa(config)# packet-tracer input inside tcp 10.10.10.1 31862 1.1.1.1 23
    Phase: 1
    Type: FLOW-LOOKUP
    Subtype:
    Result: ALLOW
    Config:
    Additional Information:
    Found flow with id 17, using existing flow
    Result:
    input-interface: inside
    input-status: up
    input-line-status: up
    Action: allow
    Thanks

  • RVL200 Port Address Translation

    Hi,
    Does the RVL200 offer Port Address Translation and it so where do I find the feature in the web interface. So far I have only found Port Forwarding and Port Triggering. The RVL200 has got the latest firmware installed (1.1.12.1).
    Thankyou,
    Robin Horn

    The port address translation rule can be configured at Setup>UPnP page. You would have to add a Service that specifies the External port and Internal port. Note that the UPnP checkbox does not need to be checked. (The feature is known as Asymmetric forwarding, as opposed to the regular port forwarding.)

  • Network Address Translation, Automatic Port Forwarding

    Does the Airport Extreme do
    Network Address Translation? Do I have to do something to make NAT functional?
    Does the Airport Extreme automatically forward ports? Or is this something I have to do manually
    sorry if this is discussed already but a Search of Forum did did not yield the information I need.

    Hi Barbara, welcome to the discussion area!
    +Does the Airport Extreme do Network Address Translation?+
    Yes
    +Do I have to do something to make NAT functional?+
    No, if you have the device configured as a router with the Connection Sharing settings set to Share a public IP address so that the AirPort Extreme is handling the chore of assigning IP addresses to connected devices.
    If you have the AirPort Extreme configured as a "bridge", then NAT is handled by the router that is upstream of the AirPort Extreme.
    +Does the Airport Extreme automatically forward ports? Or is this something I have to do manually+
    Port forwarding must be setup manually on the AirPort Extreme using AirPort Utility, the application used to setup the AirPorts.

  • How do I disable Network Address Translator on my macbook?

    I am getting a notice that Back to my Mac will not work because I have more than one device on my network providing NAT (network address translation).  It says to try disabling NAT on one of the devices.  How do you do that?

    Airport Extreme needs to be  in Bridge Mode.
    Here: http://support.apple.com/kb/TS1208

  • Address translation for intranet access

    Hi,
    We are using iviews created using in SAP Web Dynpto iView template in SAP Enterprise Portal 7.0.
    Resently, we have migarated server from 32 bit machine to 64 bit machine.
    After migration We are facing some problem with web dynpro applications.
    Web Dynpro applications can be opened from internet but not from intranet.
    We want that applications can be accessed from intranet as well as internet.
    Address of Web AS specified in system used by web dynpro applications is in the form <proxy hostname>.<domain>.<extension>:<port-SSL> like xyz.company.net:SSL-Port-Number.
    Can we define translation rule on WebApplication server for converting address to actual address in the form <server host>.<domain>.<extension>:<port>?
    Need your help.
    Thanks,
    Apurva

    Hi ,
    It looks like ,configuration to be on DNS server to point to the correct URL.
    Please check with your network team. It is mapping of two URLs.

  • Envelope to address translation problem?

    Hi,
    Using exchange server 2003 SP1, sending mail through smarthost Sun Java System Messaging Server 6.1 HotFix 0.06 (built Nov 11 2004)
    I think i should actually post this on some exchange server forum but i'm not sure.
    Suddenly when people from their outlook environment send a email to a custom recipient which is in the GAL, the MTA receives a message like this:
    Transport layer information:
    Envelope From: address: [email protected]
    Envelope To: addresses: IMCEAex-O=KLUWER+20ACADEMIC+20PUBLISHERSOU=DOMAIN_CN=RECIPIENTS_CN=[email protected]
    Date: Thu, 21 Jul 2005 07:47:40 +0200
    From: "Kammen, van, Marco, Springer NL" <[email protected]>
    Subject: my message
    To: " ([email protected])"
    <IMCEAEX-O=KLUWER+20ACADEMIC+20PUBLISHERSOU=DOMAIN_CN=RECIPIENTS_CN=[email protected]>
    Message-id: <[email protected]>
    Channel: conversion
    From To Size Queued since
    18 Marco.vanKammen@springer-s IMCEAex-_O=KLUWER+20ACADE    20 21 Jul 05 07:51
    Instaid of the MTA using the correct address which is shown in the header between ()'s it uses a strange UTF-8? Formatted address which can't be resolved by the MTA thus leaving it in the conversions channel.
    Anyone have a clue what to do about this... either on the exchange side or the messenger side??
    Best Regards,
    Marco.

    Well, um, no.
    Mail servers use the envelope address. We don't look at the header "TO" if there's an envelope address. That's what the envelope address is for.
    Consider a message that's been "BCC". There is no header "TO" address to look at, just the envelope address.
    If the envelope address is messed up, we're stuck.

  • ASA 5510 Network address translation through an internal network.

    Is it possible to perform static Nat's through an internal network?
    Here's my situation I have a ASA 5510 with a public outside interface (let’s call it 68.68.68.1), and I have an inside private IP address (192.168.1.2/24). The inside IP address leads to a 4900m with that interface being configured with a 192.168.1.1 (no switching). On the 4900 M I have several VLANs one of them is an internal DMZ of sorts. (192.168.2.0/24). Within this DMZ network are several Web servers which need to be associated a public IP address (68.68.68.x).
    Every time I configure a static Nat to associating a public IP address with an internal IP address within the DMZ, packet Tracer on the ASA informs me that the packet gets dropped at the static Nat and I cannot figure out why this is so.
    Safe it to say my question still stands is it possible to Nat (68.68.68.222 to and 92.168.2.60) given the configuration above, and how would I go about configuring in such the manner above so that I acn apply static nat through the 192.168.1.0 network to reach the 192.168.2.0 network.
    Any help on this matter is greatly appreciated. Thank you.

    more information  as requested
    csc# sh int ip br
    Interface                  IP-Address      OK? Method Status                Protocol
    Ethernet0/0                192.168.1.2   YES CONFIG up                    up
    Ethernet0/1                172.16.2.3      YES CONFIG up                    up
    Ethernet0/2                192.168.12.1    YES CONFIG up                    up
    Ethernet0/3                68.68.68.1   YES CONFIG up                    up
    Internal-Control0/0        127.0.1.1       YES unset  up                    up
    Internal-Data0/0           unassigned      YES unset  up                    up
    Management0/0              192.168.19.1    YES manual administratively down down
    csc-ssm# sh nameif
    Interface                Name                     Security
    Ethernet0/0              inside                   100
    Ethernet0/1              %^&*%$                   100
    Ethernet0/2              @#$%&*()                  30
    Ethernet0/3              outside                    0
    Management0/0            management               100
    nat (inside) 0 access-list nat0
    nat (inside) 1 serverNET 255.255.255.0
    nat (inside) 1 Server 255.255.255.0
    nat (inside) 1 192.168.8.0 255.255.255.0
    nat (inside) 1 CorpVPN 255.255.255.0
    nat (inside) 1 192.168.30.0 255.255.255.0
    nat (Eng) 0 access-list ENG_nat0_outbound
    nat (Eng) 1 172.16.2.0 255.255.255.0
    nat (WiFi-Guest) 1 192.168.12.0 255.255.255.0
    global (ENG) 2 172.16.2.10-172.16.2.50 netmask 255.255.255.0
    global (outside) 1 interface

Maybe you are looking for