Connecting to Win2k Advanced Server via Terminal Services.

[PushHands]

Following this thread about remote desktoping, I set up a Win2k Advanced Server machine and enabled terminal services.

I've installed the the Remote Desktop from my WinXP cd as described by Microsoft.. I'm able to remote desktop into a laptop that is running WinXP but can not remote desktop in on the Win2k Advanced Server.

I've set the Terminal Services to run automatically but still can not remote desktop in. Am I missing some setting?

edit: btw, I can access the shared drives on the Win2k Advanced Server computer with no problems so the network is up

 

[azev]

Can you define cannot remote desktop to win2k ??
were u able to connect at all and got to a logon screen or nothing at all ??
If you get to a logon screen try login on using administrator account. (I you can only logon using an account that has a logon localy permision enabled --> correct me if I am wrong!!)
Try using IP address of the win2k if you dont have any name resolution services
see if any of that helps.

 

[bozo1]

Is Remote Desktop the same as Terminal Servies? I believe you need to install the WTS client.

 

[PushHands]

Remote desktop is a feature, I believe, Microsoft had in their Server version of NT based OSes, at least starting with Win2k. They added that feature into WinXP so you could remotely view and control another computer that was running that particular service which allows remote access.

You can install the remote desktop viewer off the WinXP cd or by downloading the program from Microsoft (see the link in my first post). But you still need a computer to be running terminal services/remote desktop services in order to have the ability to access it.

To answer your 2nd question, no, I can't even get to the logon screen. Remote desktop requires you to use IP addresses.

 

[PushHands]

WTS = Windows Terminal Services client?

 

[bozo1]

Originally posted by: PushHands
WTS = Windows Terminal Services client?

Yes. What I meant was that Remote Desktop is an XP feature. WTS is built-in to W2K Server. I don't think you can use XP's Remote Desktop client to access a W2K Terminal Server.

 

[PushHands]

I see bozo1. What would you use then?

 

[azev]

Yes. What I meant was that Remote Desktop is an XP feature. WTS is built-in to W2K Server. I don't think you can use XP's Remote Desktop client to access a W2K Terminal Server.

Yes you can !!! I used it at work and at home everytime.
Make sure you install terminal service on windows 2000 (Administration Mode) and it will allows 2 connections to your server.
You should be able to connect to the server using windows XP client (much better featured compared to what win2k terminal service client offers).

 

[bozo1]

That's what I was asking cause I didn't know for sure.

Dunno what the problem is. You may try to use the regular WTS client to try and pinpoint the problem. You can do Start, Programs, Administrator Tools and create a WTS client diskette from there and use it to install or look around the W2K machine for the actual files. (Don't remember offhand what directory they are in.)

 

[PushHands]

Originally posted by: azev
Yes you can !!! I use it at work and at home everytime.
Make sure you install terminal service on windows 2000 (Administration Mode) and it will allows 2 connections to your server.
You should be able to connect to the server using windows XP client (much better featured compared to what win2k terminal service client offers).

I'm logged in and have administrative rights and terminal services is running according to the Services list. How do I make sure it allows 2 connections to the server?

 

[azev]

by default when you enable terminal services in windows 2000 and you dont have terminal service licence number, it will only allow 2 connection in remote administration mode.

Well if all have failed, why dont you remove terminal services from add/remove software windows component, reboot the computer and reinstall it again using add/remove software.

You can also check your terminal service manager and see if the rdp is listening to any request/enabled.

See if that helps