<div>
Make sure you've enabled forwarding 3389 for both TCP and UDP.
</div>


<div>
Using SonicWALL Terminal Service definition. &nbsp;Regrettably, it includes TCP and UDP. &nbsp;I wish it had been that easy!
</div>


<div>
you say that you have redirected RDP from the Static external IP address of the new server to the internal address of the new server - does that mean that you have multiple external IP addresses? &nbsp; that would be unusual (but not impossible).<br />
<br />
can you still RDP to the original server?<br />
<br />
I would usually use port forwarding and use a non-standard port and forward to the RDP port on the various servers<br />
<br />
for example, forward TCP and UDP port 10000 to server 1, port 3389. &nbsp; &nbsp;forward 10009 to server 2, port 3389<br />
<br />
that way, you are always using the same IP address/dns name to connect to your network - and you simply enter the port number in the connection settings &nbsp; (myexternaldomain.com:1000<wbr />0 &nbsp;or myexternaldoamin:10009)
</div>


<div>
Actually, I do have multiple external IP addresses. &nbsp;The additional server is for a LOB app that required an exclusive server and I had a spare external IP address to use for it. &nbsp;When trying to isolate the issue, I have tested the process to internal workstation IPs which worked, but not to this Server.....Yes, I did hit the checkbox to allow access to this server!<br />
<br />
Tom
</div>


<div>
Did you use the Wizard or do things manually?
</div>


<div>
I will assume that you have the correct default gateway settings on the new server.<br />
<br />
two things to test<br />
<br />
1 - try setting up the 2nd external IP address to access the original server (as you know that should work) - although you say you have tested to a workstation IP, so that should actually work<br />
2 - try forwarding the original external IP address to the new server (or better, forward a different port on the original IP to 3389 on the new server)
</div>


<div>
we've all been there - generally after a 14 hour day, when this absolutely must work right now.......................<wbr />..........<wbr />.. &nbsp; :)
</div>


<div>
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.<br />
<br />
I have recommended this question be closed as follows:<br />
<br />
Accept: Wings1 (<a href="https:#a42431618" rel="ugc">https:#a42431618</a>)<br />
<br />
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.<br />
<br />
seth2740<br />
Experts-Exchange Cleanup Volunteer
</div>


<div>
Seth,<br />
<br />
I had accepted a solution and thought the issue had been closed. &nbsp;Not sure how to do that from here, but if you need to close it, please do.<br />
<br />
Tom
</div>


<div>
<div class="content wysiwyg-content">
I have an SBS 2008 Domain. &nbsp;I have added an additional server. &nbsp;Internally, I can access the new server via RDC. &nbsp;When attempting to access the new server from outside the network it will not connect. &nbsp;In my firewall/router I have redirected terminal services pointing to the public static IP address of the new server to the private IP address of the server and kept the 3389 port (for now). &nbsp;Will not connect.<br />
<br />
What am I missing????
</div>
</div>


I have an SBS 2008 Domain.  I have added an additional server.  Internally, I can access the new server via RDC.  When attempting to access the new server from outside the network it will not connect.  In my firewall/router I have redirected terminal services pointing to the public static IP address of the new server to the private IP address of the server and kept the 3389 port (for now).  Will not connect.

What am I missing????

External Remote Access to Server 2012

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.

Remote Access

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.

Hardware Firewalls

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.