Avatar of Bert2005
Bert2005Flag for United States of America

asked on 

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.
Microsoft Server OSRemote AccessRouters

Avatar of undefined
Last Comment
Bert2005
ASKER CERTIFIED SOLUTION
Avatar of N-W
N-W
Flag of Australia image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of Bert2005
Bert2005
Flag of United States of America image

ASKER

Thanks. That answers all the questions. So, it would be silly, given all the security issues with port 3389 (even though you can change it), and the time necessary to configure your router for all clients) one would be rather dumb to not use the RD Gateway.

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 as the RD Gateway can use DNS? Of course, RDC or RDP (they almost seem interchangeable, although I think RDC is perferred now), must be configured correctly with the FQDN of the server.-

This should be all I need.
SOLUTION
Avatar of N-W
N-W
Flag of Australia image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of Bert2005
Bert2005
Flag of United States of America image

ASKER

Thanks N-W. I appreciate your help.
Avatar of Bert2005
Bert2005
Flag of United States of America image

ASKER

N-W,

May I ask you one more question? Sorry.
Avatar of N-W
N-W
Flag of Australia image

Sure, go ahead.
Avatar of Bert2005
Bert2005
Flag of United States of America image

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?
Avatar of Bert2005
Bert2005
Flag of United States of America image

ASKER

Or  did I set up a number for a particular computer which was associated 3389 in the Cisco PIX?
Avatar of N-W
N-W
Flag of Australia image

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.
Avatar of Bert2005
Bert2005
Flag of United States of America image

ASKER

Thanks. It all comes back. :-)
Microsoft Server OS
Microsoft Server OS

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

59K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo