Link to home
Start Free TrialLog in
Avatar of InfoTechEE
InfoTechEE

asked on

RDS: Not able to connect via WebAccess from outside world

We are running Windows Server 2008 R2 Remote Desktop Services. We have configured it to use Virtual Desktop Pools. The user accesses the webesite via WebAccess, an clicks on the RemoteApp icon called Virtual Desktop Pools.

When doing this from the LAN, everything works fine. We do receive a security warning shown below, but other than that everything works fine.

"A website wants to run a RemoteApp program. Make sure that you trust the publisher before you connect to run the proram."

Publisher: SalesCloud.domain.com
Type: Remote Desktop Connection
Remote Computer: SaleCloud.domain.local

Here is where the problem is -- I THINK.

When it connects it tries to search for SalesCloud.domain.local -- which is fine when you are on the LAN.

However, when you are outside the LAN, it gives you an error message that it cannot find that server because its not on the same network as you are. See the error message below.

"Remote Desktop can't find the computer "SalesCloud.domain.local". This might mean that "SalesCloud.domain.local does not belong to the specified network. Verify the computer name and domain you are trying to connect to."

I looked all over the place, and don't see where I can change SalesCloud.domain.local to SalesCloud.domain.com.

FYI: Our other RDS server is working just fine, and the remote computer matches the publisher as ServerName.Domain.Com.
Avatar of oztrodamus
oztrodamus
Flag of Australia image

It sounds like your RDS WebAccess gateway is not setup to use 3rd party SSL certificates. That means every remote PC needs to have an entry in it's Host file to resolve salescloud.domain.local to the external interface the SSL certificate is bound to. Obviously, this is not ideal.
ASKER CERTIFIED SOLUTION
Avatar of Cláudio Rodrigues
Cláudio Rodrigues
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of InfoTechEE
InfoTechEE

ASKER

Please see the attached image. It says bcr.local. I think that's where the problem is. Our other RDS server shows domain.com which is an accessable connection from the outside world.
Our other RDS server (granted its not VDI -- simply RDS), shows domain.com instead of bcr.local and its working just fine.
 
Publisher and Remote Computer
ex.JPG
Called MS for support.

There are 2 ways to go about this. If we had domain.com installed everything would be working fine, because our internal and external domain names would be the same.

But since we have domain.local installed, without going through heavy DNS changes internally, this way would not work.

MS advised to install RDS Gateway instead. Worked out great.