RemoteApp/Webaccess and Exchange same network

I am having problem using the Exchange and RDS on the same network.

1- Server 2012 with Exchange 2013,  RD Lic
2- Server 2012 with RD web access, RD Gateway, RD Connection Broker, and RD Session Host.

Setup Exchange/OWA on port 443 and  works ok.

When Install the Remote Desktop services, It was on 443 and was not able to use it.
So change it to 1443 port, I can connect to the website and login but when try to run the RemoteApp get error

"The Remote Computer does not support RemoteApp. For assistane, contact your system administrator"

On one PC but other PC work fine from the office. From Home it work ok.

Before I was having problem from all pc, but as suggest by some one I have add this to RDPCustomSettings


where is the web address
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
You either need a reverse proxy or you need two public IP addresses.  Both Exchange and RDGateway *really* want to run on 443 and are not really movable under normal circumstances. While you can move RDWeb, RDGateway is not the same role and is not so easily moved. Even those that successfully move it (using unsupported and undocumented methods) find it breaks with regular patches (hence the unsupported.)  It is just a terrible road to go down.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MTCCOMPAuthor Commented:
As I have understand  the under Server 2012 they allow to change the default port for RDS under transport setting which I have done. And strangle it work on OK on from HOME PC (different network) and works from WORK-PC1 but does not from WORK-PC2, also if connect the WORK-PC1 to different network (it does not work anymore), so I thought some thing is block by second network. But what?
But WORK-PC2 does not work from both Network.
Cliff GaliherCommented:
Keep in mind that the S in RDS stands for "services" and is plural.  RDS is a collection of services, not a single service.   Some services can be changed easily (like RDSH and RDWeb) while others cannot. Since the primary purpose of deploying RDGateway is to allow outside access (it isn't needed for internal access only) and is intended to work *without* a VPN, it was really designed to only run on 443, which is an allowed outbound port on most networks such as hotels and similar. Deploying it on a non-standard port defeats the primary purpose of RDGateway and you might as well just require a VPN which is more standards based and tends to also be easier to access.

It is still relatively easy to get a second IP address from most ISPs in the US and across Europe (as I don't know your location), but if you are really in a place where you can't, a reverse proxy really is your best option. Most modern UTMs (which any small business should have) such as Sophos, SonicWALL, WatchGuard, Untangle, and others offer a reverse proxy as part of their UTM services. And there are several open-source free variants as well. Apache can run as a reverse-proxy  for example. Even the Linux-based firmware releases for consumer routers like pfsense and tomato can be configured to do this with, admittedly, a bit of effort and with not great performance (but why would you use a consumer router in a business?)  So cost is rarely a barrier to a proper deployment.
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

MTCCOMPAuthor Commented:
I agree with you with all the things and I have 2nd IP which I  am using to test setup.
As I do not want to touch the production server until I am sure new server (VM) will work.  

I do not have 3rd IP to test that if it will work from outside because
as my test setup is working from ONE PC (external network) and not other PC(external network), Make me thing that there is possible it will do same when I will have 2nd IP for RDS. To me it looks that some thing on the External Network or PC that is the problem.
MTCCOMPAuthor Commented:
Also I Need RDS to just run one REMOTEAPP.
Cliff GaliherCommented:
Not sure why you'd need a 3rd IP, unless both your exchange *and* RDS servers are still in testing.  Which in that case I'd say you are trying to tackle two (mostly) unrelated problems at the same time.  Get your Exchange server in production and have that on one IP.  Then use your second IP for testing just RDS.  And when you have it working, shift the IP to a production server.  You'd never be using more than two IPs and you aren't making changes to a production environment.

As far as the behavior you expect, as I said, there are just too many variables to make RDGateway run on a non-standard port reliably. It will very likely work *unreliably* as you've discovered. But if you knew the answer, you probably wouldn't have come here looking for help (as you'd already know the answer!)  So it isn't in my interest to continue to argue the point. You can either continue to believe your own answer despite the evidence, or you can accept that what you are trying to do isn't going to work. I have no vested interest either way. I was just trying to help. But I have no interest in continuing to argue.
MTCCOMPAuthor Commented:
Thanks for you input. Discussion  here is to troubleshoot not to argue.

Just to clear, 1 IP is use by the old server for DOMAIN/exchange/ TS in one server in production.

2nd IP is test env.  for VM Host where I am hosting 2 VM machine one for Domian/Exchange 2103 and one for RDS. I do not have 3rd IP, to check the Microsoft theory the having 2 ip will solve the problem also  if that was the case Microsoft should have said "2 IP is required to use Exchange and RDS in same network" and Microsoft would not have given the option (in Server 2012 R2) to change the Port as it was not given in Server 2012.

Any way thanks for all you help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.