Question about Windows remote desktop

[nastyboy]

thanks, but the problem is not due to having a dynamic IP, because it is fixed, it comes because with a single IP and a program that seems to have a fixed port, how can I distinguish between machines?

[cobito]

@nastyboy:

Hello
I have a mini-server behind a router, with a fixed public IP

I have my PC and router configured so that I can access it from outside my network with Remote desktop. Now I would like to access more than one computer from this network indistinctly.
The program uses a particular port, hence the doubt I am raising.
With a fixed public IP, I want to access via remote desktop more than one machine on the same network. The program uses a fixed port, I think it's 3389. How do I tell the router when I 'call' it that I want to access one machine or another?
Can I specify a port other than 3389 and have Remote desktop assume it?

regards

If I have understood correctly, the problem is that you have more than one PC with terminal server that you want to access from outside. If so, I don't know how to change the port, but in all the routers I know, when doing NAT, it asks for both a public and an internal port. You just have to vary the public port while keeping the internal one at 3389. Obviously, each internal port 3389 will be directed to a different local IP.

[nastyboy]

Hello
thanks for the reply, but
does Remote desktop accept ports other than 3389? If I call with this program that already has this port by default, I would have to be able to change it to be able to specify a public port previously specified in 'NAT-Virtual servers' of my router

[cobito]

@nastyboy:

Hello
thanks for the reply, but
does Remote desktop accept ports other than 3389? If I call with this program that already has this port by default, I would have to be able to change it to be able to specify a public port previously specified in 'NAT-Virtual servers' of my router

Let me show you what comes up on my router (and on all the ones I've seen so far):

There you can see several fields where they put "External port" and "Internal port". In internal port you put the 3389 and write the local IP address where the server is. Then in external port you can put any other port, such as 3388. When you access from outside using port 3388, the router will communicate with the machine that has the IP and port 3389.

In other words, the router translates port 3388 to 3389.

PD: What router do you have?

[incrediboy]

not all routers allow that cobito, which is why I recommended using that website.

I did not recommend it because the ip is static or dynamic, I said it because with that method, having a unique external ip, you can have a different domain name for each computer accessible from the outside.

[nastyboy]

that photo reminds me of my router
I understand that, maybe it's because I didn't understand how the software works well.

The listener has port 3389l, and the caller can use any port, just configure it in that window.
I think I have it clear, I will try

thanks

[cobito]

@incrediboy:

not all routers allow that cobito, that's why I recommended using that website.

I didn't recommend it because the ip is static or dynamic, I said it because with that method having a unique external ip you can have a different domain name for each computer accessible from the outside.

The problem is not the IP. If I have understood the problem correctly, what nastyboy wants is to have access to several servers that within the local network have the same port. For example, they could be two PCs with remote desktop and he wants to be able to access any of them from the outside. To do that, it is necessary to assign a port to each service because in the end you are accessing two PCs with two different local IPs from a single public IP.

Imagine that you have two web servers on your local network and you want to access each of them separately. From within the local network it is very easy: you just have to put the local IP of each of the servers and you will be able to access each of them separately, but what happens if you want to access from outside? How do you access each machine on the local network separately if you only have one public IP? Well, for example, by making one of the web servers use port 80 and the other port 81.

@nastyboy:

that picture reminds me of my router
I understand that, maybe I didn't understand how the software works well.

The one who listens has port 3389l, and the one who calls can use any port, just configure it in that window.
I think I have it clear, I will try

thanks

Exactly.

[incrediboy]

@cobito:

The problem is not the IP. If I understand the problem correctly, what nastyboy wants is to have access to several servers that within the local network have the same port. For example, they could be two PCs with remote desktop and he wants to be able to access any of them from the outside. To do that, it is necessary to assign a port to each service because in the end you are accessing two PCs with two different local IPs from a single public IP.

Imagine that you have two web servers on your local network and you want to access each of them separately. From within the local network it is very easy: you just have to put the local IP of each of the servers and you will be able to access each of them separately, but what happens if you want to access from outside? How do you access each machine in the local network separately if you only have one public IP? Well, for example, by making one of the web servers use port 80 and the other use port 81.

with what I said it is very easy… www.serv idor1.com:80 and www.serv idor2.com:80

the software I put above assigns domain names to a pc and not to an external ip, I don't know where you see the problem.

[nastyboy]

the question is whether from outside my network, and using remote desktop, I could write in its connection window:

public IP –> I connect to machine 1 (private IP_1) in my network (by default, since I do not indicate anything, port 3389, CONFIGURED IN THE ROUTER to associate external 3389 with internal 3389 of private IP_1)

public IP:3390 --> I connect to machine 2 (private IP_2) in my network (port 3390, indicated explicitly and CONFIGURED IN THE ROUTER to associate external 3390 with internal 3389 of private IP_2)

In other words, I want to know if that Remote desktop program can be forced to connect through ports other than 3389

thanks to both of you, the debate is always healthy

[incrediboy]

as cobito has said, we would need to know your router to know if it can be done

[chispis]

Apparently, it can be done from the registry, http://julianrv.com/blog/2005/11/cambiar-el-puerto-de-terminal-services-y-remote-desktop.html