locked
Redirect small business work space to another terminal server,how to handle sub domain "remote"? RRS feed

  • Question

  • Hi all,

    I got a situation here.I need to setup a small business server 2011 for my client.Because they are using old windows xp computers,they are not going to replace those computers at this moment,I want to setup terminal service for them and let them work remotely even inside of office to get windows 7 user experience.I don't want them to work directly on this small business server, so I setup another windows 2008 standard R2 as a terminal server to let them work on it.The problem is I want to keep sub domain "remote.xxxx.com" for client to access terminal server (2008 Standard)in office also want to use it with https access (winsbs 2011) outside of company.The sub domain "remote.xxxx.com" was setup to go to winsbs2011 by default.Can I just change it to another sub domain.Some people told me this default remote domain reserved by system,better keep it.

    Is anyone can help me about this?Thank you so much!


    Thursday, August 18, 2011 4:53 PM

Answers

  • Sounds like you have port forwarded 3389 direct to the RDS and are using the RDP client without the RDGateway, right?

    If you change so that you are using the RDP client in gateway mode (with gateway bypass when local, optional) the same RDP settings will work from both inside and outside the LAN, and you get to remove the unnecessary 3389 forwarding.

    http://www.supergumby.dyndns.org/mstsc.htm


    EDIT: BTW - RDS (Remote Desktop Services) is the 'new', but proper, name for Terminal Services.
    • Marked as answer by Sean Zhu - Tuesday, August 23, 2011 7:48 AM
    Thursday, August 18, 2011 9:27 PM