RDC with Server 2008, 2011 and 2012
Hi experts,
I know that in Servers 2003 such as SBS 2003, in order to use RDP, you had to open port 3389 on the router. I believe with port forwarding, the remote user could access the computer with the suffix 3389. If you wanted to access another computer with 3390, could you use the same static public static IP?
In the scenario of using port 3389, when the remote connection was made, did it go from the router to the client and skip the server?
In servers 2008 above, there is no longer a need to open port 3389 (a good thing), as the server now runs Remote Desktop Management and all requests including RWA go through there. I am not sure if it is now called Remote Desktop Server Services or RDSS.
My major question is if you still have 3389 open and port forwarding to the client computer would that take the remote user to the specific client so that it would not actually use the server and Remote Desktop Services?
Thanks.
Bert
PS If there are two many different questions, I would be more than happy to split them. It just seems as though they kind of go together. Thanks.
I know that in Servers 2003 such as SBS 2003, in order to use RDP, you had to open port 3389 on the router. I believe with port forwarding, the remote user could access the computer with the suffix 3389. If you wanted to access another computer with 3390, could you use the same static public static IP?
In the scenario of using port 3389, when the remote connection was made, did it go from the router to the client and skip the server?
In servers 2008 above, there is no longer a need to open port 3389 (a good thing), as the server now runs Remote Desktop Management and all requests including RWA go through there. I am not sure if it is now called Remote Desktop Server Services or RDSS.
My major question is if you still have 3389 open and port forwarding to the client computer would that take the remote user to the specific client so that it would not actually use the server and Remote Desktop Services?
Thanks.
Bert
PS If there are two many different questions, I would be more than happy to split them. It just seems as though they kind of go together. Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks N-W. I appreciate your help.
ASKER
N-W,
May I ask you one more question? Sorry.
May I ask you one more question? Sorry.
Sure, go ahead.
ASKER
I use RDC and Remote Gateway so no problem, but I am curious since 2003 was three to four years ago for me.
When I had 3389 port forwarded to say Computer A and 3390 to Computer B and so on, how did I access them? I knew the public IP, say 72.xx.xxx.99. Did I write something like this in the browser: https://72.xx.xxx.99:3390 to get to Computer B?
When I had 3389 port forwarded to say Computer A and 3390 to Computer B and so on, how did I access them? I knew the public IP, say 72.xx.xxx.99. Did I write something like this in the browser: https://72.xx.xxx.99:3390 to get to Computer B?
ASKER
Or did I set up a number for a particular computer which was associated 3389 in the Cisco PIX?
In your RDC client, for the computer name you would put in "72.xx.xxx.99:3390".
For port 3389, just enter the IP address as it knows 3389 is the default port.
For port 3389, just enter the IP address as it knows 3389 is the default port.
ASKER
Thanks. It all comes back. :-)
ASKER
This also allows you to connect to all machines (if you have permissions) from home simply using the name of the computer and the domain such as computer_name.domain.local
This should be all I need.