<div>
It makes sense. &nbsp;I did the same a couple of years ago. &nbsp;Same names, same IP addresses. &nbsp;Worked fine.
</div>


It makes sense.  I did the same a couple of years ago.  Same names, same IP addresses.  Worked fine.

<div>
<div class="content wysiwyg-content">
Do I need to configure a Gateway Role if I am only having users connect to the farm from within the network? &nbsp;We don't access the Farm from outside only internally. &nbsp;The reason I ask is that it seems I am having issues connecting to the servers themselves when using RDP. &nbsp;I have no HA and only 2 Host servers and the Connection Broker and have setup a RR NLB setup. &nbsp;I have an existing 2003 TS environment and I have built the new 2012 Farm but don't want to confuse the end user with new names. &nbsp;I plan on when going to production with the new system pointing the name they use now to the new servers. &nbsp;Say Corp1 is what they are using, I want it to point to the new system. &nbsp;I am guessing smoking the test farm collection and creating a new one with said old name as the new FARM name on 2012. &nbsp;Does that make sense?
</div>
</div>


Do I need to configure a Gateway Role if I am only having users connect to the farm from within the network?  We don't access the Farm from outside only internally.  The reason I ask is that it seems I am having issues connecting to the servers themselves when using RDP.  I have no HA and only 2 Host servers and the Connection Broker and have setup a RR NLB setup.  I have an existing 2003 TS environment and I have built the new 2012 Farm but don't want to confuse the end user with new names.  I plan on when going to production with the new system pointing the name they use now to the new servers.  Say Corp1 is what they are using, I want it to point to the new system.  I am guessing smoking the test farm collection and creating a new one with said old name as the new FARM name on 2012.  Does that make sense?

2012 RDS Gateway

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Remote access may refer to the connection to a data-processing system from a remote location, for example through a virtual private network remote desktop software, terminal emulation, or the activation of features of a business telephone system from outside the business's premises.