Rerouting outside IP to local 192 address using static route

Confusedit;

Is there specific TCP/IP ports that you want to do this for????

You can do a nat translation as follows

ip nat inside source static tcp 192.168.1.x 80 interface ethernet 0 80  

Where your outside address is on ethernet 0 and the port you want to translate is 80....

you can try this

ip nat inside source static 192.168.1.x interface ethernet0  

This will statically map all inbound requests to the internal address of 192.168.1.x but may also cause some undesirable effects....

What does your current configuration look like?  
How many IP addresses do you have?
And what are you trying to accomplish?

Thanks
Scott

Sounds like you need to use NAT. Have a read of this doc:

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080094e77.shtml

and see if it helps. Does this router currently connect you to the Internet ? If so, then it probably already has NAT setup for outbound translation. If thats the case, the config might look something like this:

============
interface ethernet0
 ip address w.x.y.z   (Internet IP address of router)
 ip nat outside

interface fastethernet0
 ip address 192.x.y.z (internal IP address)
 ip nat inside

ip nat inside source list 1 interface ethernet 0 overload

access-list 1 permit 192.x.y.z 0.0.0.255
============

To which you'll need to add:

ip nat inside source static tcp 192.x.y.z 80 w.x.y.z 80

Which would allow users on the Internet to access a web server on the IP w.x.y.z which would get translated to the internal IP 192.x.y.z

OK it seems I did bad wording the question in such a hurry.  I already have NAT translations that work for people trying to access my servers from outside my network.  Here is the setup basically....

ip nat inside source static tcp 192.x.x.5 80 22.x.x.16 80 extendable
ip nat inside source static tcp 192.x.x.5 25 22.x.x.16 25 extendable
ip nat inside source static tcp 192.x.x.5 110 22.x.x.16 110 extendable                                                  
ip nat inside source static tcp 192.x.x.4 21 22.x.x.15 21 extendable
ip nat inside source static tcp 192.x.x.4 80 22.x.x.15 80 extendable

Now let me explain my situation a little better.  My LAN IPs start with 192 of course and my assigned static ip's would be 22.x.x.15 and 22.x.x.16

Now it translates fine if someone is outside the network and accessing the .15 or .16 adress
It also translates fine if from inside the network I access the 192.x.x.4 or 192.x.x.5 adresses

It doesn't however work from inside the network trying to access the 22.x.x.15 or .16
For example 192.x.x.4 aka 22.x.x.15 is my webserver.
If I type 192.x.x.4 while on the LAN it works
If I type 22.x.x.15 while outside the LAN it works
If I type 22.x.x.15 from inside the LAN it will not resolve the webpage

I hope this is clear enough because it seems like there was some confusion from the above responses.  I do appreciate your help guys.

scotty is right. What you are trying to do simply does not work on a Cisco router, and you'll never get it to work. The packets must actually traverse the interfaces to hit the nat rule.
The NAT translation only works as an outside packet comes in through the outside interface - then it gets forwarded to the proper inside host.
A packet sourced from the inside LAN would have to actually go out of the router, hit another router to be turned back around and come back in the outside interface.

I've worked with Cisco TAC trying to find a workaround. There is an article on CCO that explains "nat on a stick" that looked promising using a loopback as an interface, but still does not work, and is not supported by TAC.

The PIX has a capability to do just what you want with the "alias" command, but there is simply no equivalent in router IOS.

I realized after posting this it would just be easier to add local record to my local DNS.  I'm not sure about how exactly split zones should work.  Thanks for the help guys.