Terminal Services - Web Access Help 1

[vtsmike]

We have a WIN2K pro server. It is running Terminal Services, and has the 90 day license enabled. I have 1 5 pack client license, but since I 'lost' the previous install, it says they are used. I don't think my problem is related to this, but maybe it is.

I can connect remotely to TS through a VPN, using IP/Sec. It works fine.

My problem is that I cannot get TSWeb to work. I have tried inside the network, and from a public IP. The result is the 404 message page cannot be found. I am trying to access using IE6 //servername/tsweb

I have checked the obvious things, but I am guessing there is some TSWeb setting that I have not 'enabled'.

Thanks.

 

[comtec17]

Do you have IIS installed on the servers you are trying to connect to via the TSweb?

I am pretty sure that if you want to use TSweb, each of the clients must be running IIS.

 

[Stevehewitt]

You must be running IIS and have the Remote Desktop Connection App installed locally. (E.G. WinXP or download it from the MS site.)
The only problems I have had is when tightening security IIS kept on changed the default document settings in IIS which meant I kept getting a 404 error. Make sure that default documents are on.

Other than that, the TSWeb extra works out of the box. Pretty good as well if you ask me!

Another test is to go to

http://localhost/tsweb/

from your local server hosting the TS Sessions. Then you can see if IIS is stopping it from remote sessions, or if it's all sessions!

 

[vtsmike]

Yes - I have IIS on the server that is being accessed.

No - I did not have IIS on the client.

Yes - I did have the remote connection software.

I have a remote XP machine, that I installed IIS and still could not connect to the server.

I have a local network machine that is 2000, I have to install IIS and try it.

But, the kicker at this point is that I cannot access it locally on that server. I open IE on the server, using localhost, the network IP, or the servername /TSWeb and I still get the 404 page. IIS has the default pages allowed.

Any more things to check?

 

[Stevehewitt]

Take a look in the inetpub\

http://wwwroot\

folder and make sure that there is a folder in there called TSWeb and I think it's an index.htm or index.html file. I know it sounds daft but something as simple as forgetting to copy the TS folder across is easily done. (I should know!)

You don't need IIS on the localhost on the client. E.G. The WinXP machines don't need IIS.

What happens when you go to

http://localhost/

? Does it come up with anything or another 404 error?

Steve.

 

[vtsmike]

Steve,

Thanks for the insight.

I realized early on that TSWeb does not exist in inetpub\

http://wwwroot\

- I was afraid to touch it, or add it it since I figured it should have some 'magical' powers.

Should I add the folder manually?

What index/default page shoule be used?

When/where does the magic take place?

The IIS running on that server does work correctly, and serves the index page from the default root when accessed locally or across a public IP.

 

[Stevehewitt]

No problem Mike.

By default, IIS uses the C:\Inetpub\

http://WWWRoot\

folder as the web share for the default first web. Generally, I keep it this way and would recommend just copying the TSWeb folder manually to the

http://WWWRoot\

folder. Give it a go after the copy and hopefully it should just work.

The magic of TSWeb is actualy in the index.htm (or .html) file within the TSWeb folder. It uses an ActiveX control.
Something I do when I am setting TSWeb up is to open up the index.htm/html page in some WYSIWYG HTML Editor like FrontPage (or you can edit the HTML directly if you want but my HTML skills aren't good enough) and change the default value of the 'Connect to:' box so it has the name of the TS server in it.

One other thing - for TSWeb to work remotely (from a public terminal outside of your local network) I think you have to open port 3389 on your firewall.
This wouldn't be necessary if you are connecting through a VPN to the network first.

Let us know how you get on and good luck!

Steve.

 

[vtsmike]

Steve,

I beleive we are onto the answer then.

I do not have a TSWeb folder anywhere on the C: drive for that server. This is where the IIS was originally installed, and where it is currently running. You are correct the default root is the way we have it.

So where can I copy TSWeb folder from?

Thanks!

 

[Stevehewitt]

Try

http://www.microsoft.com/downloads/...b5-97ff-47bc-bacc-92283b52b310&DisplayLang=en

Download it and go through the wizard. It defaults to the IIS

http://WWWRoot

folder anyway. Finish the installation (only takes a few seconds) and you should be sorted.

Steve.

 

[vtsmike]

Steve,

That did the trick.

I will check at home for our firewall passthrough, and we should be all set.

Thanks for all the help!

-Mike

 

[Stevehewitt]

No problem.

Thanks for the star, and if you still have problems post back.

Steve.