There are other options.
What you need to do is to declare for both ends what the forwarding port (what MS calls a service port) will be for each computer.
The issue is NAT. You need to explain to the Linksys router that traffic over a certain port on your public interface (WAN-side IP) should be redirected to workstation X on your LAN side.
I am not sure why mijbianco15 insists this can only be done with VPN, perhaps there are restrictions by his ISP that most do not face as a common issue.
I will give you the links to the MS and other support for explaining the process, but in a nutshell:
1. It helps to have the underlying client software installed, including helper applications. For NAT traversal Microsoft expects that you will have installed on the client side:
. DirectX 9.0b (This oddly has a lot to do with NAT)
. The Discovery Client and the uPnP Client : Control Panel, Add/Remove Programs, Add/Removing Windows Compnenents, Networking, check the first and last box and Apply.
Now on the Router you need to Port Forward to the LAN side IPs the addresses that the client expects to be open.
Make a list by IP. Using static IPs for the clients simplifies matters. Just understand that a remote sesssion on your Public IP means little; which workstation? with what priviliges?
You plan ahead of time to use forwarded port assingments through your Router to resolve this confusion.
Port 1792: someone wants to connect to fbmeans
Port 1793: someone wants to talk to bjbianco
Port 1794: someone is trying to connect to bcastner
..etc...
See the following for the assignments
Most of what you may need to know is here:
And certainly can be found here: