fdarkow
asked on
Remove the /tsweb location from the Remote Web connection URL
We have recently set up a windows 2003 terminal server. We are able to connect using both Remote Connection and Web Remote connection, but want to reduce the URL to NOT include the /TSWeb addition.
The format we are using now is: Server name.domain.com/tsweb. This gets us to the page that allows us to choose the server name and resolution or screen size. We want to change it to: Server name.domain.com to bring up the sign in page instead.
Do you have any articles for this or do you know the location that must be used to allow this? Input would be appreciated as the boss wants it done ASAP - so we are under a bit of pressure to get it done quickly.
Thanks for your help.
The format we are using now is: Server name.domain.com/tsweb. This gets us to the page that allows us to choose the server name and resolution or screen size. We want to change it to: Server name.domain.com to bring up the sign in page instead.
Do you have any articles for this or do you know the location that must be used to allow this? Input would be appreciated as the boss wants it done ASAP - so we are under a bit of pressure to get it done quickly.
Thanks for your help.
Lee W, MVP
Create a Virtual directory in IIS and point it's home page to the path for /tsweb. In addition, you'll have to create a DNS entry and setup a host header entry.
ASKER
Do you know where we can find the directions for each of these? Or articles from MS?
I'll post the information shortly
Who's running your DNS? That's going to be a key part - do you have control over it?
ASKER
We have a Windows 2000 server for the Network DNS. For the External DNS server, we have UUNET and a connection setup where they take care of the multiple servers and DNS connections we have to manage in another part of our business.
With the External DNS numbers, we can control where each one points and assign them for each as needed.
With the External DNS numbers, we can control where each one points and assign them for each as needed.
Try this code. It is borrowed from OWA
<%
If Request.ServerVariables("S
Dim strRedirURL
strRedirURL = "https://" & Request.ServerVariables("S
strRedirURL = strRedirURL & "/exchange"
Response.Redirect strRedirURL
End If
%>
http://www.microsoft.com/technet/community/columns/5min/5min-301.mspx
<%
If Request.ServerVariables("S
Dim strRedirURL
strRedirURL = "https://" & Request.ServerVariables("S
strRedirURL = strRedirURL & "/exchange"
Response.Redirect strRedirURL
End If
%>
http://www.microsoft.com/technet/community/columns/5min/5min-301.mspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Will give it a try to see what we get. Thanks for all your input. Will let you know how it goes.
ASKER
I found the answer - the router had improperly redirected the IP/URL to the old Terminal Server at port 80. I redirected it to the correct IP for the new Terminal Server and it worked fine.
Can't believe that it was that silly. Thanks for all your help anyways. It was good practice checking all the settings.
Can't believe that it was that silly. Thanks for all your help anyways. It was good practice checking all the settings.