Windows Server 2012
--
Questions
--
Followers
Top Experts
RDweb 'Connect to a Remote PC' only appears on 2012 R2 server locally
Hello,
I have been in and out of forums checking on most queries for this, but in my particular instance, not many have solved this issue that I suspect might have something to do with the FQDN relationship between certificate and host server being .local vs .com.
When I browse externally to URL https://remote.server.com I can log in (with either a standard user or admin) and I am presented with 'RemoteApps', however, when I log in on the local server (as admin or standard user) I am presented with 'RemoteApps' along with 'Connect to a Remote PC'; which is exactly what I want to see when I log in externally from any client.
So, to add some insight into what I can confirm:
TCP Port 3389 &Â 443 are open.
I am using Internet Explorer (after reading about the ActiveX trap)
IIS show desktops is set to TRUE
Tested with Firewall OFF, Tested with AntiVirus OFF
My server has a hostname of DC-FS01
My SSL certificate has an FQDN of remote.server.com however, internally my hostname looks like DC-FS01.server.local
I have a Forward Zone called remote.server.com that points to the internal server / DNS server IP address, and can ping remote.server.com internally.
I read somewhere that I should be able to ping remote.server.com and get a response, this does not happen in my instance, but I find that strange if I am meant to be able to achieve this when I am going through a browser.
Any insight or advice into this would be much appreciated.
Thanks
I have been in and out of forums checking on most queries for this, but in my particular instance, not many have solved this issue that I suspect might have something to do with the FQDN relationship between certificate and host server being .local vs .com.
When I browse externally to URL https://remote.server.com I can log in (with either a standard user or admin) and I am presented with 'RemoteApps', however, when I log in on the local server (as admin or standard user) I am presented with 'RemoteApps' along with 'Connect to a Remote PC'; which is exactly what I want to see when I log in externally from any client.
So, to add some insight into what I can confirm:
TCP Port 3389 &Â 443 are open.
I am using Internet Explorer (after reading about the ActiveX trap)
IIS show desktops is set to TRUE
Tested with Firewall OFF, Tested with AntiVirus OFF
My server has a hostname of DC-FS01
My SSL certificate has an FQDN of remote.server.com however, internally my hostname looks like DC-FS01.server.local
I have a Forward Zone called remote.server.com that points to the internal server / DNS server IP address, and can ping remote.server.com internally.
I read somewhere that I should be able to ping remote.server.com and get a response, this does not happen in my instance, but I find that strange if I am meant to be able to achieve this when I am going through a browser.
Any insight or advice into this would be much appreciated.
Thanks
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Hello and thanks for your response.
I am temporarily using 3389 (currently for doing direct-to-server admin outside of RDweb) - I will change this when I pass the point of understand what is going on here.
So, when you mentioned "Add the RDWeb URL to Trusted Sites."
Are you referring to the internal address of my RDweb or the FQDN ?
And are you advising to add this on the server or the client trying to reach that address?
But in response to your question, I get to see a similar image you displayed only when I am logging in to remote.server.com on the stand alone server locally, when I jump on another client PC in the LAN and browse to remote.server.com (using IE).. "connect to a remote PC" is omitted from view.
Regards
I am temporarily using 3389 (currently for doing direct-to-server admin outside of RDweb) - I will change this when I pass the point of understand what is going on here.
So, when you mentioned "Add the RDWeb URL to Trusted Sites."
Are you referring to the internal address of my RDweb or the FQDN ?
And are you advising to add this on the server or the client trying to reach that address?
But in response to your question, I get to see a similar image you displayed only when I am logging in to remote.server.com on the stand alone server locally, when I jump on another client PC in the LAN and browse to remote.server.com (using IE).. "connect to a remote PC" is omitted from view.
Regards
I suspected this may have something to do with CALs, so I generated a report:
Best Practices Analyzer is complaining about 'device CALs', but then the Microsoft online CAL wizard suggests device CALs would be best suited to configuration this size.
Report Date:,"Monday, 5 February 2018 2:54:34 AM"
CAL Version,CAL Type,Installed CALs,CALs in Use,CAL Availability
Windows Server 2012,RDS Per Device CAL,50,0,Available
Windows Server 2012,RDS Per User CAL,0,0,None
No Per User License has been Issued
No Per User License Issuance has failed
No Per Device License has been issued
Best Practices Analyzer is complaining about 'device CALs', but then the Microsoft online CAL wizard suggests device CALs would be best suited to configuration this size.
Report Date:,"Monday, 5 February 2018 2:54:34 AM"
CAL Version,CAL Type,Installed CALs,CALs in Use,CAL Availability
Windows Server 2012,RDS Per Device CAL,50,0,Available
Windows Server 2012,RDS Per User CAL,0,0,None
No Per User License has been Issued
No Per User License Issuance has failed
No Per Device License has been issued






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Well I should state, that "Connect to a Remote PC" was appearing locally prior to following your steps. Â IT is the external clients not seeing "Connect to a Remote PC" that is the concern.
I will try your advise on the external client 'IE Trusted-Sites' and post the results shortly. Â Thanks for the quick response.
I will try your advise on the external client 'IE Trusted-Sites' and post the results shortly. Â Thanks for the quick response.
To confirm, I tried IE on another computer.. it added some ActiveX plugins and then I was able to get in!
Thanks very much, it would appear the IE security settings was preventing me from getting to the gold.
Now, Â I have a new issue, adding the workstations that are available for remote access to GP ! :)
Cheers Philip!
Thanks very much, it would appear the IE security settings was preventing me from getting to the gold.
Now, Â I have a new issue, adding the workstations that are available for remote access to GP ! :)
Cheers Philip!
Windows Server 2012
--
Questions
--
Followers
Top Experts
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.