|First, before you can configure a static IP on your router's WAN side, you have to be sure you get one from your ISP. If the internet package you're paying for from your provider does include static TCP/IP settings you'll know because they'll give you the following info: IP Address, Subnet Mask, Default Gateway, DNS.|
Now, if you don't have that information you can't just make up an IP and use it because you'll probably pick one that's already in use and cause a duplicate IP error.
This is something both Picohat and I have tried to get across to you which you don't seem to understand. So think about this and figure it out or we're all wasting our time.........Do you have a static IP as provided to you by your ISP?
Typically most (if not all) ISP's provide a basic "Dynamic IP" package for home use. One has to ask for a Static IP package and they cost more money.
Please note, I am not talking about statically assigning an IP to your computer. Instead we are talking about your external (internet) IP address as provided by your ISP which would be assigned to the WAN port of your router.
Now, having said the above I'm going to try to explain this to you one last time.
On the LAN side of your SOHO router you should be using DHCP and your computer should be set to "obtain an IP address automatically" This is DHCP. Assuming you have the DHCP server setup correctly on the router and the router's LAN IP is: 192.168.0.1
Your client should receive something like the following when it boots up:
Default Gateway: 192.168.0.1
The important part is that the DG and DNS both point at the router. The DG has to be the LAN IP of the router or traffic from your PC will never get out on the internet as the router is the gateway to the internet. As for the DNS, the router will handle passing DNS info to external DNS servers as necessary when it is properly configured.
The router's LAN port is either DHCP or static depending on which package you're getting from your provider.....Static or Dynamic
Again, I have to stress, you need to confirm which you are getting from your provider.....a Static IP package or a Dynamic package and set the WAN side of your router up accordingly
Once you have the router and it's internet connection working correctly then and only then can you configure the port forward.
The image you show of your "triggering" does not show an internal "destination" IP address. I'm familiar with setting up a port forward, not a trigger so I'm not sure how the "trigger" works. But I can tell you this much, a port forward looks exactly the same with one exception, you have a desination IP address. You need to look through the guide for your router and if need be, it's help files and figure out how to correctly "forward" a port. I don't think triggering will do it since the client waiting for a connection on 3389 does not "listen" on the network for traffic on that particular port. It waits for a connection on that particular port..........ergo you need to forward port 3389 to the IP address of the client you wish connect to.
It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.