• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1380
  • Last Modified:

Remote Desktop (Terminal Server) RDP icon not working externally

Hi Guys,
We've got 5 Terminal Servers (2008R2) and have created a landing page server/rdweb for each. If i go to the landing page of each server there is an RDP icon to open up a full desktop to the server as opposed to just the RemoteApp programs but if i do this inside the network the RDP connection works fine but if i do this from an external address then it errors saying 'Remote Desktop can't find computer 'server', this might mean that 'server' does not belong to the specified network.'
I have flushed the DNS and made sure the FQDN is there. It works fine from inside the network but when connecting from external it cannot find it.
Any ideas ?
Thanks
0
Netexperts
Asked:
Netexperts
  • 4
  • 4
1 Solution
 
WiebrenCommented:
How does the external connect , does the server have it's own WAN ip, portforward or  VPN ?
0
 
NetexpertsAuthor Commented:
Port forward so:

https://domain.com:8888/rdweb
https://domain.com:8889/rdweb

Different port for each server.
0
 
WiebrenCommented:
Are you sure that the RDP session you start from the website doesn't just use standard port 3389 to connect .?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
NetexpertsAuthor Commented:
I assume it does but i would've thought that as i can authenticate and login (i.e get to the landing page) that this would mean anything else is executed from within the network (i.e when i click on the RDP icon it starts up 3389 and just brings up the screen)
Hope that made sense.
0
 
NetexpertsAuthor Commented:
I also can't activate any of the remoteapp programs unless i'm in the network either so i presume this is linked.
0
 
WiebrenCommented:
You probably only forward the landing page, and it probably just serves some activex control that is executed on the client.  The activex control might just use port 3389 and that port is ofcourse not reachable. But you might want to verify this all, maby by using tcpview on the client.
0
 
NetexpertsAuthor Commented:
I managed to sort this, it appears it was a setting on the session host server as this has to be the eternal FQDN but thought i'd give you the points for time taken
0
 
WiebrenCommented:
thanks
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now