Programs like teamviewer8/8/2023 ![]() ![]() ![]() For example you'd make a service called "RDP for Marty" with protocol TCP and port 4389. You can also do it with a FQDN like :5389Īlso you may have to create custom services in your firewall for all of the computers. Note that Jim gets no colon and port number after the public IP because he is at the default port outside and inside. To connect to Jim from the internet side you would put the following in the Computer Name of the terminal services client: 75.123.75.23 :5389 To connect to Marty from the internet side you would put the following in the Computer Name of the terminal services client: 75.123.75.23 :4389 To connect to Jim from the internet side you would put the following in the Computer Name of the terminal services client: 75.123.75.23 Also remembering which port goes where is a pain. I believe this is called port redirection.ĭownside of doing one port forward for each workstation is doing one port forward for each workstation, which could be a lot of port forwards depending on the number of computers you have. Notice the public port changes but the private internal port on the workstation does not. Our workstations are JIm at 192.168.1.3, Marty at. Our public IP will be 75.123.75.23 and our private range of IPs is a Class C at 192.168.1.x. Lets do 3 workstations for example and assume each one has a static private or internal IP. Two, you need to to forward different ports on the public IP to the same RDP port (3389) on each internal workstation IP. You can't have Jim's computer pick up Jane's IP one day and then pick up Marty's IP another day, or even a new IP. Assign them manually, or do DHCP reservations. One, make sure each workstation has a static internal IP. To port forward a single public IP to multiple internal private IPs, You'd need to do two things. Then there are two ways to access them RDP to a internal server and then (pivot) RDP from that server to the workstations, or, do a custom port forward to each workstation and directly RDP to each workstation from outside which can be a pain. This I believe also takes care of local windows firewall rules. You can set the workstations to accept connections from any version of the RDP client to make it easy for now and restrict later. Leave the workstations alone and just enable RDP on them. Does anyone know of any options?Īs for getting RDP working for multiple workstations behind a firewall with a single public IP, don't bother with messy registry settings. We open ports for RDP so this would not be a security issue. I can open a firewall port for a box that works as a proxy if there is an open source solution. ![]() ![]() Are there any non-administrator open source options that I can set up on my network internally? (by non-admin, I mean a client to workstation software that the client/employee, who only needs access to do work on their office workstation, can have up and running in a matter of seconds, without any administrator options, in their road warrior style client software) I know you need a computer acting, I would assume as a proxy, which is what teamviewer is supplying, so that you can connect through the firewall just by having the listener software installed on the remote system. So I would like to have a teamviewer type option but without the unbelievably high cost associated with it. I am finding after extensive troubleshooting right down to regedit, opening ports in the firewall, update un-installs, netstat, and more, that getting some computers working with RDP is pretty much impossible. When Windows Remote Desktop works it is a very nice solution, but for me it doesn't work for 50% of the computers in our domain. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |