<div>
<div class="content wysiwyg-content">
I currently have a 2012 R2 server confgured to deploy apps using RDWEB. &nbsp;Apps are published and working both internally and externally. &nbsp;I have purchased and installed an SSL cert. from GoDaddy as well.<br />
<br />
We are using split-brain DNS... Internal domain ends in .LOCAL and external domain ends in .COM.<br />
<br />
When accessing the RDWEB page all is well... &nbsp;The site uses the external name and SSL cert properly.<br />
<br />
The issue is once logged into the site, and I launch an app I get the following dialogue box in attachment 1. &nbsp;Then I get prompted for Username and Password, and then I get the dialogue box pop up in attachment 2.<br />
<br />
If you notice the external name is there on attachment 1, and the internal name is there on attachment 2.....<br />
<br />
External: apps.xxx.com<br />
Internal: rds1.xxx.local<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2014/10_w42/877402/SHOT1.PNG" target="_blank" title="ATTACHMENT 1 (168 KB)"><img alt="ATTACHMENT 1" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2014/10_w42/800_877402/SHOT1.PNG" /></a><br />
<a href="https://filedb.experts-exchange.com/incoming/2014/10_w42/877403/SHOT2.PNG" target="_blank" title="ATTACHMENT 2 (200 KB)"><img alt="ATTACHMENT 2" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2014/10_w42/800_877403/SHOT2.PNG" /></a><br />
So the 2 questions are:<br />
<br />
How can I get rid of the 2 dialogue boxes referring to SSL?<br />
<br />
Why is it prompting me for Username and password when I launch an app AFTER I already successfully logged into the site?
</div>
</div>


SHOT1.PNG

SHOT2.PNG

I currently have a 2012 R2 server confgured to deploy apps using RDWEB.  Apps are published and working both internally and externally.  I have purchased and installed an SSL cert. from GoDaddy as well.

We are using split-brain DNS... Internal domain ends in .LOCAL and external domain ends in .COM.

When accessing the RDWEB page all is well...  The site uses the external name and SSL cert properly.

The issue is once logged into the site, and I launch an app I get the following dialogue box in attachment 1.  Then I get prompted for Username and Password, and then I get the dialogue box pop up in attachment 2.

If you notice the external name is there on attachment 1, and the internal name is there on attachment 2.....

External: apps.xxx.com
Internal: rds1.xxx.local





So the 2 questions are:

How can I get rid of the 2 dialogue boxes referring to SSL?

Why is it prompting me for Username and password when I launch an app AFTER I already successfully logged into the site?

Server 2012 R2 RDWEB SSL Issue

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

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

HTTPS is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security (TLS) or its predecessor, Secure Sockets Layer (SSL). The main motivation for HTTPS is authentication of the visited website and to protect the privacy and integrity of the exchanged data. HTTPS is widely used for protecting page authenticity on all types of websites, securing accounts and keeping user communications, identity and web browsing private.