Whenever you change the listening port for RDP from 3389 you have to configure a new windows firewall rule on the machine where you changed it for RDP because it defaults to 3389 and I don't believe it is editable so you add a new one to include you new port.
Just call your new inbound rules RDP (you'll probably need two, one for TCP and a second for UDP) and use the two existing "Remote Desktop" inbound rules as examples for configuration. Just make sure that you use the new listening port in your configuration.
EDIT: And then of course in your connection you'll have to use :8888 (port number) in mstsc.exe for your connection to work
ie: YourExternalStaticIPAdress:8888
Yes.... typically when you remote into a remote desktop host on an internal (privately addressed) non-public facing network, from a remote desktop client that is not part of the same private network, you have to hit the outside edge, where you've configured your pinhole (port forwarding) to send things along to the internal (LAN side) network, and then to a specific host based on the listening port.Would the external static IP address be the static IP provided by Charter that was assigned to the router?
Yes.... typically when you remote into a remote desktop host on an internal (privately addressed) non-public facing network, from a remote desktop client that is not part of the same private network, you have to hit the outside edge, where you've configured your pinhole (port forwarding) to send things along to the internal (LAN side) network, and then to a specific host based on the listening port.
You can use a FQDN if your provider has one associated with that IP or some people use Dynamic DNS services like DynDNS.org which can be helpful if that IP is subject to change but it your case not necessary.
And are you certain that you haven't configured a port for listening that is otherwise engaged on either or both machines. There are ports that are reserved which you need to avoid.
I generally use 8886, 8887, 8888, 8889. They seem to just work and haven't caused me any issues to date.
Not sure.... let me fire mine up and test.Is there a feature on the Windows Server 2012 R2 that I need to set up?
Not sure.... let me fire mine up and test.
You may want to first get this working with default settings on the internal network first as everything should be provided for in advance by the operating system and Windows with configure the firewall rules for you with everything set to 3389.
After you confirm that it is working as expected with default settings on the internal network, then advance one step at a time.
Change the listening port and see what happens, making sure you include the colon and the new port number in your connection (10.1.10.222:8886 ).
If the problem starts there then it's the firewall that you'll need to fix.
Once that is up and running you can test it from an external network, hitting the outside edge IP address including the listening port and see if your NAT pinhole passes it through as expected.
Did you reboot the machines after changing the registry entry?
That particular registry edit requires a reboot to take effect.
Is one of the machines you're trying to connect to a 2012 R2 Server and if so is it a Domain Controller?
Not sure.... let me fire mine up and test.
You may want to first get this working with default settings on the internal network first as everything should be provided for in advance by the operating system and Windows with configure the firewall rules for you with everything set to 3389.
After you confirm that it is working as expected with default settings on the internal network, then advance one step at a time.
Change the listening port and see what happens, making sure you include the colon and the new port number in your connection (10.1.10.222:8886 ).
If the problem starts there then it's the firewall that you'll need to fix.
Once that is up and running you can test it from an external network, hitting the outside edge IP address including the listening port and see if your NAT pinhole passes it through as expected.
So it, worked when I changed all the information back to default and rebooted. Then when I changed the listener to 8888 and rebooted I tried to connect with the 10.1.10.x:8888 and it didn't work. So its a fire wall issue? I have both fire walls turned off though.
OK, so now turn the firewalls back on.
I would think so and I believe that, that is the list I used to use. I see my old favorites have been claimed since I last looked (been awhile).would it be safe to assume that if the ports are not listed they are unused?